Website not opening or showing an error: start here (diagnostics map)
- 16.07.2026 19:09
-
- troubleshooting
- website
Use this page as a map: find the error code or symptom you see and open the matching guide.
First: check the service status
If several sites or services stopped working at once, check garmtech.info – our status page shows current incidents and planned maintenance. If the issue is listed there, no ticket is needed: the page is updated as work progresses.
You see an error code
- 403 Forbidden / 406: file permissions and common causes; if mentioning a block – Imunify360 blocks (403/406)
- 404 Not Found: after uploading or migrating a site
- 429 Too Many Requests: fix 429
- 500 Internal Server Error: fix 500
- 502 / 503: fix 502/503
- 508 Resource Limit Is Reached: fix 508; also check CPU/RAM limits in Plesk
- Cloudflare 1020: Access denied; Cloudflare 521/522/523: origin unreachable
No error code – a symptom instead
- Site loads forever / “can’t reach this page”: check DNS – which nameservers does the domain use and DNS propagation. Also make sure the domain has not expired.
- Plesk default page instead of your site: publish your site correctly
- “Index of /” file listing: set a default index page
- Certificate / HTTPS warning: install or renew SSL in Plesk, or troubleshoot SSL issues
- Service suspended notice: unpaid invoice – how to restore service
WordPress-specific errors
- “There has been a critical error on this website”
- ERR_TOO_MANY_REDIRECTS
- “Error establishing a database connection”
Still stuck?
Check the exact error in the logs: View website logs in Plesk (access_log, error_log). If you open a ticket, include the domain, the exact error text and the time it occurred – this speeds up diagnostics a lot.
Related Articles
Comments
Add Comment