Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WordPress Website Not Working: Causes and How to Fix It

WordPress Website Not Working: Causes and How to Fix It

Short answer

A WordPress website usually stops working because of a faulty plugin or theme, a PHP error, a database connection problem, or a hosting, domain or SSL issue. Start by noting the exact error you see, then check recovery mode email, deactivate plugins and read the error log.

Key takeaways

  • The exact symptom, such as a white screen, a critical error or a 500 code, points to the most likely cause.
  • Most broken WordPress sites are caused by a plugin or theme conflict, often right after an update.
  • Since WordPress 5.2, fatal errors trigger recovery mode and an email to the site admin with a special login link.
  • Renaming the plugins folder by FTP turns off every plugin when you cannot reach the dashboard.
  • If the site is down for everyone and the dashboard is also gone, check hosting status, domain renewal and DNS first.

How do you know what is wrong with your WordPress site?

Look at the exact message or behavior first, because each symptom points to a different cause.

Do not start changing settings at random. Write down what you see, when it started and what changed just before. A plugin update, a new theme, a PHP upgrade on the host or an expired card on your hosting account are the usual suspects.

Use this table to match the symptom to the likely cause:

What you seeMost likely causeFirst thing to check
Blank white pagePHP fatal error or memory limitDebug log, plugins
“There has been a critical error”Fatal error in a plugin or themeAdmin email for recovery link
500 Internal Server ErrorServer error, often .htaccess or PHPHost error log
“Error establishing a database connection”Wrong database details or database downwp-config.php, host status
404 on every page except homeBroken permalinksSettings > Permalinks
Too many redirectsWrong site URL or SSL settingSettings > General, host SSL
Site not found or DNS errorDomain expired or DNS changedDomain registrar
“Briefly unavailable for scheduled maintenance”Interrupted update.maintenance file

The WordPress handbook keeps a longer list of common WordPress errors with links to fixes.

Is the WordPress site down for everyone or just for you?

Check on another device and another network first, because a local cache, VPN or firewall can make a working site look broken.

Open the site on your phone with Wi-Fi turned off. Try a private browser window too. If it loads there, the problem is on your side: clear the browser cache, turn off the VPN or flush your DNS cache.

If it fails everywhere, log in to your hosting account. Look for an outage notice, a suspended account or an unpaid invoice. Many hosts suspend sites for billing problems or for using too many resources, and the site then shows a host page instead of WordPress.

Also check that your domain has not expired. An expired domain stops resolving even when the hosting account is fine.

How do you fix “There has been a critical error on this website”?

Open the recovery mode email WordPress sent to the admin address, log in through its link and deactivate the plugin or theme it names.

Since version 5.2, WordPress detects many fatal PHP errors on page load and switches on recovery mode. It emails the site admin a special login link and the name of the plugin or theme that crashed.

In recovery mode, the broken extension is paused only for you. Deactivate it, update it or replace it, then click Exit recovery mode.

If the email never arrives, check spam. If it still is not there, use the manual steps below. Our full guide covers the critical error message in more depth.

How do you turn off all plugins when you cannot log in?

Rename the wp-content/plugins folder over FTP or your host's file manager, which deactivates every plugin at once.

Plugins are the most common cause of a site that suddenly stops working. When the dashboard is down too, do this:

  1. Connect with FTP, SFTP or the file manager in your hosting panel.
  2. Open wp-content.
  3. Rename the plugins folder to plugins-off.
  4. Load the site. If it works, a plugin was the cause.
  5. Rename the folder back to plugins. WordPress now lists every plugin as inactive.
  6. Activate plugins one at a time and reload the site after each one until it breaks again.

The last plugin you activated before the break is the culprit. Keep it off and look for an update or a replacement. The same trick works for themes: rename the active theme's folder and WordPress falls back to a default theme if one is installed.

For a step-by-step version with screenshots of each tool, see how to deactivate all plugins without admin access.

How do you find the real error message?

Turn on WordPress debug logging in wp-config.php and read wp-content/debug.log.

A white screen or a generic error hides the real problem. The WordPress debugging documentation explains three constants that make WordPress record errors without showing them to visitors.

Add these lines to wp-config.php, above the line that says “That's all, stop editing”:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Reload the broken page, then open wp-content/debug.log. The last lines usually name a file and a line number. If the path contains /plugins/plugin-name/, that plugin is the cause.

