WordPress

Fix common WordPress errors

Diagnose the WordPress critical error, white screen, database connection error, 403 blocks and admin lockouts on FoxFolio Cloud hosting.

Last updated
Last reviewed
For
Customers running WordPress on FoxFolio Cloud
Time needed
About 30 minutes

Quick answer

Most WordPress errors come from a plugin, the theme, a low PHP memory limit or wrong database details in wp-config.php. Check the error log in the control panel, deactivate the most recently changed plugin or theme from the WordPress tools, and compare the database settings with MySQL Databases. Take a backup before editing files.

Before you start

  • Access to the hosting control panel for the site
  • A recent backup, or time to create one before changing files

Applies to: WordPress Cloud, Managed WordPress, Cloud Hosting.

Match the message to the likely cause

What you seeMost likely cause
“There has been a critical error on this website” or a blank white pageA plugin, the theme, missing core files or the PHP memory limit
“Error establishing a database connection”Wrong database name, user, password or host in wp-config.php, or damaged tables
403 Forbidden when saving or submittingThe web application firewall blocked a request that looked unsafe
Cannot sign in to the WordPress dashboardWrong password, a security plugin, or an old site address

Steps

  1. Back up before changing anything

    Create a files-and-database backup. See Create an on-demand backup.

  2. Read the error log

    In the control panel, open the logs section and view the error log. A “fatal error” line usually names the plugin or theme folder at fault.

  3. Deactivate the likely culprit

    On WordPress plans, use the plugin or theme list in the WordPress tools to deactivate it. On any plan, you can rename the plugin’s folder in wp-content/plugins with File Manager to switch it off.

  4. Show the real error if needed

    In File Manager, edit wp-config.php and set WP_DEBUG to true, reload the page to read the message, then set it back to false straight away so visitors do not see it.

  5. Raise the PHP memory limit if the log says memory was exhausted

    Increase memory_limit in the PHP settings. See Change your PHP version and PHP settings.

  6. Fix a database connection error

    Compare DB_NAME, DB_USER, DB_PASSWORD and DB_HOST in wp-config.php with what MySQL Databases shows. The server name shown there is the database host. If the details match, repair the tables with wp db repair over SSH or the repair option in phpMyAdmin.

  7. Regain dashboard access

    Reset the administrator password from the WordPress tools’ Users screen. If a security plugin blocks you, rename its folder to deactivate it temporarily.

What you should see

The site loads normally again, the error log stops showing new fatal errors, and you can sign in to the WordPress dashboard. Update or replace the plugin or theme that caused the problem before reactivating it.

Troubleshooting and common mistakes

Nothing in the error log explains the fault.
Run through Fix a website that is not loading, which also checks the domain, SSL and malware status.
A 403 appears only when saving a particular page or form.
The firewall rule that blocked it can only be adjusted by support. Open a ticket with the page address and the time it happened.
The site broke after an update and none of the above helps.
Restore the backup taken before the update. See Restore files or a database from a backup.

When to contact FoxFolio support

Open a ticket if the error log points to the server rather than WordPress, if the database cannot be reached even with correct details, or if a firewall block needs reviewing. Include the site address, the exact error and when it started. WordPress Cloud support covers the hosting platform; debugging custom code, themes or plugins is outside standard support, though support will tell you what the logs show.

Sign in to open a ticket What to include in a ticket

Sources

Adapted from the platform vendor’s WordPress error, database connection, logs and firewall documentation.