New 24/7 monitoring and daily cloud backups now included in every Shield Pro plan.

HTTP 403

How to fix a WordPress 403 forbidden error

A 403 forbidden error means the server understood the request but refused to serve it. WordPress files, security plugins, or hosting firewalls often block access. This tutorial covers permissions, .htaccess, and security plugin recovery.

Time: 15-30 minutes Level: Beginner

What this problem looks like

403 errors on WordPress usually come from wrong file permissions, aggressive security plugins, mod_security rules, or IP blocks in .htaccess. Unlike 500 errors, the server is actively refusing access rather than crashing.

Start by noting whether wp-login.php, wp-admin, or the whole site is blocked. Path-specific 403 often points at a security plugin or hotlink protection rule.

Step 1: Map where the 403 appears

Open the homepage, a blog post, wp-login.php, and wp-admin in a private browser window. If only wp-admin is blocked, a security plugin or host WAF is the likely cause.

  • Sitewide 403: check root .htaccess and folder permissions.
  • wp-admin only: security plugin or host admin protection.
  • Uploads folder 403: hotlink protection or wrong permissions on wp-content/uploads.
If you recently changed your office IP, security plugins that whitelist IPs may block you from everywhere else. Disable the plugin via FTP before editing rules.

Step 2: Fix file permissions on Linux hosting

Directories should be 755 and files 644. Never set 777 on production. In cPanel File Manager, select wp-content, wp-admin, and wp-includes and apply correct permissions recursively.

bash
find /path/to/wordpress -type d -exec chmod 755 {} \;
find /path/to/wordpress -type f -exec chmod 644 {} \;

Step 3: Inspect .htaccess for deny rules

Open .htaccess in the site root. Look for Deny from all, Require all denied, or plugin-generated blocks. Comment out suspicious sections and test.

Step 4: Deactivate security plugins via FTP

Plugins like Wordfence, iThemes Security, and All In One WP Security can 403 wp-admin after misconfiguration. Rename the plugin folder in wp-content/plugins/ to deactivate it without admin access.

  1. Rename wordfence to wordfence.off.
  2. Reload wp-admin.
  3. Reconfigure or replace the plugin before reactivating.

Step 5: Contact host about mod_security

If 403 appears when saving posts or uploading files, mod_security may flag legitimate requests. Ask your host to check mod_security logs and whitelist the rule ID blocking your action.

When to stop DIY and hire help

Persistent 403 errors after permission fixes often involve host WAF rules or corrupted .htaccess from multiple security plugins. BugShield resolves access blocks at a fixed price with secure Vault access to your hosting.

FAQs

Why does wp-admin show 403 but the front end works?

Security plugins, host admin URL protection, or IP whitelists commonly block wp-admin only. Deactivate security plugins via FTP first.

Can wrong permissions cause 403?

Yes. Files set to 600 or folders to 700 can make the web server refuse to read them. Use 644 for files and 755 for directories.

Should I chmod 777 to fix uploads?

No. 777 is a security risk. Fix ownership with your host so the web server user can write to wp-content/uploads.

How do I fix 403 after migrating hosts?

Reset permissions, regenerate .htaccess from Permalinks, and confirm the new host does not block your IP range.

Rather someone else fixed it?

Request a fix at a confirmed price. Named UK developer, secure Vault, direct chat.

Request a Fix