Set WP_DEBUG back to false when you are done. A public debug.log can expose details about your server.

Your host also keeps a PHP error log, often in the hosting panel under logs. Check it when debug.log stays empty.

What if the site shows a 500 Internal Server Error?

A 500 error means the server failed while building the page, most often because of a corrupt .htaccess file, a PHP fatal error or a memory limit.

HTTP 500 is a generic server response, so the browser cannot tell you more. Work through the common causes:

  • .htaccess: Rename .htaccess in the site root to .htaccess-old. If the site loads, go to Settings > Permalinks and click Save to create a fresh file.
  • Plugins and themes: Use the folder-rename method above.
  • Memory: If the log says “Allowed memory size exhausted”, raise the PHP memory limit or ask your host to.
  • PHP version: A recent PHP upgrade can break old plugins. Check which version your host switched to.

Our dedicated guide to the 500 internal server error goes through each case.

What if WordPress says it cannot connect to the database?

Check the database name, user, password and host in wp-config.php, then confirm with your host that the database server is running.

The message “Error establishing a database connection” means WordPress could not log in to MySQL or MariaDB. The four values in wp-config.php must match what your hosting panel shows: DB_NAME, DB_USER, DB_PASSWORD and DB_HOST.

If the details are right, the database server may be down or overloaded. That is a host problem, so open a support ticket. A corrupted table can also cause it. WordPress has a built-in repair tool you can switch on with define( 'WP_ALLOW_REPAIR', true ); for a short time.

Read the full walk-through on fixing the database connection error.

What if the site loops with “too many redirects” or shows SSL warnings?

Redirect loops usually come from a mismatch between the WordPress Address, the Site Address and how HTTPS is set up on the host or CDN.

Open Settings > General and make sure WordPress Address (URL) and Site Address (URL) both use the same domain and https://. If you cannot reach the dashboard, set WP_HOME and WP_SITEURL in wp-config.php.

Then check the layer in front of WordPress. A CDN set to send plain HTTP to a server that forces HTTPS creates an endless loop. Clear any caching plugin and CDN cache after each change, or you will keep seeing the old redirect.

If the browser warns that the connection is not private, the SSL certificate may have expired. Most hosts renew free certificates automatically, so ask support if it did not happen.

How do you stop your WordPress site from breaking again?

Keep tested backups, update in small steps, and test big changes on a staging copy first.

A few habits prevent most outages:

  1. Take an automatic daily backup and store a copy off the server.
  2. Update plugins one at a time, not all at once, and check the site after each.
  3. Test major updates and PHP upgrades on a staging site.
  4. Remove plugins and themes you do not use.
  5. Run a supported PHP version that your plugins also support.
  6. Use an uptime monitor so you hear about downtime before your visitors do.

If you cannot find the cause after these steps, restore the last working backup and contact your host with the exact error, the time it started and what you changed.

Frequently asked questions

Why did my WordPress site stop working after an update?

An update can bring a plugin or theme that conflicts with another extension, your PHP version or your WordPress version. Turn plugins off by renaming the plugins folder, find the one that breaks the site, then roll it back or wait for a fixed release.

Can a WordPress site go down without any changes?

Yes. Automatic updates, a host PHP upgrade, an expired domain or SSL certificate, a full disk, an unpaid hosting invoice or a server outage can all break a site even when you changed nothing yourself.

How do I get into WordPress if the dashboard is broken?

Use the recovery mode link from the admin email if WordPress sent one. Otherwise connect by FTP or your host's file manager, rename the plugins folder to turn off all plugins, and try logging in again at your login page.

Will I lose my content if my WordPress site breaks?

Usually not. Posts and pages live in the database, and most errors come from code in plugins, themes or settings. Your content is safe unless the database itself is damaged, which is why off-site backups matter.

When should I contact my web host?

Contact your host when the database server is down, the account is suspended, you see server errors with nothing in the logs, or you cannot reach the files at all. Give them the exact error and the time it started.

Sources

  1. Common WordPress errors WordPress Developer Resources
  2. Recovery Mode WordPress.org Documentation
  3. Debugging in WordPress WordPress Developer Resources
  4. 500 Internal Server Error MDN Web Docs
  5. Supported Versions PHP.net

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.