WordPress Login Page Not Working? 9 Fixes to Get Back In

Being locked out of your own website is stressful. You enter your username and password, press enter, and the wordpress login page not working problem greets you instead: a blank white page, a loop back to the login form, or a browser error about too many redirects. Your content is still there, but you cannot reach your dashboard.

The good news: the cause is usually small — a bad browser cookie, a faulty plugin, one bad line in a configuration file, or a site address that no longer matches. Work through these 9 fixes in order, simplest first. Most readers get back in within the first three.

• Quick Checks — Do These First
• Diagnose Table: Symptom, Cause and Fix
• 1. Clear Your Browser Cache and Cookies
• 2. Disable Your Plugins Through FTP
• 3. Check Your .htaccess File for Bad Rules
• 4. Fix the Site Address After a Migration or SSL Change
• 5. Clear Your Server and CDN Cache
• 6. Switch to a Default Theme Through FTP
• 7. Reset Your Password the Proper Way
• 8. Check File Permissions
• 9. Still Seeing the wordpress login page not working? Ask Your Host
• What to Avoid
• FAQ
• Conclusion

Quick Checks

• Is the whole site down, or just the login page? Open your homepage in a new tab. If the homepage loads but wp-login.php does not, the fault is localised to the login process, and fixes 1 to 4 will most likely solve it.
• Try the direct login address. Type yourdomain.com/wp-login.php instead of /wp-admin. A broken redirect can make wp-admin fail while the direct page works.
• Think about what changed recently. A migration, a new SSL certificate, a plugin or theme update, or a new security plugin almost always precedes login trouble. Naming that change points straight at the fix.
• Ask another admin to try. If a colleague can log in from their device, the fault is in your browser or network. If nobody can log in, the fault is server-side.
• Disconnect your VPN and check the exact error. Some VPNs and office firewalls block login cookies. A blank page, “too many redirects”, a 404, and a silent refresh are four different symptoms with four different fixes, mapped in the table below.

Diagnose Table

Symptom	Likely cause	Go to fix
Blank white page on wp-login.php	PHP fatal error from a plugin or theme	Fix 2, Fix 6
Correct details entered, then returned to the login form	Login cookie blocked, or site address mismatch	Fix 1, Fix 4
“Too many redirects” or ERR_TOO_MANY_REDIRECTS	Bad .htaccess rule, SSL mismatch, or wrong site URL	Fix 3, Fix 4, Fix 5
404 error on wp-login.php	Security plugin renamed the login URL, or a missing file	Fix 2
“ERROR: Cookies are blocked or not supported by your browser”	Browser blocking cookies, or cookie settings misconfigured	Fix 1
Correct password rejected every time	Wrong username stored, or password needs a proper reset	Fix 7
Login page loads slowly, then fails	Server-side error or security rule blocking the request	Fix 9

1. Clear Your Browser Cache and Cookies

A large share of wordpress login page not working cases come down to a corrupt login cookie or a cached copy of the login page. WordPress logs you in by setting a cookie in your browser. If that cookie is damaged, expired, or blocked, the form simply refreshes instead of letting you in. Rule this out first. It takes two minutes.

Clearing the site’s cookies and cached files is the fastest first fix when the wordpress login page not working problem is browser-side.

1. Clear cookies and cached data for your site. In Chrome, go to Settings, then Privacy and security, then “Delete browsing data”. In Firefox, use Settings, then Privacy and Security, then “Clear Data”.
2. Close the tab fully, then reopen the login page. Do not just press refresh. A closed tab forces the browser to fetch a fresh copy of wp-login.php.
3. Try an incognito or private window. Incognito loads the page with no cookies, extensions, or cache. If the login works there, your normal browser profile is the problem.
4. Try a different browser. If Chrome fails but Firefox works, the issue sits in one browser. For general Chrome page problems, see our guide to Chrome pages not loading.
5. Allow cookies and disable interfering extensions. WordPress cannot log you in if your browser blocks cookies. Check the cookie icon in the address bar, and temporarily disable ad blockers or privacy extensions for your site.

If the login works in incognito but not in your normal window, finish clearing the normal profile and remove any extension that blocks scripts or cookies on your domain.

2. Disable Your Plugins Through FTP

If the browser is innocent, a plugin is the next suspect. Security plugins such as Wordfence and iThemes Security are the most common offenders because they directly touch the login process. Redirect plugins, caching plugins, and login customisers can also break wp-login.php. You cannot reach the dashboard to disable them, so do it through FTP.

1. Connect with an FTP client. Use FileZilla or your host’s file manager with the FTP details from your hosting account.
2. Open /wp-content/ and rename the plugins folder to plugins-disabled. This deactivates every plugin at once without deleting anything.
3. Try the login page. If wp-login.php now works, a plugin was the cause.
4. Rename the folder back to plugins. The plugins return deactivated.
5. Reactivate plugins one by one. Log in and reactivate each in turn, testing the login page after each. When it breaks again, you have found the culprit; keep it deactivated and look for an update or alternative.

