Key takeaways
- The error message tells you where to look: domain, DNS, certificate, code or server.
- Most outages follow a change — undo the last one if it is safe.
- Never delete or reinstall in a hurry; back up first and keep the logs.
1. Confirm it is really down
Open the site on your phone over mobile data, and from another network. If it works there, the problem may be your local network, a DNS cache or a blocked IP address.
2. Read the error
- "This site can't be reached" or a DNS error: check that the domain has not expired and that DNS records were not changed.
- "Your connection is not private": the SSL certificate has expired or does not match the domain.
- Error 500 or a blank page: usually code, a plugin or the PHP version after an update.
- 502, 503 or 504: the server, or a service behind it, is overloaded or stopped.
- Strange content or redirects to other sites: treat it as a possible hack.
3. Check the last change
Most outages follow a change: an update, a new plugin, a DNS edit, a full disk or an unpaid invoice. If you can undo the last change safely, do it.
4. Don't make it worse
- Don't delete files or reinstall in a hurry — data and evidence get lost.
- If you suspect a hack, change passwords from a clean device and keep the logs.
- Take a fresh backup or snapshot before you try any fix.
5. Tell your visitors
Post a short status note on social media, or switch to a simple maintenance page. Silence costs more trust than downtime.
When to call for help
If the site is not back within 15 minutes, if payments or email are affected, or if you see signs of a hack, send an urgent request. We secure what is there, restore the service and fix the cause — whether you host with us or anywhere else.
Sources and further reading
The service behind this article
SOS: emergency help
Site down, hacked or expired? We step in with priority.