wp-admin not working? Run the front door test first

Updated October 30, 2026

When wp-admin won't load, the fix is usually 5 to 15 minutes of work in your host's file manager, and it starts with a 10-second test.

Open your homepage in a private browser window. That's the front door test.

• If the homepage loads but wp-admin doesn't, the problem is narrow. Usually a plugin, a login redirect or a memory limit that only the admin hits.
• If the homepage is broken too, it's the whole site. Head to the white screen guide or the database fix below.

Whether the homepage is working or not splits the problem in two, and it also decides whether an AI assistant can help at all.

You'll need one thing for most fixes: access to your files through your host's file manager or SFTP. If you don't have it, your host's support can do these steps for you.

"There has been a critical error on this website"

Since WordPress 5.2, this is what a fatal error usually looks like. When a plugin or theme throws a fatal error, WordPress shows this message and emails the site's admin address a special link into recovery mode.

1. Check the inbox for the admin email (and spam). The subject mentions your site having a technical issue.
2. Click the recovery mode link and log in.
3. WordPress pauses the plugin or theme that caused the error, for you only, and tells you which one it was.
4. Deactivate it, or update it if an update fixes the bug.

Recovery mode only pauses the broken plugin in your browser. Visitors still see the error until you deactivate it.

No email? Some hosts don't send mail reliably. Skip to the plugin fix below.

White screen or errors only in wp-admin: turn off plugins by hand

This is the official fix when you can't reach the admin screens.

1. Open your file manager or SFTP and go to wp-content.
2. Rename the plugins folder to plugins_old.
3. Try wp-admin again.

If it loads, a plugin was the problem. Rename the folder back to plugins, then rename plugin folders inside it one at a time (add -off to the name) until wp-admin breaks again. The last one you renamed is the culprit.

If it still doesn't load, try the theme. Rename your active theme's folder in wp-content/themes, and WordPress falls back to a default theme like Twenty Twenty-Five if one is installed.

To see the actual error instead of guessing, add these lines to wp-config.php above the line that says to stop editing:

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

Errors then go to wp-content/debug.log instead of the screen. Turn it back off when you're done.

The login page keeps reloading, or "too many redirects"

You type your password, the login page comes back empty, and nothing happens. Or the browser gives up with a redirect error.

Most of the time, the site's two addresses disagree with the URL you're on: http vs https, or www vs no www. Fix it by pinning both in wp-config.php:

define( 'WP_HOME', 'https://example.com' );
define( 'WP_SITEURL', 'https://example.com' );

Use your real address, exactly as visitors should see it. These override the values in the database without changing them. Then clear your browser's cookies for the site and log in again. If you just moved the site to a new address, the domain change guide covers the rest.

wp-admin or wp-login.php shows a 404

If the rest of the site works, a security plugin has probably moved your login page to a custom address. Find that address in your notes or the plugin's settings email. Or rename that plugin's folder in wp-content/plugins to switch it off, and /wp-login.php works again.

"Briefly unavailable for scheduled maintenance"

An update got interrupted and left a .maintenance file in your site's root folder, the same folder that holds wp-config.php. Delete it and reload. If you meant to put the site in maintenance on purpose, the maintenance mode guide shows the proper way.

"Allowed memory size exhausted" in the admin

wp-admin needs more memory than the front end. WordPress gives the admin up to 256 MB by default, unless your host caps PHP lower. If the error only appears in wp-admin, ask your host to raise the PHP memory limit, or set it in wp-config.php:

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

That only works if your host allows WordPress to raise the limit. If it doesn't, it's a ticket to your host.

"Error establishing a database connection"

This one breaks the front door test too, since nothing loads without the database. WordPress's own docs say it's usually a mistake in wp-config.php. Check DB_NAME, DB_USER, DB_PASSWORD and DB_HOST against your host's database settings. If they're right, the database server itself may be down or over quota, and that's for your host.

When an AI assistant can and can't help

If the front door test fails and the whole site is down, Kitepod can't help. It works through a plugin on your site, and if that plugin can't answer, there's nothing for the assistant to talk to. You need your host or SFTP, and the steps above.

If only wp-admin is broken, the plugin may still answer. When it does, you can ask from Claude or ChatGPT:

Kitepod can read the last fatal error, recovery mode and paused plugins, Site Health results and the tail of the debug log with secrets masked. Rolling back a plugin takes a checkpoint first, so you can undo it.

You connect a site to Kitepod from inside wp-admin, so if wp-admin broke before the site was ever connected, this route isn't open to you.

Finer points

Why is wp-admin not working when my site is working?

Usually a plugin that only runs in the admin, a login redirect problem between http and https, a security plugin that moved the login page, or the admin running out of memory. Each has a fix above.

How do I get into wp-admin without logging in?

You can't skip the login. But if a plugin is blocking it, renaming wp-content/plugins in your file manager turns every plugin off without logging in, and the recovery mode email gives you a working login link after a fatal error.

Will renaming the plugins folder delete my plugin settings?

No. Settings live in the database. Renaming the folder only switches the plugins off. When you rename it back, you may need to reactivate them in Plugins.

What if I forgot my wp-admin password?

Click "Lost your password?" on the login screen and WordPress emails a reset link to your account's address. If email doesn't arrive, your host can reset it for you.

Once you're back in, set WP_DEBUG to false again and delete wp-content/debug.log. On many servers anyone who guesses that address can read it.