403 Forbidden. It sounds harsh, like you’ve been banned from your own website. This code means your server understands your request but refuses to fulfill it.
Usually, this is a security setting gone wrong. Either a security plugin is being too aggressive, or your file permissions are too strict.
Solution 1: Check File Permissions
If your server folders are set to “private,” the web browser cannot read them.
- Open your File Manager.
- Right-click the public_html folder and check Permissions.
- Set Directories/Folders to 755.
- Set Files to 644.
- Save and refresh.
Solution 2: Deactivate Security Plugins
Plugins like Wordfence or iThemes Security can sometimes lock out the admin if they detect a “false positive” threat.
- Go to wp-content/plugins via FTP.
- Find your security plugin folder.
- Rename it (e.g., wordfence-deactivated).
- Check your site. If it loads, reinstall the plugin and reset its settings.
Solution 3: Check for Corrupt .htaccess
Just like with 500 errors, a bad .htaccess rule can cause a 403.
- Rename your .htaccess file to .htaccess_backup.
- Try to access the site. If it works, generate a new one in Settings > Permalinks.
Conclusion
A 403 error is your server trying to protect you, but doing it too well. By relaxing the permissions or disabling over-zealous plugins, you can let the right people (you and your visitors) back in.
