1. Home
  2. Docs
  3. User Guide
  4. Troubleshooting
  5. Website problems

Website problems

This page lists the most common website problems, what they mean and how to fix them yourself in the panel. The first step is almost always the same: look at the error log in the Log Viewer — it usually names the exact cause.

500 Internal Server Error

The server could not run the page.

Likely causeFix
Invalid line in .htaccess (for example Options FollowSymLinks, php_value, an AddHandler for a PHP version that does not exist)Run Internal Server Error and Remove AddHandler in Fix Account Issues, or rename .htaccess temporarily in the File Manager to test.
Wrong file permissions (for example 777 on PHP files or folders)Run Fix Permissions in Fix Account Issues.
PHP fatal errorRead the error in the Log Viewer. Often the PHP version is too new or too old — change it in the PHP Selector.
Memory limit reachedRaise memory_limit in Edit php.ini.

Blank page (white screen)

Usually a PHP error with error display switched off. Check the Log Viewer. For WordPress, a broken plugin or theme is the most common cause — rename its folder in wp-content/plugins to disable it.

403 Forbidden

Likely causeFix
No index.php / index.html in the folderUpload an index file, or check that the site files are in the right folder (see Domains).
Wrong ownership or permissionsRun Fix Account Issues.
A firewall rule blocked the request (forms, admin pages)Check your IP and the rule in ModSecurity.
Folder is password protectedSee Directory Protection.

404 Not Found

The address does not exist. Check the spelling and that the file is in the correct folder. For WordPress and other CMSs with “pretty” URLs, make sure the CMS’s .htaccess file exists (in WordPress: Settings → Permalinks → Save). Use Statistics to find broken links.

“Error establishing a database connection”

The site cannot log in to its database.

  1. Open the site’s configuration file (for example wp-config.php) in the File Manager.
  2. Check the database name and user — both with your account prefix, for example youraccount_shop — the password and host localhost.
  3. In MySQL Manager, check that the user is assigned to the database; reset its password if needed and update the file.

Note: Changing your panel password also changes the password of your main MySQL user. If a site uses that user, update its configuration — see Account settings.

Too many redirects

The site redirects in a loop, usually between http and https or between www and non-www. Check the Redirect list, the .htaccess file and the site address in your CMS settings — they must all agree on one version, for example https://www.example.com.

Certificate / “Not secure” warnings

MessageFix
Your connection is not private / certificate expiredInstall or renew the certificate in AutoSSL. The domain must point to this server.
Padlock with a warning (“mixed content”)The page loads images or scripts over http://. Change them to https:// (in WordPress: update the site address and use a search & replace in WordPress Manager).

Site is slow

  1. Check the Process List for many busy PHP processes and the Statistics for unusual traffic (bots).
  2. Use a newer PHP version in the PHP Selector — PHP 8.x is much faster than 7.x.
  3. Enable caching in your CMS and remove unused plugins.
  4. Optimize the database in MySQL Manager.

Cannot upload or change files

CauseFix
File System Lock is onUnlock it.
Disk quota fullFree space — see Disk Usage.
File larger than the upload limitRaise upload_max_filesize and post_max_size in Edit php.ini, or use FTP.

My site was hacked

  1. Run an Antivirus Scan and clean or quarantine infected files.
  2. Restore a clean backup if you have one from before the infection.
  3. Update the CMS, themes and plugins; remove unused ones.
  4. Change all passwords: panel, FTP, database and CMS admin users.
  5. Switch on the File System Lock and ModSecurity.

Still stuck?

Contact your hosting provider and include: the domain, the exact error message, the time it happened, and what you already tried. A copy of the relevant lines from the Log Viewer helps a lot.

Was this article helpful to you? No Yes