A website works on the server but not for visitors
When a site loads for you but not for the customer's actual visitors.
If a website loads correctly when checked directly on the server, but visitors report it not loading, doesn't load for the customer specifically, or shows an old version of the site, the cause is almost always DNS rather than anything on the server itself.
Steps
- Confirm what address the domain's DNS is currently publishing, and compare it against this server's address. A recent domain transfer, a nameserver change, or a typo in a DNS record are the most common causes.
- If DNS was changed recently, the delay before every visitor's own internet provider picks up the change can be a real cause on its own, and can take some time to clear everywhere.
- If the customer reports an old version of the site specifically, rather than it not loading at all, they're very likely seeing a cached copy through their own browser or internet provider rather than anything wrong on the server.
Tip: asking the customer to check the site from a different network, such as their phone's mobile data instead of their home internet, quickly tells you whether this is a local caching issue or a genuine DNS problem.