AI, Development & Tech

WordPress emergency: What to do when your website suddenly goes down?

261106 WordPress emergency website down cover image
Skip to table of contents
Contents 6 sections
  1. What do you do in the first few minutes?
  2. White page after an update: How do you get back in?
  3. What should you do if the website has been hacked?
  4. Lost admin access: Which ways lead back?
  5. When is professional help worthwhile?
  6. What this means for you

In the evening you quickly updated three plugins, and the next morning the first customer gets in touch: the website now shows only a white page. No menu, no contact form, and even the login to the dashboard leads nowhere. Anyone who frantically installs more updates or deletes files at this moment can quickly turn a small error into a big one.

Most WordPress outages follow a few patterns. A plugin or theme doesn't get along with the rest after an update, the connection to the database drops, someone has gained access, or you simply can no longer get into the backend. For each pattern there is a first step you can manage even without programming knowledge.

This guide shows what to do in the first few minutes, how to get a crashed or hacked installation back under control, how to recover a lost admin access, and when outside help is worthwhile.

What do you do in the first few minutes?

First back up and write things down, then repair. After an attack, the WordPress documentation explicitly advises staying calm and documenting the incident, and the same sequence helps with any kind of outage.

The first minutes after the outage
Sequence based on the recommendations of the WordPress documentation
  1. Write it downwhat you see, since when, and what you last changed
  2. Back upcopy files and database exactly as they are right now
  3. Roll backundo the last change, for example by disabling a plugin
  4. Askclarify with your host whether the server or only your website is affected
Source: WordPress documentation

First note what you see, since when the error has occurred, and what you last changed: a new plugin, an update, an adjustment to the theme. You will need this note later, whether you repair it yourself or hire someone.

Then you copy the files and database exactly as they are right now, even if the website is broken. If something goes wrong during the repair, you at least have the state from before your intervention. Many hosts offer a one-click backup for this in the customer area.

Only then do you undo the last change. If the error is not obviously on your side, a short inquiry to the host is worthwhile: they can see whether the server itself has problems, and in the event of an outage of the whole server they can do more than you can.

White page after an update: How do you get back in?

Usually via recovery mode, which WordPress has included since version 5.2. If a plugin or theme crashes with a fatal error, WordPress shows visitors an error message and sends an email to the website's admin address. It states which extension triggered the error and includes a link to recovery mode.

You log in via this link while WordPress pauses the faulty extension. This applies only to your browser; all other visitors continue to see the error page. In the dashboard you deactivate the plugin or switch the theme, then you end the mode using the button in the toolbar.

If no email arrives because the admin address is outdated or the server doesn't send emails, you disable the plugins manually. You connect via FTP or through your host's file manager, open the wp-content folder, and rename the plugins folder to plugins.hold. If you then open the plugin page in the dashboard, WordPress deactivates all plugins it can no longer find. Afterwards you rename the folder back and reactivate the plugins one by one until the error occurs again. The plugins' settings are preserved in the process.

If that doesn't help, the error log will tell you more. In the wp-config.php file you turn on debug mode with WP_DEBUG and the log with WP_DEBUG_LOG, which WordPress then writes to the debug.log file in the wp-content folder. Set WP_DEBUG_DISPLAY to false so that the messages do not appear on the website visible to everyone. The mode is not intended for continuous operation of a public website, so turn it off again after troubleshooting.

If the website shows a message instead of the white page saying there is no connection to the database, the problem lies elsewhere. Then usually the access credentials in wp-config.php are no longer correct, or the host's database server is unreachable. You can clarify both fastest with your host's support.

What should you do if the website has been hacked?

Block all access, restore a clean version and only then close the vulnerability. According to the WordPress documentation, you can recognize an attack by typical signs: Google or Bing warn about your site, the host has blocked it, visitors report warnings from their virus scanner, or user accounts appear that you did not create.

Where the vulnerabilities in WordPress are located
Newly disclosed security vulnerabilities in 2025 according to Patchstack
  • 11.334new vulnerabilities in core, plugins and themes
  • 91 %of them in plugins
  • 6in the WordPress core itself
  • 46 %without a security update at the time of disclosure
Source: Patchstack

Most vulnerabilities are found in the extensions. The security company Patchstack counted a total of 11,334 newly disclosed vulnerabilities related to WordPress in 2025, 91 percent of them in plugins, the rest in themes, and only 6 in the WordPress core itself. For 46 percent, no security update from the developer was available at the time of publication. An update alone therefore does not always protect you, whereas a plugin you don't need at all is always an unnecessary risk.

After an attack, you change all passwords, not just the one for WordPress: also those for FTP or SFTP, for the host's customer area and for the database, and for all users with access. New security keys in the wp-config.php log out everyone who is still logged in. The WordPress documentation recommends changing the passwords a second time after the cleanup, because as long as the website is not clean, the new passwords can also be intercepted.

If you have a backup from a day before the attack, you restore it and then update WordPress, plugins and themes. Without a clean backup, it gets laborious: The folders wp-admin and wp-includes can be replaced with fresh files of the same WordPress version, but the wp-content folder contains themes, plugins and uploads that you have to check file by file. According to the WordPress documentation, the .htaccess file is a particularly frequent target. Also check your own computer for malware, because the stolen credentials often originate from there.

Lost admin access: Which ways lead back?

The simplest way is the "Lost your password" link on the login page. WordPress then sends an email to the address of your user account, through which you set a new password.

If the email doesn't arrive or the address is no longer correct, you go through the database. Most hosts provide phpMyAdmin or Adminer for this. In the table wp_users, you enter an email address that you have access to for your user, and then request a new password via "Lost your password". This way you don't have to deal with encrypted passwords.

If an attacker has taken over your account and changed the permissions, a new password is not enough. Then the procedure from the previous section applies, and you check in the user management which accounts have administrator rights.

When is professional help worthwhile?

As soon as the website earns money and you cannot narrow down the error within an hour. A shop that is unreachable for a day costs revenue, and a hacked site can additionally be flagged as unsafe by search engines. Then there are cases where you simply lack the tools: no FTP access, no backup, a database you have never opened.

Anyone who doesn't want to work through error logs and database tables on their own gets WordPress emergency help on board, which cleans up a crashed or hacked installation and brings it back online. Pass on your notes from the first few minutes and clarify in advance who gets which access.

You can also use a free basic check for possible security vulnerabilities, so you know where your website stands before an emergency occurs.

After any external intervention, change the passwords you handed out for it. This is not distrust, but the same rule as after an attack: Every access that is no longer needed gets closed.

What this means for you

Most emergencies are only half as bad if two things are in place: a current backup and an admin address that you actually read. We consider prevention the most important work on any WordPress website, more important than any new plugin.

  • Plan backups: The WordPress documentation recommends weekly backups for small websites, daily ones for active sites, and always one before every update. Keep several versions in different places, such as with your host, in cloud storage, and on your computer.
  • Check the admin address: Look under Settings, General to see whether there is an address there that you read regularly; the email for recovery mode is sent to it.
  • Clear out plugins: Delete everything you don't use, and keep the rest up to date.
  • Secure access: long, unique passwords from a password manager and two-factor authentication for all admin accounts.
  • Create an emergency sheet: Store your host login, FTP details, and the contact for emergencies in a place you can reach even without your website.

How to create a backup and restore it in an emergency is shown in the lesson Create and restore a backup with Duplicator.

You can find an overview of securing a new installation in the lesson Security and Backups from the course WordPress for Beginners.

Comments

Register and comment.

Continue reading

You might also like

View all articles →