One special case: iThemes Security can rename your login URL entirely, so a 404 may mean the page moved to a custom address. Check the plugin’s settings or your notes. If renaming the plugins folder changes nothing, rename it back and move on to fix 3.

3. Check Your .htaccess File for Bad Rules

The .htaccess file controls how the server handles requests, including redirects. Security plugins often add rules to it, and one bad rule can loop the login page or block it outright. If the wordpress login page not working problem began right after installing or configuring a security plugin, this fix is very likely the answer.

A single bad redirect rule in .htaccess can break the login page — checking this file fixes many wordpress login page not working cases.

1. Download a backup of the current file. Find .htaccess in your site’s root folder through FTP. Enable “show hidden files” in your FTP client if you cannot see it.
2. Look for suspicious rules. Focus on blocks added by security plugins, rules mentioning wp-login, and HTTP-to-HTTPS redirects written the wrong way. These are the classic cause of “too many redirects”.
3. Replace the file with the default WordPress rules. The official defaults are published in the WordPress .htaccess documentation. Delete the file’s contents, paste the default block, and save.
4. Test the login page immediately. If it works, the old rules were the problem. Re-add custom rules one section at a time, testing after each, to identify the bad one.

Always keep a backup of the original file so you can compare and restore.

4. Fix the Site Address After a Migration or SSL Change

WordPress stores your address in two settings: WordPress Address and Site Address. If they do not match the address you actually use, login breaks. This follows site migrations, domain changes, and SSL installations where the site still thinks it lives at http:// while you visit https://. The result is the classic loop back to the login form.

A redirect loop that keeps returning you to the login form is often caused by a site address mismatch — a common wordpress login page not working trigger after migrations.

1. Open wp-config.php through FTP. It sits in the site root. Download a backup copy first.
2. Find the WP_HOME and WP_SITEURL lines. They look like define( 'WP_HOME', 'https://yourdomain.com' );.
3. Check both match your real address exactly. The protocol matters: https:// and http:// are different addresses to WordPress, as are www and non-www.
4. Fix any mismatch, or add the constants if missing. Place both define lines just above the “That’s all, stop editing!” line. Defining them in the file overrides stale values left in the database by a migration.
5. Clear your browser cookies once more, then test. The old redirect may still be cached, so repeat the cookie clear from fix 1 before judging the result.

If you recently installed SSL, check redirects are not forced twice, for example in both .htaccess and a plugin. Double redirects commonly cause the “too many redirects” error.

5. Clear Your Server and CDN Cache

Caching layers sit between your browser and WordPress: your host’s page cache, a caching plugin’s stored pages, and a CDN such as Cloudflare. If any of them serves a stale or corrupt copy of the login page, you get the wordpress login page not working problem even though WordPress itself is fine. Clear every layer so you reach the real, live page.

1. Purge your hosting cache. Most managed hosts have a “Purge cache” button in the control panel or admin bar. If your host uses object caching such as Redis or Memcached, ask support to flush it.
2. Purge your CDN cache. In Cloudflare, go to Caching, then Configuration, and choose “Purge Everything”.
3. Pause Cloudflare to test. Under Overview, use “Pause Cloudflare on Site” to route traffic directly to your server. If the login works while paused, a Cloudflare rule or cache setting is the cause. Re-enable it afterwards and adjust the rules.
4. Check for aggressive page rules. A rule that caches everything, including wp-login.php and wp-admin, breaks logins. Login and admin pages must always bypass the cache.

CDN purges can take a few minutes, so test in a fresh incognito window after a short wait.

6. Switch to a Default Theme Through FTP

A broken theme can crash the login page as easily as a broken plugin. The usual culprit is a bad edit to the theme’s functions.php, which runs on every page load including wp-login.php. One PHP error there produces the blank white page. Switching to a default theme through FTP removes the suspect theme from the picture.

1. Open /wp-content/themes/ through FTP. You will see a folder for your active theme plus any others installed.
2. Rename your active theme’s folder, for example mytheme to mytheme-disabled. WordPress detects the missing theme and falls back to a default theme such as Twenty Twenty-Four, if one is installed.
3. Try the login page. If it loads, your theme was the problem.
4. Inspect functions.php for recent edits. Open it and check the end of the file. Remove the recent addition, or restore the file from a backup or a fresh copy of the theme.
5. If no default theme exists, upload one. Download a default theme from wordpress.org into /wp-content/themes/, and WordPress will use it automatically once your broken theme is renamed.

If the theme itself is faulty rather than your edit, ask the theme developer for a proper fix.

7. Reset Your Password the Proper Way

Sometimes the login page works fine and the credentials are the problem. Before assuming anything complicated, reset your password through the official channel. Many “login not working” reports end here: the password was changed, the username was slightly different, or the account email was never confirmed.

When the page loads but your details are rejected, a proper password reset solves the wordpress login page not working complaint fast.

