WordPress Error Messages: What Each One Means and What to Do

Who wrote the error tells you who fixes it: a critical error comes from WordPress, a memory error from PHP, and 502, 503 and 504 errors from your server or host
The short answer

Copy the exact words of the error, then find out who wrote it: WordPress, PHP, your server, your CDN or a plugin. That tells you what broke and who can fix it. Find your message in the table below, take a backup, and change one thing at a time. Rather have us fix it?

An error message on your website feels like an emergency, and most of them read like they were written for programmers. But every WordPress error message is a clue. The exact wording tells you what failed, and often who can fix it.

We look after WordPress sites for small businesses every day, so this guide works from what you actually see: the exact message, who wrote it, what it means, and the first safe step. Where we have a full guide for one error, we link to it instead of repeating it here.

Read the whole message first

Most people read the first few words, panic, and start changing things. Read all of it, and copy it somewhere. The message usually says who wrote it:

  • WordPress writes plain sentences, like “There has been a critical error on this website.” or “Error establishing a database connection”.
  • PHP, the language WordPress runs on, writes technical lines like “Allowed memory size of 268435456 bytes exhausted” or “Parse error: syntax error”. These usually name a file, and the file name points to the plugin or theme behind it.
  • Your server or host writes the numbered pages: 403, 404, 500, 502, 503 and 504. A 4xx code means the request was refused or the page was not found. A 5xx code means the server itself failed.
  • Your CDN, such as Cloudflare, shows its own branded error pages when it cannot reach your server.
  • A plugin can show its own errors in its own words, and those are not in any WordPress list.

If something looks broken but there is no message on the page, open your browser’s developer tools (Ctrl + Shift + I in Chrome) and check the Console tab. Each error names the file that failed, and the file path tells you the source: /plugins/ points to a plugin, /themes/ to your theme, /wp-includes/ to WordPress core, and a different domain usually means your CDN. Start with the first error in the list. Most of the time, that is the real problem and the rest follow from it.

Asked ChatGPT already?

That is a good first step, and pasting the whole message helps. The table below shows what the common ones mean. In a chat window, the AI only sees what you paste in, so you run each step and tell it what happened. Count your time, too. If an hour of your time is worth $75, an afternoon of steps costs more than our $199 fix. Rather hand it off? We fix it for $199, the same business day if you reach us by 2pm ET.

WordPress error messages and what they mean

Here is the exact wording (WordPress 7.1, October 2026), who writes each message, and where to start:

What you seeWho wrote itWhat it meansWhere to start
“There has been a critical error on this website.”WordPressA plugin or theme crashed. WordPress emails the site admin a recovery linkFix the critical error
A blank white pagePHP (hidden)The same crash, with the message switched offFix the white screen
“Error establishing a database connection”WordPressWordPress cannot reach the database that holds your contentDatabase connection
“Briefly unavailable for scheduled maintenance. Check back in a minute.”WordPressAn update is running, or stopped partwayStuck in maintenance mode
“Another update is currently in progress.”WordPressA core update lock is still setUpdate lock
“Updating failed. The response is not a valid JSON response.”WordPress (editor)The editor could not save through your site’s REST APIInvalid JSON response
“The uploaded file exceeds the upload_max_filesize directive in php.ini.”WordPress, reporting a PHP limitThe file is bigger than your server allowsUpload limits
“Allowed memory size of … bytes exhausted”PHPA task needed more memory than PHP is allowedMemory limit
“Parse error: syntax error, unexpected …”PHPA file has broken code, usually from a recent edit or snippetUndo the last code change in your host’s file manager
“Sorry, you are not allowed to access this page.”WordPressYour user role cannot open that screenAccess errors
“The link you followed has expired.”WordPressA security check failed: a page left open too long, or an upload too bigExpired link
“Destination folder already exists.”WordPressA plugin or theme folder with that name is already on the serverRemove the leftover folder, then install again
Login page errorsWordPress or a security pluginWrong details, a lockout or a login loopLogin errors
403 ForbiddenYour server or a firewallThe server refused the requestAccess errors
404 Not FoundWordPress or your serverThat address has no pageFix 404 errors
500 Internal Server ErrorYour serverSomething failed and the server will not say whatFix a 500 error
502, 503 or 504Your server or hostThe server is overloaded, restarting or too slow to answerWait a minute, then check why the site is down
Cloudflare error 521 or 522Your CDNCloudflare is fine, but your server did not answer itCheck the server, then your host

Older guides still list “Are you sure you want to do this?”. Current WordPress says “The link you followed has expired.” for the same failed security check.

“Error establishing a database connection”

Everything on your site, from pages and posts to users and settings, lives in a database. When WordPress cannot reach it, every page shows this one line. WordPress’s own documentation lists three causes:

  • The connection details in wp-config.php are wrong. This happens after a move to a new host or a password change. If nobody touched the site, this is the least likely cause.
  • The database server is down or over its limits. This is the most common cause for a site that was fine an hour ago, and only your host can fix it.
  • The site was hacked and its files were changed.

