Use this guide when your website reaches a server but shows an error or old content. If the domain does not resolve, start with domain and DNS troubleshooting. For certificate warnings or redirect loops, follow the HTTPS guide first. Never bypass a certificate warning to sign in.
Identify what fails
Record the exact URL, error text and time with timezone. Test the homepage and one affected inner page. Note whether the problem affects everyone or only one browser, and whether it began after an upload, application update or configuration change. Avoid repeatedly submitting forms or payments while testing.
Read the error
- 403 Forbidden: the request was refused. Possible causes include access rules, a security filter, file permissions or a directory without an allowed index page. Check recent changes and the expected homepage file. Do not make files world-writable or disable security protections to test.
- 404 Not Found: check the URL, filename capitalization and upload location. If the homepage works but application pages fail, ask your developer to check routing or rewrite rules. Use the upload guide for file placement rather than moving whole folders experimentally.
- 500 Internal Server Error: check the error log around the failed request. Application errors, incompatible PHP settings or invalid configuration can cause this response; the code alone does not identify the cause.
- 503 Service Unavailable: check for planned maintenance, resource pressure or an unavailable application backend. Note whether the error comes from your application or a CDN. Do not assume restarting everything will fix it.
If content is outdated
Try a private browser window and a hard refresh. Compare the same URL on another device. Confirm the expected files are in the correct domain's document root. A browser, application and CDN can each cache different content; a private window does not bypass every cache.
If you use a CDN, review its cache status and documented refresh options for the affected URL. Do not delete cache directories, change DNS or turn off the proxy merely to diagnose stale content. Ask support or your developer which layer needs attention.
Check limits and collect safe evidence
Review the storage and traffic usage shown for your hosting account. If a limit is reached or uploads fail, contact support before removing anything. Read the relevant domain or application error log if available; ask support where to find it if not.
Send a short, relevant log excerpt and the checks above using the support checklist. Redact passwords, tokens, cookies and unrelated personal data. Keep detailed errors out of public pages and preserve a backup before any repair.
