First, find out which layer failed
"The website is down" can mean three different things:
- DNS fails — the name does not resolve. The browser shows "server IP address could not be found".
- HTTP fails — the name resolves and the server answers with an error status such as 500 or 503.
- Content fails — the page loads but is wrong, blank, or missing sections.
Check the status code before changing anything. It tells you whether to look at DNS, the web server, the application, or the database.
curl -I https://example.com
curl -I http://example.com
If curl returns "Could not resolve host", stop here and see "Domain Not Working? How to Diagnose DNS and Propagation".
Read the status class
| Class | Meaning | Where to look |
|---|---|---|
| 4xx | The request is wrong or not allowed | URL, permissions, WAF, redirects |
| 5xx | The server or application failed | PHP log, application log, resources |
A 4xx is usually fixable from the site's configuration. A 5xx usually requires a log entry to identify the cause.
403 Forbidden
The server understood the request and refused it. Common causes:
- Wrong file or directory permissions.
- A missing index file and directory listing disabled.
- An
.htaccessrule blocking the request. - A WAF or ModSecurity rule triggered by the request.
- Hotlink protection or IP deny rules.
Do not set files to 777 to test. Use 644 for files and 755 for directories, and check the error log for the specific rule.
404 Not Found
The server is working, but the requested path does not exist. Check:
- The file exists in the correct document root.
- The URL matches the file name, including case.
- WordPress permalinks are configured and
.htaccessis writable. - A redirect is not pointing at a deleted page.
See "How to Set Up 301 Redirects (and Fix 404 Errors)".
429 Too Many Requests
A rate limit was hit. It can come from the application, a security plugin, the WAF, or a CDN. Check whether the limit is per IP or global, and whether a legitimate integration is polling too often. Do not disable the limit permanently; raise it only for the specific source that needs it.
500 Internal Server Error
The application failed while handling the request. This is the most common 5xx on PHP sites and almost always has a log entry.
- Read the PHP error log or the application log.
- Check for a fatal error after a plugin, theme, or core update.
- Check
.htaccesssyntax. - Check the PHP version and memory limit.
- Check file permissions after a restore or upload.
Full procedure: "How to Fix a 500 Internal Server Error".
502 Bad Gateway
A proxy or gateway could not get a valid response from the application. On cPanel this can involve PHP-FPM; on Coolify it is usually Traefik and a container port.
- Check whether the application process is running.
- Check the PHP-FPM pool status and logs on a VPS.
- For containers, see the Coolify 502 article.
503 Service Unavailable
The server is temporarily unable to handle the request. Causes include maintenance mode, resource exhaustion, connection limits, or an application in a restart loop.
- Check for a
.maintenancefile in WordPress. - Check disk space, inodes, memory, and CPU.
- Check whether the database is reachable.
- Check the error log for "too many connections" or worker limits.
504 Gateway Timeout
The request reached the server but took too long. Look for a slow database query, an external API call without a timeout, a large import, or a proxy timeout that is shorter than the application needs. Increasing the timeout without finding the slow operation only delays the failure.
Where to look on shared hosting
- cPanel Metrics then Errors for recent web server errors.
- File Manager for
error_logfiles in the document root. - Disk and inode usage; a full account can return 500 or 503. See Inode Limit Exceeded in cPanel.
- PHP version and extensions; a version change can break an older site.
- Recent changes: update, plugin install, restore, or
.htaccessedit.
Safe first moves
- Back up the site and database before editing files.
- Read the log before disabling anything.
- Change one thing and retest.
- Roll back the last change if the error started immediately after it.
Do not delete .htaccess, disable the WAF, or turn off all plugins at once and leave them off. Those actions hide the cause and can create new problems.
Related articles
- How to Fix a 500 Internal Server Error
- How to Set Up 301 Redirects (and Fix 404 Errors)
- How to Put Your Website in Maintenance Mode (and Take It Out)
- How to Restore Website Files from a cPanel Backup
- Inode Limit Exceeded in cPanel
- How to Fix "Error Establishing a Database Connection" in WordPress
If the status is 5xx and the log does not identify the cause, contact SysopHost support with the exact status code, the URL, the timestamp, and whether the site worked before a specific change. Do not paste full logs containing customer data.