Troubleshooting
Why Is Your WordPress Password Not Working? Causes and Fixes

Short answer
A WordPress password usually fails because the username or email is wrong, the password has a typo or autofill error, a security plugin has locked you out, or cookies and caching break the login. Check the account details first, then reset the password by email, WP-CLI or phpMyAdmin.
Key takeaways
- WordPress passwords are case sensitive, so caps lock and autofill cause many failures.
- Security plugins can lock you out even when the password is correct.
- A login page that just reloads points to cookies or caching, not the password.
- Staging, local and live copies each have their own passwords.
- WP-CLI, phpMyAdmin or your host can reset a password without email.
Why is my WordPress password not working?
Your WordPress password usually fails because the username or email is wrong, the password has a typo or hidden character, the account changed, or a cookie, cache or security plugin is blocking the login.
The login form only tells you that something is wrong. It rarely tells you exactly what. That is why a correct password can still look like it fails.
Before you try anything big, confirm which message you see. WordPress words its errors differently depending on whether it recognised the username or not.
| What you see | Most likely cause | First fix |
|---|---|---|
| The username is not registered on this site | Wrong username or email | Try the email address instead |
| The password you entered for the username is incorrect | Typo, old password or saved autofill | Retype it by hand, then reset |
| Login page reloads with no error | Cookies, caching or URL mismatch | Clear cookies, exclude login from cache |
| Too many failed attempts or a lockout notice | Security plugin lockout | Wait, or disable the plugin over FTP |
| Correct password works elsewhere but not here | Different site, staging copy or multisite | Check the exact site URL |
Is the username or email actually correct?
Check the account name first, because WordPress accepts either the username or the email address, and many people mix up the two or use an old email.
WordPress usernames cannot be changed from the profile screen, so the name you picked at install time still applies. If you set up the site long ago, it may be something like admin or your first name.
Try logging in with the email address on the account instead. If WordPress says the email is not registered, the account may use a different address than you think.
If you have lost track of both, our guide on how to find your WordPress username and password walks through the places to look, including your host's dashboard.
Could the password simply be mistyped?
Yes, and this is more common than any technical fault: caps lock, keyboard layout, autofill and pasted spaces all change what WordPress receives.
Passwords in WordPress are case sensitive. A password typed with caps lock on is a different password.
Watch for these quiet mistakes:
- Caps lock or num lock switched on
- A different keyboard layout active, which moves symbols like @ and "
- A space copied at the start or end when pasting from a note
- The browser autofilling an old password saved months ago
- A password manager filling the entry for a different site
Click the eye icon on the login form to show the password as you type. It is the fastest way to spot a stray character.
Did someone change the password or the account?
If the password worked before and now does not, check whether another admin, a plugin or a security event changed it, because WordPress does not change passwords on its own.
On sites with several users, another administrator can edit your profile and set a new password. Some hosts and security services also force password resets after a breach warning.
WordPress normally emails the account owner when a password or email address changes. Search your inbox for a notice like that.
If you suspect someone else got in, treat it as a security issue. Reset all admin passwords, review the user list for accounts you do not recognise, and run a scan. Our guide on how to run a WordPress security audit covers what to check.
Is a security plugin locking you out?
Security plugins often block logins after a few failed tries, and while you are locked out even the correct password will fail or the form will refuse to submit.
Plugins such as Wordfence, Solid Security and Limit Login Attempts style tools count failures per IP address. After a set number they block that IP for a period of time.
Signs of a lockout include a message about too many attempts, a block page, or a login that simply fails no matter what you type.
You have three options:
- Wait for the lockout period to end, then try once, carefully.
- Log in from a different network, such as mobile data, if the block is by IP.
- Rename the plugin's folder in wp-content/plugins over FTP or your host's file manager to switch it off.
Renaming the folder deactivates the plugin without deleting its settings. Rename it back after you log in. If Wordfence is the cause, see our guide on Wordfence blocking admin access.
Two-factor authentication can also look like a password failure. If the plugin asks for a code and you no longer have the device, use the backup codes you saved when you turned it on.
Are cookies or caching breaking the login?
When the password is right but the login page just reloads, cookies or page caching are usually the cause, not the password itself.
WordPress needs cookies to keep you signed in. If your browser blocks them, or an old cookie is stuck, the login succeeds on the server and then immediately looks like it failed.
Try these in order:
- Open a private or incognito window and log in there
- Clear cookies for your site only, then reload the login page
- Disable browser extensions that block cookies or scripts
- Purge your caching plugin and any server or CDN cache
Login pages should never be cached. If a cache plugin or CDN stores wp-login.php, everyone gets a stale form. Our guide to a login page refreshing and redirecting covers this pattern in depth.
A mismatch between http and https, or between www and non-www, also breaks login cookies. Make sure the address in Settings > General matches the one you type.
Are you logging in to the right site?
Many people keep a staging copy, a local copy or an old version of a site, and a password changed on one copy does not change on the others.
Each WordPress install has its own database and its own users table. A password reset on your staging site does nothing for the live site.
Check the address bar carefully. Bookmarks sometimes point to a staging subdomain, a temporary host URL or an old domain that still runs a copy of the site.
On WordPress multisite, a user can exist on the network but not be added to a particular site. The password is correct, yet that site will not let the user in.
How do I reset a WordPress password when it will not work?
Use the Lost your password? link first; if the email never arrives, reset the password with your host's tools, WP-CLI or phpMyAdmin instead.
The normal reset flow sends a link to the account email. You click it and set a new password. The official WordPress password reset documentation lists every method.
If the email does not arrive, see our guide on a password reset email not received.
If the link arrives but fails, the reset password not working guide covers expired and invalid links.
When email is not an option, you can work at the server level:
- WP-CLI: run the wp user update command with a new user_pass value over SSH.
- phpMyAdmin: edit the user's row in the users table and set the password with the MD5 function. Our phpMyAdmin password guide has the full steps.
- Host dashboard: many managed hosts let you reset the admin password from their control panel.
Always back up the database before editing it directly. One wrong field can lock out every user.
Newer WordPress versions store passwords with stronger hashing built on PHP's password_hash function. An MD5 value set in phpMyAdmin still lets you log in once, and WordPress replaces it with a stronger hash after that login.
Can a plugin or code change stop valid passwords from working?
Yes, a plugin that replaces the login process, such as a custom login page, social login or membership plugin, can reject passwords or send you to a page that does not exist.
Custom login URL plugins move wp-login.php to a secret address. If you forget the new address, the old login page may show an error or a 404, which feels like a password problem.
Membership and single sign-on plugins sometimes take over authentication completely. They may check the password against a different system.
To test this, deactivate plugins by renaming the plugins folder over FTP. If login works, rename it back and reactivate plugins one at a time to find the cause. The steps are in our guide on how to fix a plugin conflict.
Developers sometimes hook into the wp_authenticate filter to add rules. A bug in that code can reject every password, so check any custom code in the theme's functions file too.
Why does my new password get rejected when I try to set it?
WordPress itself accepts weak passwords after you confirm the checkbox, but security plugins and hosts can enforce stronger rules that reject passwords without much explanation.
On the reset form, WordPress shows a strength meter. If the password is weak, it asks you to tick a box confirming you want to use it anyway.
Some security plugins remove that option and require a minimum length, mixed characters or a password that has not appeared in known breaches. The Have I Been Pwned password check is one service such plugins use.
Use a password manager to generate a long, random password. It avoids rejection and is far safer than a memorable one.
What should I do if nothing works?
If every reset method fails, contact your host with the site URL and the exact error, because they can check server logs, database access and firewall blocks you cannot see.
Server firewalls such as ModSecurity sometimes block login requests that contain certain characters. Hosts can whitelist your IP or relax a rule.
Before you contact support, gather a few details:
- The exact error message, word for word
- Whether the login page reloads, shows an error or shows a block page
- What you changed recently, such as a plugin update or new password
- Whether the same thing happens in a private window and on another network
With that information, most hosts can find the cause quickly. If you are completely locked out of the dashboard, our guide on being locked out of wp-admin lists every recovery route.
Frequently asked questions
Is the WordPress password case sensitive?
Yes. WordPress treats uppercase and lowercase letters as different characters, so a password typed with caps lock on will fail. Usernames and email addresses are more forgiving, but the password must match exactly.
Why does WordPress say my password is incorrect when I know it is right?
The most common reasons are a saved autofill entry with an old password, an extra space from pasting, a different keyboard layout, or logging in to a staging or old copy of the site that still has a different password.
How long does a WordPress login lockout last?
WordPress core does not lock accounts. Lockouts come from security plugins or the host, and each sets its own duration. Check the plugin settings once you are back in, or ask your host if the block comes from the server.
Can I log in with my email instead of my username?
Yes. The standard WordPress login form accepts either the username or the email address on the account. If one fails, try the other before resetting the password.
Will resetting my password log out other devices?
Often it does, but do not rely on it. After changing the password, open your profile screen and use the Log Out Everywhere Else button to end other sessions. Application passwords used by apps are separate and must be revoked on their own.
Sources
- Reset your password WordPress.org
- wp user update WordPress Developer Resources
- authenticate hook WordPress Developer Resources
- Pwned Passwords Have I Been Pwned
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.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


