Troubleshooting guide Admin Access

WordPress Admin Not Working: How to Get Back Into wp-admin

Locked out of wp-admin or staring at a blank dashboard? Here is the recovery path I run on every client site.

Arjun Mehta Published June 15, 2026 Updated June 18, 2026 8 min read Step-by-step walkthrough

Reviewed and tested by the WPRescue team on a real WordPress install before publishing. How we test fixes

What's Happening

When the admin area refuses to load or login keeps failing, the cause is usually cookies, a plugin, or corrupted core files.

Losing access to /wp-admin is one of the more stressful WordPress problems because it feels like the whole site is broken even when the front end is usually still online. In practice the admin area is a separate set of scripts and any one of them can fail while the public pages keep serving.

The symptom usually falls into one of a few buckets: a blank admin, an infinite login redirect, a permissions error, or a plain 500 on any /wp-admin URL. Each bucket has a short list of realistic causes tied to plugins, themes, cookies, or file ownership.

This guide sorts the fixes by which bucket the symptom fits, so you can jump to the section that matches what you actually see instead of running every fix on the internet in sequence.

Clear Your Browser Cache and Cookies

This is where I always start. Seriously. I can't tell you how many times a frantic client call ended with them sheepishly admitting their browser cache was the culprit. Your browser stores temporary files and cookies to make websites load faster. Sometimes, these cached files get outdated or corrupted, causing issues with how WordPress loads its own admin pages. It's the simplest fix, so it's always the first thing to check.

WordPress uses cookies to manage your login session. If these cookies are messed up, your browser might think you're not logged in, even if you just entered the correct credentials. Or, it might get stuck in a login loop. Clearing your browser's cache and cookies is like giving it a fresh start. It forces your browser to download fresh copies of all website files and reset any session information. This often solves those weird 'redirect loop' issues where you enter your password and just end up back at the login screen.

The process is pretty straightforward, no matter what browser you're using. You usually go into your browser's settings or history, find an option like 'Clear browsing data,' and make sure 'Cookies and other site data' and 'Cached images and files' are selected. Then, try logging in again. If that doesn't work, try a different browser or even an incognito/private browsing window. This bypasses any stored data and gives us a clean slate to test with.

Disable Plugins Through FTP

A huge percentage of the 'WordPress admin not working' calls I've received boil down to a plugin conflict. A newly installed plugin, an update to an existing plugin, or even two plugins that just don't play nice together can crash your admin area. Sometimes, a plugin might even have a bug that only manifests on certain server configurations, locking you out.

The problem is, if you can't get into wp-admin, you can't just go to the 'Plugins' page and deactivate them. This is where FTP or your hosting control panel's file manager comes in handy. You need to access your server's file system directly. What we're going to do is essentially rename the 'plugins' folder. WordPress won't be able to find any plugins then, effectively deactivating all of them.

To do this, connect to your site via FTP. I usually use FileZilla. Navigate to `wp-content`. Inside `wp-content`, you'll see a folder named `plugins`. Rename this folder to something like `plugins_old`. Now, try accessing your wp-admin. If you can log in, we've found our culprit. You'll see a bunch of notices about plugins being deactivated because their folder disappeared.

bashRenaming your plugins folder via command line SSH. Replace `wp-content/plugins` with `wp-content/plugins_old` to disable all plugins at once. If you use an SFTP client (like FileZilla), you'll navigate to the `wp-content` directory and rename the folder directly.

mv wp-content/plugins wp-content/plugins_old

Isolate the Problem Plugin

Okay, so you've renamed `plugins` to `plugins_old`, and suddenly you're back in your WordPress admin. Great news, a plugin was causing the issue. Now, we need to figure out which one. Go back to your FTP client and rename `plugins_old` back to `plugins`. Don't log out of wp-admin yet.

