Site not found
- 1 Overview
- 2 The Root Cause of the Error
- 3 How to resolve the issue
It’s possible that when you visit your site, you see an error that states ‘Site Not Found’:
This wiki guides you through why you may be seeing this error and how to resolve it.
The Root Cause of the Error
This error means that the IP your domain is resolving to in DreamHost's system points to an Apache web server not configured for your domain.
There are a few reasons why your IP may not be correctly pointed to your web server IP which are explained below.
Viewing your site’s IP address in your browser
Due to the way that DreamHost configures Apache, unless you have purchased a unique IP address for your domain, attempting to view your site by entering the IP address in your browser automatically gives you the Site_not_found error. This is because you’re viewing the shared IP of your web server, not the IP of your site. If you absolutely need to view your site through an IP address, you must purchase a unique IP.
You can read more about Unique IPs here:
Frequently this error appears due to a change in your IP address, which is commonly triggered by removing hosting for a domain and then setting up a MIRROR, REDIRECT, PARK, or CLOAK. While changes to the DreamHost DNS are nearly instantaneous, the new information doesn't reach other servers around the world until the other servers expire the old data that they are holding on to. This is referred to as DNS propagation.
The reason why you get this error during this period of time is that the DNS information you are receiving to your local computer is outdated, and the Apache instance that you are being incorrectly sent to no longer has any record of your site. Depending on your location, it can take up to several hours for DNS changes to propagate, so the best thing to do is leave your domain alone for a few hours before attempting any sort of fix.
In addition, if you go to (Panel > ‘Domains’ > ‘Manage Domains’) and click the small 'DNS' link under a domain, you are presented with a DNS page. When you click the blue Go! button at the top, a DNS update is forced in DreamHost's system. But again, DNS propagation online may still take several hours.
How to check your current DNS records
To check on the status of your DNS update, you can visit what's my DNS? to see what IP address your domain currently resolves to.
Using Linux or Apple Mac
If you’re using a Linux or Mac computer, you can also run some commands in your terminal to check the current IP of your site. Visit the SSH wiki regarding how to log in to your terminal:
Once logged into your terminal, you can run the ‘dig’ command to check the status of the IP resolution. For example, this command checks for the current IP address resolving online in your location. (Your IP is different depending on the server on which your site is located.):
dig +short yourdomain.com 220.127.116.11
This command checks the current IP assigned to your DreamHost nameserver. (Your IP is different depending on the server on which your site is located.)
dig +short yourdomain.com @ns1.dreamhost.com 18.104.22.168
If your domain.com is using DreamHost nameservers, you should be getting the same IP with both commands. If not, try flushing your local DNS. You can read about this in the following wiki:
Windows users can use the "nslookup" command using the command prompt. You can read more about using the command prompt in Windows here:
C:\Users\user>nslookup yourdomain.com Name: yourdomain.com Address: 22.214.171.124
This command checks for the current IP address resolving online in your location. (Your IP is different depending on the server on which your site is located.)
C:\Users\user>nslookup yourdomain.com ns1.dreamhost.com Name: yourdomain.com Address: 126.96.36.199
This command checks the current IP assigned to your DreamHost nameserver. (Your IP is different depending on the server your on which your site is located.)
If yourdomain.com is using DreamHost nameservers, you should be getting the same IP with both commands. If not, try flushing your local DNS. You can read about this in the following wiki:
How to resolve the issue
There are several ways to solve this problem.
Rebuilding httpd conf via Dreamhost's control panel
Go to (Panel > ‘Domains’ > ‘Manage Domains’) in your panel and click on the Edit button to the right of the domain under the ‘Web Hosting’ column. There's no need to change anything on this page. Simply save by pressing the blue Change settings button. Then wait up to 10 minutes to see if the problem is solved. With this solution you've simply rebuilt the httpd configuration file on the web server.
If you're not using DreamHost's DNS
If you aren't using DreamHost to manage your domain's DNS, most likely the IP address that points to DreamHost by your DNS provider is incorrect.
You can figure out the correct IP by querying the DreamHost nameserver with one of the commands in the above section (depending on your OS).
Here's another way to find the correct IP:
- Log in to your panel at (Panel > ‘Domains’ > ‘Manage Domains’).
- Click the ‘DNS’ link under your domain.
- When the Manage Domains page opens, find the A record in the "non-editable" section.
- Update your A record with your DNS provider to point to this IP in our system.
Once the DNS propagates, the sleepy DreamHost robot should no longer appear.
Using a suspended account
For accounts that are suspended due to non-payment, DreamHost will stop serving the DNS for the account. Your sites will then show the Site Not Found page until you are paid up and re-activate the account. Log in to your control panel or check your emails from DreamHost to see if this may be the case.
If you cannot solve this problem using the suggestions above, please feel free to contact support for further assistance.
You can contact support through your panel at (Panel > ‘Support’ > ‘Contact Support’).
Using Passenger WSGI enabled
This problem, or one like it, occasionally manifests on domains that use Passenger WSGI. In this case, the error appears differently in that the server error page does not get displayed.
Symptoms may include:
- Other domains on the same account and server working correctly.
- Timeouts trying to access the site.
- No Passenger processes showing up when running ps -A from the shell.
In this instance, the solution is the same – edit the domain and click Change Settings. Then wait for it to propagate. You can also try disabling and re-enabling Passenger on the same domain edit page as well.
This changes the domain configuration settings without altering the domain DNS records.
|Note:||This will NOT work for cloaked domains since the cloaking service is on a special machine and the DNS will ALWAYS have to change when activating/deactivating cloaked domains.|