There’s something oddly personal about a 403 Forbidden error. Your site is clearly there, the server is clearly awake, and yet it’s looking straight at you and saying: you’re not allowed in. On your own website.
The good news is that a 403 is rarely a sign of anything serious. Unlike a crash or a hack, it simply means a rule somewhere is blocking a request, and once you find that rule, the fix usually takes minutes. This guide walks you through the likely culprits in the order that solves most cases fastest.
What Does “403 Forbidden” Mean?
A 403 is the server’s way of saying it understood your request but refuses to allow it. It’s different from a 404, where the page doesn’t exist, and from a 500 error, where something broke. With a 403, everything works; access is just being denied.
You might see it as “403 Forbidden”, “Access Denied”, “You don’t have permission to access this resource” or “Forbidden: you don’t have permission to access / on this server”.
The Most Common Causes
- A security plugin or firewall blocking your IP address or a specific action.
- A corrupted or overly strict .htaccess
- Wrong file or folder permissions on the server.
- A plugin or theme conflict, often right after an update.
- Your host’s firewall (often ModSecurity) or Cloudflare rules flagging a normal request as suspicious.
- A missing index file, so the server refuses to show a folder’s contents.
Quick Checks Before You Fix Anything
Take two minutes to rule out the simple stuff:
- Reload the page, and check that the URL is correct with no typo.
- Try a private or incognito window, or a different browser. If the page loads there, it’s your cookies or cache.
- Switch off your VPN if you use one. Firewalls sometimes block VPN IP addresses.
- Try your phone on mobile data. If the site works there but not on your Wi-Fi, your IP address is probably being blocked.
Fix 1: Clear Your Cache (Browser, Plugin and CDN)
Sometimes the 403 has already been fixed, but you’re still seeing an old saved copy. Clear your browser cache and cookies for the site, then purge your caching plugin (such as LiteSpeed Cache or WP Rocket) and, if you use Cloudflare, choose Caching → Purge Everything. Then reload in a fresh window.
Fix 2: Check Your Security Plugin and Firewall
Security plugins are brilliant at blocking attackers, and occasionally they block you too. If you’ve had a few failed logins, saved a post containing code, or logged in from a new IP address, your plugin may have locked you out.
- If you can still reach the dashboard, open your security plugin (Wordfence, Solid Security, Limit Login Attempts and so on) and look for a list of blocked IPs or a live traffic log. Unblock your own IP address and add it to the allowlist.
- If you’re completely locked out, log in to your hosting File Manager or use FTP, go to wp-content/plugins, and rename the security plugin’s folder (for example, wordfence to wordfence-off). This switches it off. Load your site again, then rename the folder back and adjust its settings.
If you followed our guide to a secure WordPress login, check the login-limiting plugin first, because it’s the most common culprit.
Fix 3: Reset Your .htaccess File
The .htaccess file sits in your site’s main folder and controls redirects, security rules and permalinks. One bad line in it can trigger a 403 across the whole site.
- Open your hosting File Manager and go to your site’s root folder (usually public_html). Turn on Show hidden files if you can’t see .htaccess.
- Download a copy of the file first, as a backup.
- Rename it to .htaccess-old.
- Reload your site. If the 403 is gone, the old file was the problem.
- In WordPress, go to Settings → Permalinks and click Save Changes without changing anything. WordPress creates a fresh, clean .htaccess for you.
If you’d added special rules before, such as redirects or security tweaks, add them back one at a time from your saved copy, checking the site after each.
Fix 4: Correct Your File Permissions
Permissions decide who can read, write or run each file on your server. If they’re too strict, the server refuses to show your pages; if they’re too loose, some hosts block them for safety. Either way, you get a 403.
The safe standard values for WordPress are:
- Folders: 755
- Files: 644
- wp-config.php: 640 or 600 (some hosts prefer 644)
In your hosting File Manager, right-click a file or folder and choose Permissions or Change permissions to check them. Many hosting panels also have a one-click “fix permissions” tool, and your host’s support team can reset them for you in a couple of minutes. If you’re not comfortable changing them yourself, this is a perfectly reasonable thing to ask support to do.
Fix 5: Deactivate Plugins, Then Check Your Theme
If the error appeared right after you installed or updated something, that’s your strongest clue.
- If you can reach the dashboard, go to Plugins, deactivate them all, and check the page.
- If you can’t, rename the wp-content/plugins folder to plugins-off via File Manager. All plugins switch off at once.
- If the 403 disappears, rename the folder back and reactivate plugins one at a time until the error returns. That last plugin is the culprit.
- Still stuck? Switch to a default theme like Twenty Twenty-Five to rule out your theme.
Fix 6: Check for a Missing Index File
When you visit your homepage, the server looks for a file called index.php (or index.html) in your main folder. If it’s missing, many servers refuse to list the folder’s contents and show a 403 instead. Check that index.php exists in public_html. If it was deleted, download WordPress from wordpress.org and upload a fresh index.php from it.
Fix 7: Look at Your Host’s Firewall and Cloudflare
If none of the above work, the block may be happening before WordPress even loads.
- Host firewall (ModSecurity): many shared hosts run a web firewall that sometimes blocks innocent actions, like saving a post with certain code or uploading a file. Contact your host’s support, tell them the exact URL and time of the error, and ask them to check the firewall logs. They can whitelist the rule.
- Cloudflare: if your site uses Cloudflare, open Security → Events and look for blocked requests with your IP address. If a rule or the bot protection is blocking you, adjust or skip that rule. Our Cloudflare for beginners guide explains where these settings live.
- IP or country blocks: check whether you, your host or a plugin has blocked certain countries or IP ranges, which can accidentally include your own.
Where You See the 403 Gives a Clue
- Only on wp-admin or wp-login.php: almost always a security plugin, login limits or a host firewall protecting your login page. Start with Fix 2.
- On the whole site: usually .htaccess, file permissions or a missing index file. Start with Fixes 3, 4 and 6.
- Only when saving a post or uploading a file: often the host’s ModSecurity firewall reacting to something in the content. Go to Fix 7.
- Only for some visitors or countries: a Cloudflare rule, IP block or country block. Check Fix 7.
- In Google Search Console: a page marked “Blocked due to access forbidden (403)” usually means a firewall is blocking Googlebot, or the URL is a private area like wp-admin that’s meant to be blocked. If it’s a real article, test it with Search Console’s URL Inspection, and check your firewall and Cloudflare bot settings.
Quick Reference: Cause and Fix
| Likely cause | What you’ll notice | Fix |
| Cached error | Works in incognito, not in your browser | Clear browser, plugin and CDN cache |
| Security plugin | Locked out after logins or a new IP | Unblock your IP, or rename the plugin folder |
| Bad .htaccess | Whole site shows 403 | Rename it, re-save permalinks |
| Wrong permissions | 403 on files or folders after a move | Set folders to 755, files to 644 |
| Plugin or theme | Started after an update | Deactivate, then re-enable one by one |
| Missing index file | 403 on the homepage | Upload a fresh index.php |
| Host or Cloudflare firewall | 403 only on certain actions or visitors | Check logs, ask host to whitelist |
When to Contact Your Host
If you’ve tried everything here and the 403 is still standing, it’s time to message your hosting support. Give them the exact URL, the time the error happened and what you’ve already tried. Most hosts can see firewall and server logs you can’t, and they fix these regularly. That’s a big part of what you pay them for, so don’t hesitate.
How to Prevent 403 Errors
- Update plugins one at a time, and keep a backup before big changes, as in our guide to backing up and restoring WordPress.
- Add your own IP address to your security plugin’s allowlist.
- Avoid editing .htaccess unless you know exactly what a rule does.
- After moving hosts, ask support to check file permissions straight away.
If you’re dealing with a different error, our guide to common WordPress errors covers the rest.
Frequently Asked Questions
What causes a 403 Forbidden error in WordPress?
The most common causes are a security plugin or firewall blocking your IP, a corrupted .htaccess file, incorrect file permissions, a faulty plugin or theme, or your host’s or Cloudflare’s firewall flagging a request as suspicious.
Is a 403 error my fault or the website’s?
If you’re visiting someone else’s site, it’s usually on their side, though clearing your cache, turning off a VPN or trying another network can help. If it’s your own site, it’s a setting on your server, plugin or firewall that you can fix.
Can a 403 error hurt my SEO?
Yes, if Google gets a 403 on pages you want indexed, it can’t read them and may drop them from search results. A short-lived 403 usually does no lasting harm, but fix it quickly and recheck the page with Search Console’s URL Inspection tool.
What file permissions should WordPress use?
The usual safe settings are 755 for folders and 644 for files, with wp-config.php set to 640 or 600 where your host allows it.
Why do I get a 403 error only when I log in to WordPress?
That’s almost always a login protection rule, such as a security plugin’s lockout after failed attempts, a country block, or your host’s firewall protecting wp-login.php. Unblock your IP in the plugin or ask your host to check.
Can Cloudflare cause a 403 error?
Yes. Cloudflare’s firewall rules, bot protection or country blocks can return a 403 to certain visitors. Check Security → Events in your Cloudflare dashboard to see what was blocked and why.
The Final Word
A 403 Forbidden error feels like being locked out of your own house, but it’s really just an overprotective doorman. Somewhere, a plugin, a file or a firewall rule has decided you don’t belong, and your job is simply to find that rule and correct it.
Work through the fixes in order, starting with the easy ones like cache and security plugins, and most sites are back in minutes. And if all else fails, your host is only a support ticket away.