Now, inside the `wp-content/plugins` folder, you'll see individual folders for each plugin. Here's the tedious part, but it's necessary: you need to deactivate them one by one. Or, more accurately, reactivate them one by one until the admin breaks again. I usually start by renaming the first plugin folder to `plugin_name_temp`, then trying to access wp-admin. If it works, rename it back, and move to the next. The alternative is to go to your WordPress admin's 'Plugins' page and activate them one by one.

Once your admin breaks again after activating a specific plugin, you've found the problematic one. At this point, you have a few options. Delete the plugin if it's not essential. Look for an alternative. Check the plugin's support forums for known issues or updates. Sometimes it's a conflict with your theme or another plugin that you'll need to report to the plugin developer.

Switch to a Default Theme via FTP

Just like plugins, your WordPress theme can cause problems with the admin area. A poorly coded theme, a theme update gone wrong, or a conflict with a plugin can all lead to a blank white screen or a broken layout in wp-admin. The process for checking this is similar to how we handled plugins.

You'll need FTP access again. Navigate to `wp-content/themes`. Inside, you'll see folders for all your installed themes. WordPress requires at least one default theme like Twenty Twenty-One or Twenty Twenty-Four to function correctly. The trick here is to force WordPress to fall back to one of its default themes.

My usual method is to rename the currently active theme's folder. For example, if your active theme is 'my-custom-theme', rename its folder to `my-custom-theme_old`. WordPress will then look for an available default theme and activate it. If you can suddenly access your admin, then your theme was the issue. You'll need to investigate the theme, contact its developer, or consider switching to a different theme.

Check for Corrupted Core WordPress Files

Sometimes, the core WordPress files themselves can become corrupted. This can happen during a bad update, a botched file transfer, or even if your hosting server experiences an issue. When core files are damaged, WordPress can't function properly, and that includes your admin area. This is a bit more involved, but it's a proven method for getting a broken site back online.

The way we fix this is by replacing your current WordPress core files with a fresh set from WordPress.org. Don't worry, this won't affect your content, plugins, or themes. Those are stored in the `wp-content` folder and your database. We are only replacing the files that make WordPress itself run.

Here's the process: Download the latest version of WordPress from wordpress.org. Extract the zip file. Now, connect to your server via FTP. Delete the `wp-admin` and `wp-includes` directories on your server. Then, upload the fresh `wp-admin` and `wp-includes` folders from your downloaded WordPress package. Also, upload all the individual files from the root of the new WordPress package to your site's root, overwriting any existing ones. Be careful NOT to overwrite your `wp-config.php` file or your `wp-content` folder.

Reset WordPress Password Via phpMyAdmin

One of the most common reasons for being locked out of wp-admin is a forgotten password. Or, perhaps, you've inherited a site, and no one remembers the admin credentials. The standard password reset link often fails to send emails due to server mail issues or plugin conflicts. When that happens, we need to go directly to the source: the database.

Your WordPress user information, including your password, is stored in your site's database. We can directly edit this through phpMyAdmin, which is usually accessible through your hosting control panel. It's a bit intimidating at first, but it's a lifesaver when you're locked out.

Log into phpMyAdmin. Select your WordPress database from the left sidebar. Then, find the `wp_users` table. (Note: your table prefix might be different, like `wp2a_users`). Click 'Browse' or 'Select * from table' to see the users. Find your username, then click 'Edit' for that row. In the `user_pass` field, enter your new password. IMPORTANT: In the 'Function' dropdown, select 'MD5'. This encrypts your password properly. Save the changes, and you should now be able to log in with your new password.

Check for .htaccess Issues

The `.htaccess` file is a powerful configuration file that tells your web server how to behave. It handles permalinks, redirects, security rules, and more. A misconfiguration in `.htaccess` can easily block access to your entire site, including the wp-admin area. This often happens after manual edits, plugin installations that modify `.htaccess`, or migration issues.

