Website not working? Find the cause with Site Check
Symptoms
- The website does not open, times out or shows "This site can't be reached".
- It shows an error page (403, 404, 500, 503) or a blank page.
- It shows a "suspended" or "bandwidth limit reached" page.
- The browser warns that the connection is not secure.
Run the check
- Log in to the control panel (
https://<server>:2083). - Open Site Check in the menu (section Advanced).
- Choose the website and click Check.
Each line has a badge: OK, Check (a warning) or Problem. A Problem line is usually the cause.
Causes and fixes (most likely first)
Address in DNS — NOT this server, or the name does not resolve
The domain points elsewhere or nowhere. Set the domain's nameservers at your registrar to the ones shown on Home and in Zone Editor, or set its A record to this server's address. DNS changes can take up to a day to be seen everywhere. Behind the Cloudflare proxy, the line says so and is not a problem by itself.
Answer on this server — an error code
The website itself answers with an error:
- 500 — usually PHP: see the Latest PHP errors of this site line and the PHP error log. A broken
.htaccessrule can also cause it: see .htaccess rules. - 403 — wrong permissions (files
644, folders755), aDeny from allrule, or noindex.php/index.htmlin the folder. - 404 — the file does not exist in the website's folder, shown on the Website line.
Account — SUSPENDED, or Bandwidth used up
Visitors see a placeholder page. Contact your hosting provider, or wait for the next month for bandwidth.
Disk space or Files and folders — at the limit
New files cannot be written and sites or email can fail. Free space: see what uses your disk space.
Certificate — none yet, or failed
The certificate is issued automatically once the domain points to this server. The line shows the last error. Fix DNS first; the certificate follows.
Still not working?
- If your hosting provider has turned on the AI assistant, click Ask the AI assistant what is wrong for an explanation and steps.
- Check Uptime to see since when the site is down.
- Contact support with the Site Check result: open Support, name the website and copy the lines marked Problem.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to see the PHP error log of your website
Find the PHP errors behind a blank page or 500 error on the Errors page, read the full log in ~/logs/php-errors.log, and show errors while debugging.
- Uptime monitoring: get an email when your website is down
How your websites are checked every 5 minutes, when a site counts as down, the alert emails you get, and how to read the uptime percentages.
- Resource Usage explained: disk, bandwidth, CPU and memory limits
Read the Resource Usage page: disk space by type, monthly bandwidth, file count, and the processor, memory and process limits that can slow a website.
- Which .htaccess rules work on your hosting
What the web server reads from .htaccess: rewrite rules, Deny/Require lines, Files blocks and php_value settings, what is ignored, and how fast changes apply.