1. Use the “Lost your password?” link. Enter your username or email and follow the emailed link. Check spam or junk if it does not arrive within a few minutes.
2. Type the username by hand. A trailing space copied from a password manager fails silently. Type it once carefully to be sure.
3. Save the new password immediately. Let the reset form generate a strong password and store it in your password manager.
4. If the reset email never arrives, ask your host. Some servers block outgoing WordPress emails. Your host can confirm whether the email left the server, and an SMTP plugin fixes delivery permanently.
5. Only as a last resort, reset through the database. In phpMyAdmin, open wp_users, find your account, and set a new user_pass value with the MD5 function. Back up the database first. The official password reset documentation describes the safe methods in order, so follow that sequence.

Never use password-reset instructions copied from a random forum. Stick to the official methods above.

8. Check File Permissions

Every file and folder on your server has permissions controlling who can read, write, and execute it. Wrong permissions can stop the server serving wp-login.php at all, giving a blank page or a 403 error. This often follows a migration, a backup restore, or an overzealous “security hardening” script.

1. Confirm the standard values. Folders should be 755 and files 644. These are the WordPress recommended values.
2. Verify wp-login.php, index.php, and wp-admin specifically. The login process touches several files, so the whole chain must be readable by the web server.
3. Fix permissions through FTP or cPanel. In FileZilla, right-click, choose File permissions, set 755 applied recursively to directories only, then 644 for files only. cPanel’s File Manager offers the same options.
4. Keep wp-config.php stricter. This file holds your database password. Use 600 or 640, and never 777, which is a serious security risk.

If permissions keep reverting, ask your host. Some server configurations reset them automatically.

9. Still Seeing the wordpress login page not working? Ask Your Host

If all eight fixes failed, the problem is almost certainly on the server itself. Your host’s support team has tools you do not: server error logs, firewall configurations, and the ability to change server-level security rules.

1. Ask support to check the PHP error log. A fatal error logged when you load wp-login.php names the file and line causing it. This is the most useful diagnostic step at this stage.
2. Ask about mod_security rules. This server firewall sometimes blocks legitimate login requests that look suspicious. Your host can check the audit log and whitelist the blocking rule.
3. Ask whether anything changed on the server. PHP version upgrades, new firewall policies, or resource limits can break a login page overnight with nothing changed in WordPress.
4. Confirm your PHP version is supported. A very old or very new PHP version paired with outdated WordPress or plugins can produce blank pages. Hosts can switch PHP versions in minutes.

Tell support which fixes you already tried. Listing them gets a useful answer far faster than “my login is broken”.

What to Avoid

Never share your admin username and password with strangers who offer to “fix it for you” in comments, forums, or direct messages. A legitimate helper never needs your live admin credentials.

Never install nulled or pirated security plugins. They frequently contain malware that hijacks the login page, and they are a common root cause of exactly this problem.

Never edit the database without a full backup. Export the database first, every single time. One wrong value in the users or options table can lock out every account.

Do not rename wp-login.php yourself. Manual renames break updates and plugins; use a reputable security plugin’s proper feature for a custom login URL.

Do not leave all plugins disabled permanently. Renaming the plugins folder is a diagnostic step, not a solution. Find the faulty plugin and replace it.

Do not hammer the login form with repeated attempts. Security plugins and hosts temporarily block IP addresses after several failed logins, turning a small problem into a lockout.

FAQ

Why does WordPress keep sending me back to the login page after I enter correct details?

This is almost always a cookie problem or a site address mismatch: your browser is not storing the login cookie, or WordPress sets it for a different address. Clear your site cookies (fix 1), then check WP_HOME and WP_SITEURL (fix 4). One of those two solves it in most cases.

I see “ERROR: Cookies are blocked or not supported by your browser”. What should I do?

Allow cookies for your site and disable blocking extensions, then try an incognito window. If the error persists across browsers, a plugin or misconfigured COOKIE_DOMAIN is interfering. Disable plugins through FTP (fix 2) and test again.

Can I log in if my security plugin changed the login URL?

Yes — the page has moved, not broken. iThemes Security’s “hide backend” feature changes wp-login.php to a custom address. Check the plugin’s settings or your notes. If nobody knows it, rename the plugins folder through FTP (fix 2), log in, and set a new custom URL you will remember.

Will renaming the plugins folder delete my plugins or their settings?

No. Renaming only deactivates the plugins. All files and database settings stay in place. Rename the folder back and reactivate each plugin from the dashboard.

I reset my password but still cannot log in. Why?

Check the username is correct, typed by hand with no extra spaces, and that you completed the reset through the emailed link. If the email never arrived, your server may not send mail; your host can confirm, and an SMTP plugin fixes delivery.

Should I reinstall WordPress to fix the login page?

Reinstalling is rarely necessary and should be a last resort. The nine fixes above resolve the problem in nearly every case without touching your content. Only consider a reinstall after your host confirms a corrupted core installation, and only with a full backup in place.

Conclusion

A wordpress login page not working error feels alarming, but it is one of the most fixable problems in WordPress. Work through the fixes in order: clear the browser, disable the plugins, check .htaccess and the site address, clear the caches, test the theme, reset the password, verify permissions, and finally ask your host.

For more step-by-step troubleshooting, browse our blog, learn more about TechSBSInfo, or return to the homepage.