If you're getting 'Internal Server Error' (500 error) or unusual redirect loops, your `.htaccess` file is a prime suspect. To check if it's the problem, connect to your site via FTP. The `.htaccess` file is usually in your WordPress root directory. It's a hidden file, so make sure your FTP client is set to show hidden files. Download a copy of your `.htaccess` file to your computer as a backup. Then, simply delete the `.htaccess` file from your server.

Now, try to access your wp-admin. If you can get in, then the `.htaccess` file was indeed the problem. Don't leave it deleted. Go to Settings > Permalinks in your WordPress admin and just click 'Save Changes' without making any actual changes. This will regenerate a fresh, default `.htaccess` file. You may need to manually add back any custom rules you had, like redirects, from your backup.

Security Plugin Lockout

I've had clients completely lock themselves out of their sites with security plugins. These plugins are fantastic for protecting your site, but their very job is to be aggressive. If you enter incorrect login details too many times, or if your IP address gets flagged for suspicious activity, a security plugin like Wordfence or Sucuri can easily block your access. This is particularly frustrating because you can't get into the admin to disable the plugin.

When a security plugin locks you out, you'll often see a message about your IP being blocked, or a generic 'Forbidden' error (403). The fix involves getting into your server files via FTP or your hosting control panel's file manager and temporarily disabling the plugin. Usually, you'd go to `wp-content/plugins` and rename the specific security plugin's folder (e.g., `wordfence` to `wordfence_old`).

If renaming the plugin folder doesn't work, sometimes these plugins add rules to your `.htaccess` file or even PHP files outside the plugin directory. You might need to check your `.htaccess` for rules added by the security plugin and remove them, or consult the plugin's documentation for manual removal steps. Some plugins also have a 'recovery mode' through specific URLs or database entries, but renaming the plugin folder is always the first step.

Complete Fix Checklist

1Clear all cookies for the site and try incognito.
2Reset the password via 'Lost your password?'
3Disable plugins by renaming /wp-content/plugins via FTP.
4Switch themes by renaming the active theme folder.
5If admin still fails, re-upload fresh /wp-admin and /wp-includes from a clean WordPress download.

Quick Tips

Never delete /wp-content during recovery
Avoid changing files via the WordPress editor while debugging

Frequently Asked Questions

What if I can't access FTP?

If you can't access FTP, your first step is to contact your hosting provider. They can help you reset your FTP credentials or provide you with access to their file manager, which is a web-based interface for managing your server files. They might also be able to check server logs for specific errors.

My site is showing a blank white screen, what does that mean?

A blank white screen, often called the 'White Screen of Death,' usually indicates a fatal PHP error. This often means a plugin or theme is causing a critical error. To diagnose, you'll need to enable WordPress debugging. Edit your `wp-config.php` file and change `define('WP_DEBUG', false);` to `define('WP_DEBUG', true);`. This might show error messages instead of a blank screen, pointing you to the problematic file or line of code. Remember to turn debug mode off after you're done troubleshooting.

Could my host be blocking my access?

Yes, absolutely. Your hosting provider might block your IP address if they detect suspicious activity, or if there's a firewall rule in place. Sometimes, it's also a server-side issue like low PHP memory limits. Contacting your hosting support is a good step to rule out any server-related issues or IP blocks. Provide them with your IP address and the exact error you're seeing.

What's the difference between FTP and SFTP?

FTP (File Transfer Protocol) is a standard protocol for transferring files. SFTP (SSH File Transfer Protocol) is a more secure version that encrypts both the commands and the data, preventing eavesdropping and tampering. Whenever possible, I always recommend using SFTP for better security. Most modern hosting providers support SFTP, and you can usually connect using the same credentials as FTP, but with a different port (often port 22).

Should I backup my site before trying these fixes?

YES, absolutely, 100% of the time. Before you make any significant changes to your WordPress site files or database, always create a full backup. Most hosting providers offer backup solutions, or you can use a plugin if you can access your admin. If you can't access admin, contact your host to see if they have recent backups you can restore, or if they can perform a manual backup for you. It's your safety net.