Help with WordPress login usually arrives as a sentence with no details: the site will not let me in. The cause is one of five things, and the order of checks saves an hour of guessing.
The login page is a single door with several locks: the password, the session, the second factor, the address ban and the host. Each one fails differently, and the error message on screen is the first clue.
Start with the exact symptom
A blank page means PHP failed or the host killed the request. A redirect back to the form means the credentials were rejected or the cookie cannot be set. A 403 means the firewall or the host blocked the address before WordPress started. A 500 usually points at a plugin or a broken theme file.
Write down what the browser shows before touching anything. A screenshot of the error is worth more than ten minutes of retyping the password.
The password is wrong, or the account is gone
WordPress tells you which. “The password you entered is incorrect” keeps the account name, while “invalid username” says the login does not exist. The second message is a gift from an old version and a leak of user names, and hiding it is a small hardening step.
Use the password reset link and check the mailbox for the message. If it never arrives, the site’s email is broken, which is a separate problem: an SMTP plugin or a signed domain fixes it.
If the mailbox is also lost, the reset has to happen on the server. WP-CLI can set a password in one command, and the host panel usually offers the same. Both need server access, so the person who asks for help needs it or needs to know who has it.
The password is right and the site still refuses
Three usual suspects. A security plugin banned the address after failed attempts, and the ban outlives the correct password. A cached login page serves a stale nonce, and the form rejects every submission. A cookie domain mismatch, common after a migration from www to the bare domain, keeps the session from starting.
Check in that order: the event log for a ban, the cache for the login page, the site URL in settings for the cookie. Each has a different fix and none of them is a new password.
The second factor blocks the way
A correct password plus a missing code looks like a loop. The code is six digits and changes every thirty seconds, and a phone with a wrong clock produces codes the server rejects.
Try a backup code. Ten are issued at enrollment, each works once, and they are the reason the recovery path exists. If the codes are gone too, a second enrolled device or an administrator reset through the host is the remaining route.
Do not disable the second factor for the whole site to get one person in. Reset that account, or issue a new enrollment link.
The address is banned
A ban is not a bug, it is the ladder doing its job. Five failed logins in fifteen minutes put the address on a slow path, and repeated attempts reach the ban. A shared office address collects failed attempts from everyone behind it.
The event log shows the rule and the address. Removing the rule or waiting for the window to pass both work, and the first one is safer when the person is at the office.
Multisite and staging catch people out
On multisite the login is shared and the roles are per site, so an account can exist without access to the site in question. On staging the database is a copy, and the password may be the old one from before the last sync.
Both cases end the same way: check the network user, then check the site role, then reset. A staging copy also needs its own second factor enrollment, because the secrets come from the copy.
What to fix after the login works
Close the obvious holes while the incident is fresh. Hide the login error that reveals user names. Put a rate limit and a CAPTCHA on the form if they were off. Turn on the second factor for the administrator. Add the person’s address to the allow list if the office is static, and skip that step if it is not.
The next lockout is cheaper when the recovery path is written down: who has server access, where the backup codes are kept, and which mailbox receives the reset.
Questions we hear
Can I log in if I lost the email?
Only through the server or the host panel: WP-CLI, phpMyAdmin or the hosting account. There is no email-free path in WordPress itself.
Why does the form reload and clear?
The nonce expired, usually because the page was cached or left open for days. Clear the cache for that page and reload before typing again.
Is it safe to disable the security plugin to get in?
It works and it opens the site while the plugin is off. Rename the plugin folder through file access instead, then turn it back on after the login.
Why is the admin address different from the site?
The WordPress address and the site address are two settings, and a mismatch after a move breaks both login and links. Set them in the database or in wp-config.php.
Next step
Write the recovery path down before the next lockout: server access, backup codes, mailbox. The two-factor authentication page covers enrollment, the brute force protection page explains the ladder, and the prices name the tier. WordPress documents the reset flow in its password guide.
