How to fix a 403 forbidden error on my website
Summary
This guide helps you troubleshoot and resolve: How to fix a 403 forbidden error on my website. Follow the steps below to fix the issue.
Common Causes
A 403 Forbidden error means your web server understands your request but refuses to authorise access to the requested resource. For small business owners, this usually means visitors cannot view your website even though the server is running. Common causes include incorrect file permissions, missing index files, IP-based access restrictions, and misconfigured security rules.
This guide assumes you are using Apache-based hosting with a control panel such as cPanel. If your host uses Nginx or another server type, .htaccess files will not apply and you should contact your provider for assistance. If your hosting panel interface differs from the examples below, check with your hosting provider before changing settings.
Troubleshooting Scenarios
Check Your CDN or Firewall Service
- If you use a content delivery network or web application firewall such as Cloudflare, log in to that service dashboard.
- Review the security events or firewall logs to see if your IP address or your visitors' IP addresses are being blocked.
- Temporarily pause the CDN or switch to development mode to determine if the 403 error is being caused by the service rather than your hosting account.
- If the error disappears when the CDN is paused, adjust the security settings in your CDN dashboard or contact the CDN provider.
Verify Your Domain DNS Settings
- Confirm that your domain name is correctly pointing to your hosting server.
- Check your domain registrar or DNS management panel to ensure the A record or CNAME matches the IP address provided by your host.
- If you recently changed hosting providers or updated DNS records, allow time for propagation before expecting the website to load correctly.
Confirm File Ownership
- Open File Manager in your hosting control panel, or connect via FTP/SFTP.
- Check the ownership column for your website files and folders.
- Files should be owned by your hosting account username, not by another user or
root. - If ownership appears incorrect, contact your hosting provider to have it corrected.
Test After WordPress Plugin or Theme Updates
- This section applies to WordPress websites. If the 403 error started after a plugin, theme, or extension update, access your site via FTP or File Manager.
- Navigate to the plugins or extensions folder, such as
wp-content/plugins. - Rename the folder of the recently updated plugin, for example to
plugin-name-disabled. - Refresh your website to see if access is restored.
- If the site works, the plugin is likely incompatible. Check for an update or contact the plugin developer.
Scan for Security Plugin Blocks
- Log in to your website administration dashboard if possible.
- Open your security or firewall plugin settings.
- Check the blocked IP list and recent activity logs.
- Remove your IP address if it has been blocked by the firewall.
- Save the settings and test the website again.
Detailed Instructions
Check File and Directory Permissions
- Log in to your hosting control panel and open File Manager. If your panel uses a different interface, such as Plesk or a custom control panel, locate the equivalent file management tool or contact your host for guidance.
- Navigate to the root directory of your website. The root directory is the main folder where your website files are stored, typically named
public_htmlorwww. - Right-click your website folder and select Change Permissions or File Permissions.
- Set directories to
755and files to644. - Click OK or Apply to save the changes.
777 on any folder or file. This allows anyone to write to your website and creates a serious security risk.Verify Index Files Exist
- Open File Manager in your hosting control panel.
- Go to the folder that is showing the 403 error.
- Look for a default index file such as
index.html,index.php, ordefault.html. Without an index file, the server may refuse to display the directory contents. - If no index file exists, upload one or create a new file named
index.htmlwith basic placeholder content. - Refresh your website in the browser.
Review .htaccess Rules
- This step applies to Apache servers. Open File Manager and ensure hidden files are visible.
- Locate the
.htaccessfile in your website root directory. - Download a backup copy of the file to your computer before making changes.
- Right-click
.htaccessand select Edit. - Look for lines containing
deny from,Require all denied, orOrder deny,allow. - Comment out suspicious rules by adding a
#at the start of the line, or remove them entirely. - Save the file and test your website.
Check IP-Based Access Restrictions
- Log in to your hosting control panel.
- Open IP Blocker, IP Deny Manager, or Security, depending on your panel.
- Review the list of blocked IP addresses and ranges.
- If your own IP address is listed, remove it from the block list.
- Save your changes and reload the website.
If none of these steps resolve the issue, the cause may be a server-level configuration that requires provider access. Open a Ticket and our Brisbane support team will investigate the 403 error for you.
Still Having Issues?
💻 Open a Ticket