Troubleshooting · Troubleshooting
How to Fix Wordfence Blocking Your Own Admin Access
Short answer
If Wordfence blocks your own admin login, use the email link on the block page to lift the lock, or log in from another network to remove your IP from the block list. If neither works, rename the wp-content/plugins/wordfence folder by SFTP to switch the plugin off, log in, fix the setting that blocked you, then switch the firewall back on.
Key takeaways
- Wordfence blocks an IP after failed logins, a firewall rule match, or a manual block.
- The block page offers an email link to the site admin to lift a temporary lockout.
- Renaming the wordfence plugin folder by SFTP switches the plugin off at once.
- A breached-password block means the password is on a leaked list; change it.
- Wordfence Assistant was closed on WordPress.org on 18 December 2025, so do not rely on installing it fresh.
- Allowlist your own IP only after you fix the rule or password that caused the block.
How do you know Wordfence is blocking you?
You see a Wordfence block page instead of the login form, or the login form rejects you with a lockout message.
Wordfence block pages carry a Generated by Wordfence timestamp at the bottom, showing the time the message was made and the time from your browser. Wordfence's Blocking Troubleshooting guide says that if the two times are far apart, the page was cached wrongly, and the block may not be real.
First confirm the block comes from Wordfence and not another plugin or your host. If the page shows no Wordfence branding and no Reason line, the block sits elsewhere.
Try the login from another network, such as a phone on mobile data. If that works, your IP is blocked, not your account.
What does each Wordfence block message mean?
Each message names a different cause, and the fix depends on reading the Reason line on the block page.
| Message | Meaning | First fix |
|---|---|---|
| You are temporarily locked out | Too many failed logins tripped the brute force rule | Use the recovery email on the page |
| Your access to this site has been limited | The firewall blocked your IP by a site setting | Remove your IP from the block list |
| 403 Forbidden: potentially unsafe operation | A firewall rule matched your request | Allowlist the request in Live Traffic |
| 403 Forbidden: WHAT? | Your IP is on the Real-Time IP Blocklist | Contact your ISP or VPN provider |
| Login blocked: breached password | Your password is on a leaked list | Reset the password |
A temporary lockout lasts as long as the site owner set in the Brute Force Protection options. Wordfence's Blocking Troubleshooting guide says admins can use the email link on the lockout page to get back in at once.
The limited-access message points to a firewall setting such as country blocking or rate limiting. The same guide says the block page shows a Reason you can use to adjust the setting.
The WHAT message means your IP sits on Wordfence's Real-Time IP Blocklist, which holds the IPs most active in attacks on WordPress sites. The guide says Wordfence will rarely remove an IP from that list, since others on the same IP may be the source.
How do you get back in with the recovery email?
Enter your admin email on the block page and open the link it sends you to lift the lock.
On most modern hosts the email arrives within seconds or minutes. Wordfence's Blocking Troubleshooting guide warns that a slow host can let the link expire before it arrives.
If the email never arrives, your site may not be sending mail at all. See How to Fix WordPress Not Sending Emails before you try a harder recovery.
Password reset mail uses the same path, so a missing reset email points to the same mail problem. See How to Fix Password Reset Emails Not Arriving in WordPress.
What if the recovery email never arrives?
Change networks first: log in from a phone on mobile data or a VPN, then remove your own IP from the block list.
With access from the second network, open Wordfence > Firewall > Blocking and delete your IP from the list. That clears the block for your normal connection too.
If you see a PHP error instead of a Wordfence block page, the cause is not a block at all. WordPress's Debugging in WordPress guide explains how to log the real error to wp-content/debug.log.
If no network works and no email arrives, move to the file-system recovery in the next section. Do not keep guessing passwords: each failed attempt can extend the lockout.
How do you switch Wordfence off by SFTP?
Rename the wordfence folder inside wp-content/plugins/ so WordPress stops loading the plugin.
- Connect by SFTP or open your host's file manager.
- Open wp-content/plugins/ and rename wordfence to wordfence-off.
- Load wp-admin and log in as normal.
Wordfence's Blocking Troubleshooting guide says this switch-off takes effect at once. If you still see a Wordfence message, clear any caching plugin and any front-end cache.
If you have no file access of your own, ask your host to rename the folder for you. Wordfence's guide gives that as the last resort for site owners without server access.
How do you get back in safely after switching it off?
Do not rename the folder back yet: Wordfence will block you again the moment it loads.
Wordfence's own Blocking Troubleshooting guide tells you to install Wordfence Assistant, use it to switch the firewall off, and then rename the folder back.
Note that Wordfence Assistant was closed on WordPress.org on 18 December 2025, so a fresh install from the plugin directory is no longer possible.
If you cannot get Assistant through Wordfence support, stay logged in from a second connection and rename the folder back, then open Wordfence > Firewall > Blocking at once and remove your IP.
Once back inside, re-enable the firewall under Wordfence > Firewall > Firewall Options and set it to Enabled and Protecting. Wordfence's guide also says to run Optimize the Wordfence Firewall again after the recovery.
How do you stop Wordfence from blocking you again?
Fix the cause first, then allowlist your IP so normal admin work never trips the same rule.
Find the block in Wordfence > Firewall > Live Traffic, which shows the exact request and rule. If the request was safe, add it to the allowlist from there.
Add your IP to the allowlist in the firewall options so it bypasses all rules. Keep the list short: one IP per admin, and no wide ranges.
Learning Mode lets Wordfence learn normal traffic and allowlist it, but Wordfence's Learning Mode guide warns against leaving it on for long, since it can allowlist things you did not intend.
If logins from your office keep failing, check whether the IP changed: home and office IPs shift, and an old allowlist entry stops matching. A VPN with a fixed IP gives you one stable address to allowlist.
If the block is really a permissions error rather than a Wordfence block, the message reads differently. See How to Fix “Sorry, You Are Not Allowed to Access This Page” in WordPress.
What if Wordfence blocks you because of a breached password?
Change the password: Wordfence blocks logins that use a password found on leaked lists.
Large breaches leak passwords, and bots try those passwords on WordPress sites. Wordfence's Blocking Troubleshooting guide says your password may match a leaked one by chance, or because you reused it elsewhere.
Check whether your email appears in known leaks at Have I Been Pwned. Wordfence's guide links that check directly from the breached-password section.
Reset the password from the login screen and pick a new, strong one. If a plugin blocks password resets, switch Wordfence off by SFTP, log in, and change the password.
What mistakes should you avoid?
Do not allowlist a wide IP range, and do not leave the firewall off after you get back in.
- Allowlisting a whole office or mobile range: one bad actor on that range can use your bypass.
- Leaving the firewall disabled after recovery: the site runs without its main guard.
- Renaming the folder back before removing your IP: the block returns at once.
- Treating every login failure as a Wordfence block: a wrong password or a broken mail setup needs a different fix.
- Skipping the Reason line on the block page: it names the rule or setting to change.
Frequently asked questions
How long does a Wordfence lockout last?
As long as the site owner set in the Brute Force Protection options. Admins can shorten the wait with the email link on the lockout page, and the block clears on its own once the set time passes.
Can I get back in without SFTP access?
Yes, if the recovery email works or another network is not blocked. Log in from the second network, remove your IP from the block list, and then use your normal connection. Without either route, ask your host to rename the plugin folder.
Why does Wordfence block me but not my visitors?
Blocks target a single IP after failed logins or a rule match, so only that IP sees the block page. Visitors on other IPs are unaffected, which is also why a second network gets you back in.
Is it safe to switch Wordfence off to regain access?
Briefly, yes, if you switch it back on right after fixing the cause. Keep the window short, do not browse other sites in between, and re-enable the firewall before you log out.
What should I do if Wordfence blocks my whole office?
One shared office IP means one blocked user can lock out everyone behind it. Remove that IP from the block list, fix the failed logins or rule that caused it, and allowlist only the office IP if it never changes.
Sources
- Blocking Troubleshooting Wordfence
- Learning Mode Wordfence
- Wordfence Assistant WordPress.org
- Have I Been Pwned Have I Been Pwned
- Debugging in WordPress WordPress Developer Resources
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.
