Why does my Web site not display correctly?
If you cannot see your Web site after you upload your site content, here are a few things you can check.
Verify your upload directory
You must upload files to the appropriate directory in order for your Web site content to display. Depending on your FTP client, you may be asked for a "home" or "start" directory. Our hosting service does not require this information, so you should leave that field blank. If your client requires a value, enter a single forward slash (i.e., /) for Linux accounts or a single forward slash followed by your hosting name (i.e., /<user name>) for Windows accounts.
NOTE: When publishing or editing with FrontPage, it automatically places folders in the correct location.
Verify your home page file name
When your domain name is typed into a Web browser, the default home page should display. This page must have a name that our hosting servers support. Depending on your account type, your order of precedence for default files may vary slightly. For more information on this topic, see the following articles:
What is the order of precedence for the default files on my Linux hosting account?
What is the order of precedence for the default files on my Windows hosting account?
Refresh your Web browser
Browsers can cache Web pages. To clear the cache and refresh your page, press CTRL + F5 for Internet Explorer, or press CTRL + R for Firefox.
Ensure your DNS is pointed correctly
If you registered your domain through us, your DNS records were updated when you set up your hosting account. If you registered your domain name elsewhere, confirm that you're using the appropriate nameservers.
The default nameservers for your hosting account depend on the day you set up your hosting. Use this list to determine your default nameservers:
- After March 11, 2008
- ns51.domaincontrol.com
ns52.domaincontrol.com - September 12, 2007 – March 10, 2008
- ns43.domaincontrol.com
ns44.domaincontrol.com - January 31, 2007 – September 11, 2007
- ns5.secureserver.net
ns6.secureserver.net - November 15, 2006 – January 30, 2007
- ns1.secureserver.net
ns2.secureserver.net - December 15, 2005 – November 14, 2006
- ns3.secureserver.net
ns4.secureserver.net - Before December 14, 2005
ns1.secureserver.net
ns2.secureserver.netOR wsc1.jomax.net
wsc2.jomax.net
Solve image problems
If your images are not displaying, make sure that the directory where they are located and the image page specified in your code match exactly. Additionally, Linux accounts are case sensitive. For example, if the name of your image is MyImage.jpg and the path in your code is myimage.jpg, the server cannot locate your image.
Correct broken site links
If you developed your Web site locally, your code should adjust for the environment change that occurs when you upload site content. Web page URLs, image paths, and database names can all be environment-sensitive.
We recommend that you use relative URLs when referencing Web pages. Relative URLs identify a Web page in relation to, or in the context of, the current page. Because they do not reference the domain name, relative URLs do not require modification when changing environments.