by dabempire | Feb 26, 2011 | Knowledgebase, Troubleshooting
When you first get set up and your domain becomes active, your URL will most likely bring you to an empty directory listing page or our default welcome homepage. This is because you haven’t uploaded your site yet. If you have uploaded your site, you need to create an index page. An index page can have whatever you want on it, but it must be called “index.html” (or “index.cgi” if it’s a CGI program). Calling the file “index.html” tells your visitors’ browsers to open that page; otherwise, the browser will just show your file list. You need to upload your web files in public_html...
by dabempire | Feb 26, 2011 | Knowledgebase, Troubleshooting
The first thing to do is of course to search through this help system! We try very very hard to always keep this up to date and filled with just about everything you’d ever want to know about our system. It’s faster than live support and can even be more comprehensive. However, we admit there are still some things that really require human intervention, and for that we have our world class technical support team! They are available via the online ticket system 24 hours a day, 7 days a week, 365 days a year. All tech support questions are answered within 24 hours. We do not currently provide telephone support as we feel it is unnecessary in (and can even hinder) providing quality customer...
by dabempire | Feb 26, 2011 | Knowledgebase, Troubleshooting
There are various of factors that can contribute to occasional slow download speeds or time-outs. If it seems that your site generally is always slow, it may be because you have images on your pages that are too large. If you have larger images, try using image compression software to reduce your image file size. Another reason could be a problem or congestion with a provider that is out of our network but between you and us. If your ISP is having any troubles it will also produce the same laggy effect. Run a Trace from your computer to your web site: When you download from your site, you are taking a path to get from your computer to your web site. To do so using Windows: * Go to START * Click on PROGRAMS * Click on MS-DOS PROMPT * Type TRACERT your_domain.com (replace your_domain.com with your domain or IP address) You will see output that has lines like this: phnx-core-7513.getnet.net (216.19.201.247) 0.929 ms 0.946 ms 1.012 ms phnxaz1wce2-se2-1.wcg.net (65.77.92.41) 1.588 ms 1.380 ms 1.227 ms phnxaz1wce1-pos6-0.wcg.net (65.77.92.29) 1.446 ms 1.356 ms 1.779 ms hstntx1wcx2-pos10-3-oc48.wcg.net (64.200.210.105) 24.107 ms 24.046 ms 25.502 ms hstntx1wcx1-pos6-0-oc48.wcg.net (65.77.93.209) 23.818 ms 23.817 ms 23.859 ms Each of the numbers above are three attempts that your computer makes to get to that location. A * or any number over 300 is a sign of a slow link. If you see a slow link the problem is in the route upstream from us, between you and us. If the problem continues or is extend you may want to consider calling them or contact us and...
by dabempire | Feb 26, 2011 | htaccess, Knowledgebase
Create a file named .htaccess in your web directory that contains the following: AuthUserFile /home/yourlogin/yourdirectory/.htpasswd AuthName Secure AuthType basic require valid-user Then in your home directory, type htpasswd -c /home/yourlogin/yourdirectory/.htpasswd pumpkin. You will be prompted to enter a password and verify it. This will enable you to secure the directory so that only user pumpkin can enter this directory. To add additional id/password pairs to the file, leave off the -c, which means ‘create a new file’. For example, htpasswd .htpasswd linus. You may well want any of the user/password combinations you created in your .htpasswd file to allow access. Note that you want to store the .htpasswd file in your home directory so it is hidden from others. The one drawback to putting your .htpasswd file in your home directory is that you will have to slightly lower the security of your home directory. Go to /home (cd /home/yourlogin) and type chmod +x yourlogin. The WWW server needs execute permission on to read the .htpasswd...
by dabempire | Feb 26, 2011 | htaccess, Knowledgebase
RewriteEngine on RewriteCond %{HTTP_USER_AGENT} ^Bullseye.* [OR] RewriteCond %{HTTP_USER_AGENT} ^fastlwspider* [OR] RewriteCond %{HTTP_USER_AGENT} ^EmailSiphon [OR] RewriteCond %{HTTP_USER_AGENT} ^EmailCollector [OR] RewriteCond %{HTTP_USER_AGENT} ^EmailWolf [OR] RewriteCond %{HTTP_USER_AGENT} ^ExtractorPro [OR] RewriteCond %{HTTP_USER_AGENT} ^GetWebPage.* [OR] RewriteCond %{HTTP_USER_AGENT} ^lwp-tribial.* [OR] RewriteCond %{HTTP_USER_AGENT} ^Mozilla.*NEWT [OR] RewriteCond %{HTTP_USER_AGENT} ^Crescent [OR] RewriteCond %{HTTP_USER_AGENT} ^CherryPicker [OR] RewriteCond %{HTTP_USER_AGENT} ^[Ww]eb[Bb]andit [OR] RewriteCond %{HTTP_USER_AGENT} ^WebEMailExtrac.* [OR] RewriteCond %{HTTP_USER_AGENT} ^NICErsPRO [OR] RewriteCond %{HTTP_USER_AGENT} ^SurfWalker [OR] RewriteCond %{HTTP_USER_AGENT} ^Telesoft [OR] RewriteCond %{HTTP_USER_AGENT} ^Zeus.*Webster [OR] RewriteCond %{HTTP_USER_AGENT} ^Microsoft.URL [OR] RewriteCond %{HTTP_USER_AGENT} ^Mozilla/3.Mozilla/2.01 [OR] RewriteCond %{HTTP_USER_AGENT} ^EmailCollector RewriteRule ^.*$ –...