So if nothing changed on your end, contact your host first. Tell them the exact message and the time it started. If the site just moved, compare these four lines in wp-config.php with what your host’s control panel shows:

define( 'DB_NAME', 'your_database_name' );
define( 'DB_USER', 'your_database_user' );
define( 'DB_PASSWORD', 'your_database_password' );
define( 'DB_HOST', 'localhost' );

DB_HOST is often localhost, but some hosts use their own address, so check theirs. Do not restore a backup over a database that is only unreachable: the data is usually still there.

Errors inside your dashboard

Most error lists stop at the messages your visitors see. These are the ones owners and editors hit while working in WordPress.

“Updating failed. The response is not a valid JSON response.”

When you save in the block editor, it sends your changes to your own site and expects a short, clean reply. This message means the reply was something else, often an error page. The common causes, in the order to check them:

  1. Re-save your permalinks. Go to Settings, then Permalinks, and click Save Changes without changing anything. This rewrites the rules the editor relies on.
  2. Check your site address. Under Settings, then General, both addresses should match your real address, including https. A mismatch after a move or an SSL change breaks saving. Our guide to changing your WordPress domain covers fixing it.
  3. Look at security plugins and firewalls. Some block the requests the editor depends on. If saving only fails on certain content, a firewall rule is a likely cause.
  4. Look for a PHP warning. A plugin that prints a warning into the reply breaks it. The debug log shows it.

Upload limits

Your server sets the largest file it will accept. When you go over it, you may see “The uploaded file exceeds the upload_max_filesize directive in php.ini.”, “… exceeds the maximum upload size for this site.”, or a “413” error from the server. The fix is to compress the file or ask your host to raise the limit. The settings are upload_max_filesize and post_max_size, and on most hosts you change them in the control panel, not in WordPress. If your host lets you edit php.ini or a .user.ini file in your site’s main folder, these two lines raise the limit to 64 MB:

upload_max_filesize = 64M
post_max_size = 64M

Keep post_max_size the same as upload_max_filesize or larger. The change can take a few minutes to show up, and your host’s own maximum still applies.

Two related messages point to the server, not your file: “Missing a temporary folder.” and “Failed to write file to disk.” Both usually mean a server setting or a full disk, and your host can check them.

One trap: a theme or plugin zip that is too big often does not say so. The server throws away the upload, the security check fails, and WordPress shows “The link you followed has expired.” instead.

“Allowed memory size of … bytes exhausted”

This is PHP saying a task ran out of memory. WordPress asks for 40 MB on normal pages and up to 256 MB for heavier work in the dashboard, unless your server already allows more. You can raise both in wp-config.php, up to what your host permits. Add these lines above the line that says “That’s all, stop editing!”:

define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

If the error names a plugin file, that plugin is the one to look at: more memory hides a problem, it does not always fix it.

Check what was running when it happened, too. Our own site logged memory errors during its nightly backups, not during visits. The cap was WordPress’s own 256 MB default for that kind of task, not the limit in the hosting panel, so raising the panel setting did nothing. Adding the WP_MAX_MEMORY_LIMIT line above to wp-config.php, set to 512M, fixed it the same day.

“Sorry, you are not allowed to access this page.” and 403 Forbidden

These look alike, but they come from different places. “Sorry, you are not allowed to access this page.” is WordPress: you are logged in, but your user role does not have permission for that screen. It is also common when a bookmark points to the settings page of a plugin that is no longer active, and after a move when the database table prefix changed. Check your role under Users, or ask another admin.

A plain “403 Forbidden” page comes from your server or a firewall, before WordPress even runs. The request was refused, and logging in again makes no difference. The usual causes are a security plugin or firewall rule, a block from your host, or wrong file permissions (typically 755 for folders and 644 for files). Your host’s error log often names the rule that blocked it.

If your host gives you SSH access, these two commands, run from your WordPress folder, reset the usual permissions. Take a backup first:

find . -type d -exec chmod 755 {} +
find . -type f -exec chmod 644 {} +

“Another update is currently in progress.”

When WordPress updates itself, it sets a lock so two updates cannot run at once. The lock lasts 15 minutes, so the first fix is to wait 15 minutes and try again. If it still shows after that, the update probably stopped partway. First check that WordPress finished updating and that the site works. Then the lock can be removed. With WP-CLI (ask your host if you are not sure you have it):

wp option delete core_updater.lock

Without WP-CLI, delete the row named core_updater.lock in the options table using phpMyAdmin, after a backup. Our guide to updating WordPress covers what to do when an update breaks your site.

“The link you followed has expired.”

WordPress adds a security token to forms and admin links, and the token runs out after about a day. If you left a page open overnight, reload it and try again. If you get this while uploading a theme or plugin, the file is probably over your upload limit (see upload limits).

No error, but pages are missing

