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 the request but refuses to authorise access to the requested resource. This is a common issue for small business and home office websites and is usually caused by incorrect file permissions, missing index files, IP-based access restrictions, or misconfigured security rules. The following steps will help you identify and resolve the most frequent causes.

Quick Fix Steps

1. Refresh your browser page after waiting a few minutes to rule out temporary server glitches.
2. Clear your browser cache and cookies, then try accessing the site again.
3. Check that you are visiting the correct domain and that there are no typos in the URL.
4. Try accessing the website from a different network or mobile device to rule out IP-based blocking.

Detailed Instructions

Check File and Directory Permissions

1. Log in to your hosting control panel and open File Manager.
2. Navigate to the root directory of your website, typically public_html or www.
3. Right-click your website folder and select Change Permissions or File Permissions.
4. Set directories to 755 and files to 644.
5. Click OK or Apply to save the changes.

Verify Index Files Exist

1. Open File Manager in your hosting control panel.
2. Go to the folder that is showing the 403 error.
3. Look for a default index file such as index.html, index.php, or default.html.
4. If no index file exists, upload one or create a new file named index.html with basic placeholder content.
5. Refresh your website in the browser.

Review .htaccess Rules

1. Open File Manager and ensure hidden files are visible.
2. Locate the .htaccess file in your website root directory.
3. Download a backup copy of the file to your computer before making changes.
4. Right-click .htaccess and select Edit.
5. Look for lines containing deny from, Require all denied, or Order deny,allow.
6. Comment out suspicious rules by adding a # at the start of the line, or remove them entirely.
7. Save the file and test your website.

Check IP-Based Access Restrictions

1. Log in to your hosting control panel.
2. Open IP Blocker, IP Deny Manager, or Security, depending on your panel.
3. Review the list of blocked IP addresses and ranges.
4. If your own IP address is listed, remove it from the block list.
5. Save your changes and reload the website.

Troubleshooting

Confirm File Ownership

1. Open File Manager or connect via FTP/SFTP.
2. Check the ownership column for your website files and folders.
3. Files should be owned by your hosting account username, not by another user or root.
4. If ownership appears incorrect, contact your hosting provider to have it corrected.

Test After Plugin or Theme Updates

1. If the error started after a plugin, theme, or extension update, access your site via FTP or File Manager.
2. Navigate to the plugins or extensions folder, such as wp-content/plugins for WordPress.
3. Rename the folder of the recently updated plugin, for example to plugin-name-disabled.
4. Refresh your website to see if access is restored.
5. If the site works, the plugin is likely incompatible. Check for an update or contact the plugin developer.

Scan for Security Plugin Blocks

1. Log in to your website administration dashboard if possible.
2. Open your security or firewall plugin settings.
3. Check the blocked IP list and recent activity logs.
4. Remove your IP address if it has been blocked by the firewall.
5. Save the settings and test the website again.

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?