Find the cause in the logs
Your website's logs are in your home folder, in logs/example.dk/. Open them with the file manager or SFTP; the newest lines are at the bottom.
| File | Contains |
|---|---|
php-error.log |
PHP errors – the most useful file for a white page or error 500 |
error.log |
Web server errors, for example files that are missing or not allowed |
apache-error.log |
Errors from .htaccess (only with Nginx + Apache) |
access.log |
Every visit, with the status code |
Common errors
500 Internal Server Error, or a white page
Usually a PHP error. Look at the last lines of php-error.log. Common causes: a plugin that does not work with the PHP version (try the previous version under Settings on the Websites page), too little memory (raise PHP memory limit), or a mistake in .htaccess.
403 Forbidden
There is no index.php or index.html in the folder, or a rule in .htaccess blocks the visitor.
404 Not Found
The file does not exist at that address. Check that the files are in example.dk/public and not in a subfolder. For WordPress and other apps with "pretty" links, the web server must be Nginx + Apache (.htaccess support).
502 Bad Gateway or 504 Gateway Timeout PHP did not answer in time, often because a script runs too long. Raise Max execution time (s), or move long jobs to a cron job. If the whole site is down, contact us.
"Your connection is not private" The certificate is missing or does not cover the address. See HTTPS and certificates.
The site shows our "suspended" page The subscription is suspended, for example because of an unpaid invoice. Contact us.
Errors are not shown on the page
For safety, PHP errors are written to php-error.log instead of being shown to visitors, because error messages can reveal paths and passwords. Always look in the log first.