Sometimes there is no message at all: a page or post is simply gone. Before you restore anything:

  • Check the Trash under Posts or Pages. WordPress keeps trashed items for 30 days before deleting them for good.
  • Check the status. A page set to draft or private disappears from the site without being deleted.
  • Check the revisions if the page is there but its content changed. WordPress keeps earlier versions you can go back to.
  • Check recent changes. A new theme or a deactivated plugin can hide content without deleting it.

If it really is gone, restore only what is missing, not the whole site. Our guide to restoring WordPress from a backup shows how.

A real example: the upload error that called itself a success

Staff at a trade association we look after were sometimes blocked from uploading PDFs. Their workaround was to make a small edit and try again. When we looked, every upload in the server logs had returned a normal “200 OK”. Nothing was over the file size limit, and the error monitor was empty.

WordPress reports most upload failures inside the reply rather than as a server error, so the logs could not see them. We added a temporary upload logger and caught the real message: “The uploaded file is not a valid photo extension.” WordPress did not write it. The page builder did: opening its photo picker marked every later upload in that session as a photo, so PDFs were refused. Once we could reproduce it in three steps, the fix was small, and the PDF that had failed went through the same afternoon.

Before you change anything

  1. Back up first. A fix can go wrong, and a fresh backup lets you undo it.
  2. Don’t update everything as a first move. An update is often the cause. Find out what changed before you change more.
  3. Change one thing at a time and check the site after each change, so you know what fixed it.
  4. Look from a private window. Your browser and caching plugins may show you an old copy of the page.
  5. Turn on the debug log only while you track the problem, and never show errors to visitors. Our debug log guide shows the safe way.
  6. Know when to hand it over. Database errors with the right details, 5xx errors and firewall blocks belong to your host. Send them the exact message, the time, and what you already tried.

Rather have someone fix it?

Whatever the message says, we find what caused it and fix it.

  1. Send us the messagePaste the exact words or send a screenshot.
  2. We find the cause and fix itWe test the fix and make sure it stays fixed.
  3. You get back to your businessWith a plain-English note on what happened.

Want to know what else might break? Our free Uh Oh Score checks your site and shows what to fix first, with no sales call required.

Get my Uh Oh Score

Questions people ask

How do I fix a WordPress error?

Copy the exact message, find out who wrote it (WordPress, PHP, your server, your CDN or a plugin), and look it up in the table above. Take a backup, then change one thing at a time and check the site after each change.

What does “Error establishing a database connection” mean?

WordPress cannot reach the database that stores your content. If nothing changed on your end, the database server is usually down or over its limits, and your host has to fix it. After a move or a password change, check the details in wp-config.php.

Why does WordPress say “Updating failed. The response is not a valid JSON response”?

The editor tried to save and got something other than the reply it expected, often an error page. Re-save your permalinks, make sure both site addresses under Settings, then General match your real https address, and check security plugins or firewalls that may block the save.

Why does WordPress say “Sorry, you are not allowed to access this page”?

You are logged in, but your user role does not have permission for that screen. It also happens when a bookmark points to a plugin that is no longer active, or after a move when the database table prefix changed. Check your role under Users or ask another admin.

How do I increase the WordPress upload size limit?

The limit is a server setting (upload_max_filesize and post_max_size), so on most hosts you change it in the control panel or ask support to raise it. Compressing the file is often the faster fix.

Why am I getting a WordPress error after an update?

A plugin or theme often is not ready for the new version of WordPress or PHP, or the update stopped partway. A critical error points to the plugin or theme, and “Briefly unavailable for scheduled maintenance” means the update did not finish. Restore the backup you took before updating if you cannot find the cause.

My pages disappeared but there is no error. What now?

Check the Trash first (WordPress keeps trashed items for 30 days), then whether the page was set to draft or private, then its revisions. If it is really gone, restore only that content from a backup.

Can I paste a WordPress error into ChatGPT?

Yes, and it is a good way to learn what a message means. Paste the whole message, not just part of it. In a chat window, the AI only sees what you paste in, so it can’t look inside your hosting account, your logs or your other plugins. Take a backup before you try a fix it suggests, and change one thing at a time. Count your time, too. If an hour of your time is worth $75, an afternoon of steps costs more than our $199 fix. AI tools can also connect to the site and make changes themselves, but someone who knows WordPress has to set them up safely and check every change they make.

Sources

  1. WordPress 7.1.3 source code, class-wp-fatal-error-handler.php, functions.php, load.php, file.php and default-constants.php (message wording, memory defaults, trash period).
  2. WordPress Developer Resources, Common WordPress Errors (checked October 2026).
  3. MDN Web Docs, HTTP response status codes.
  4. PHP Manual, core php.ini directives (upload_max_filesize, post_max_size).

Keep your website working as hard as you do

We update, back up, monitor and protect your WordPress site every day, and if an update breaks something, the fix is included on every plan.

Jonathan Wofford
About the author

Jonathan Wofford is the founder of Your WP Guy, a WordPress care and maintenance service supporting 105+ active client sites. He and his team keep WordPress sites fast, secure, and running, so business owners can stay focused on their business instead of their website.

More about Jonathan and the team

Keep reading

Leave a Comment