How To Fix A 403 Forbidden Error On Your Site?

How does the 403 Error Appear?

Website designers can customize how a 403 error looks just like 404 errors and 502 errors!

403 errors look different in different web servers. Websites even use slightly different names for this error. The most common incarnations of 403 Forbidden errors are as follow:

• Forbidden
• Error 403
• HTTP Error 403.14 – Forbidden
• 403 Forbidden
• HTTP 403
• Forbidden: You don’t have permission to access the site using this server
• Error 403 – Forbidden
• HTTP Error 403 – Forbidden

What are the Main Causes of these 403 Errors?

HTTP 403 forbidden error is commonly encountered due to a client-side setup issue, which can usually be resolved independently. One of the primary reasons behind a 403 forbidden error is the configuration settings applied to a specific folder or file. These settings determine the access privileges for different users, such as read, write, or execute permissions for that particular resource.

In this situation, the owner of the website may have:

• Altered the settings, thereby denying you access to the relevant resources.
• Failed to establish appropriate permissions.
• Another frequent factor contributing to a 403 forbidden error is incorrect or corrupted hatches file settings. This can occur after modifying a file. Fortunately, resolving this issue is relatively simple—you can create a new server configuration file.

There are several other possible causes for a 403 forbidden error, including:

• Incorrect IP Address: A domain name points to an incorrect or outdated IP address, hosting a site that restricts your access.
• Issues With a WordPress Plugin: Certain WordPress plugins may be incompatible with others or have incorrect configurations.
• New Page Link: A site owner updates a page's link, resulting in a discrepancy from the cached version.
• Malware: Malware infections can corrupt the .hatches file, requiring the removal of the infection before restoring the file.
• Missing Index Page: Your website's homepage is not named 'index. php' or 'index.html'.

Any of these causes could be responsible for the 403 forbidden error on your website.

Errors Like 403 Forbidden

Here are a few client-side errors that are related to the HTTP 403 Forbidden errors such as:

• 400 Bad Requests
• 401 Unauthorized
• 404 Not Found
• 500 Internal Server Error
• 408 Request Timeout

Method 1 – Checking .htaccess File

Most people are not familiar with the .htaccess file. It’s because the file remains in the “hidden in the project directory”.

.htaccess is basically a server configuration file and mainly works by altering the configuration on the Apache Web Server settings.

However, you can access them easily if you are using the Hostinger File Manager.

In case you are not using Hostinger File Manager, or let’s say if you’re using C Panel in place, you can access the .htaccess file hosting Control Panel with the help of File Manager. Below are the steps involved:

• Go to Hosting Control Panel and locate File Manager from there
• Next, go to the public_html directory and look for the .htaccess file

If you are not able to find such a file though, then click on the settings and enable Show Hidden Files (dotfiles) option from there

In case, if your website lacks the file and you don’t have a .htaccess file detected, you can create it through the manual approach. As discussed, as soon as you found the .htaccess file, you need to follow the following steps:

• To have a backup, download the .htaccess to your pc
• Once the downloads are complete, delete the file

• Then, try to access your site.
• If it is working absolutely fine now, it simply indicates that your .htaccess file was corrupt.
• Now, to create a new .htaccess file, you need to login to your CMS and then hit settings
• In the settings option, click on Permalinks.
• Without any changes, just hit the Save button which is located at the bottom of the page.

• Hence, following these steps, you will generate a fresh.htaccess file for your website.

In case, this doesn’t work out, move onto the next discussed steps:

Explore an in-depth guide on how to fix 500 errors.

Method 2 – Resetting File and Directory Permissions

Remember when files are created, they always come up with some default permissions. This bad permission is what led to a Http Error 403 forbidden message. They control all the files and folder activities such as how you can read, write and execute the files for your use.

If you are using Hostinger, download Fix File Ownership to take care of all your permission problems in just a single click.

Not only it will save your time but also will restore all file and directory permissions to default values.

However, you can use FileZilla FTP to edit file and folder permissions. To get started, you should follow the following steps:

• Choose any FTP client and try to access your website
• Then, shoot the hosting account and go to the root directory of it.
• Next, you have to select the main folder which obviously includes all your website files (public_html), and then right-click on it. After that, hit File permissions. (step 3)

Next, check the Apply to directories the only option and enter permission 755 in the numeric value field provided, and finally press OK.

Once the FileZilla is done changing folder permissions, repeat step 3 again. But remember, you have to choose to apply to files only option this time. Then enter the numeric value 644 in the provided field.

• Once you are done, try to access your website and check if the error is resolved

If the error is not resolved/ looks down similar as before, move to the next section of the article:

Method 3 – Disabling WordPress plugins

If the errors are still not resolved using the above two methods, it’s high time to understand that the error is popping up over and again due to an incompatible or faulty plug-in. In this section, we will try the disabling plug-in and would check if it fixes the 403 forbidden errors or not.

Instead of going to each and every plug-in and then disabling it, it would be better to disable all the plugs- INS at once. Through this step, you would not only take less time but also will be able to detect the problem easily. Below are the following steps you need to take:

• Look for the public_html folder after accessing your hosting account with FTP.
• Next, reach out to the wp_content folder on the page
• Then, go to the plugin option and rename it completely different such as “non-working plugin” etc. By doing this, the tracking procedure will become easier for you.

Try to access your website again after disabling all the plugins. Did it take away the problem? If yes, then the actual source of the error was the plugin only. Now, next, you need to deactivate the plugin one by one and thus have to check if your website is coming back to action or not.  Thus, using this method, you would be able to detect the faulty plugin that is the root cause of the problem.

If installing a new one seems mandatory, you can choose to update the plug-in though.

If sadly, none of the methods explained above works out for you, (It’s really rare), you may need to get in touch with your hosting provider.

Method 4 – Upload Index Page

Another method to resolve these 403 errors is to upload an index page.

Check your website’s homepage name as it should be like index.html or index.php format. If it’s not, then simply rename the homepage as index.html or index.php.

However, if you want to keep the current homepage name, another way is to upload an index page to your public_html directory and create a redirect to your existing homepage. Here are the steps to follow for the same:

• Using a hosting account’s file manager or FTP, Upload an index.html or index.php file to your public_html directory. 
• Open the .htaccess file.
• Insert the below-given code snippet to redirect the index.php or index.html file to your existing homepage. Don’t forget to replace homepage.html with your page’s actual name.

Redirect /index.html /homepage.html

Method 5 – Edit File Ownership

• Incorrect file ownership could be a cause of 403 forbidden errors if you use Linux or VPS hosting. Generally, files and folders are assigned to an Owner, a Group, or both.
• Keep in mind that you need SSH access to modify file ownership in Linux and VPS hosting and an SSH terminal to connect to the VPS server.
• Once you’ve connected SSH to your web server, you can check the file ownership by using this SSH command:

ls -1 [file name]

• The result would come something like this:

-rearward- 1 [owner][group] 20 Jul 20 12:00 filename.txt

Look at the owner and group part, if you find different ownership, use the chow Linux command to modify file ownership. Here’s the basic syntax for chow Linux command:

chow [owner][:group] [file name]

For example, if your username is GoDaddy, use the syntax like this:

chow GoDaddy filename.txt

If you don’t feel comfortable using SSH yourself, you can contact JanBask’s support team for assistance.

Method 6 – Verify A Record

Another possible cause of 403 errors is pointing to the wrong IP address, where you don’t have permission to view the content. 

So, make sure to check the domain A record that your domain name points to the correct IP address.

To check if the domain A record is pointed correctly, you have to access the DNS Zone Editor in hPanel:

Here are the steps to follow:

• First, log in to your hPanel.
• Click on DNS Zone Editor under the Advanced section.

• You will get the list of DNS records. You can find the record with the label A in the type column.

• Check does the IP address in the Content column. If it’s pointing to the wrong IP address, click on Edit to change it, once you update the correct one, click Update.

In case you don’t find the correct record, you have to create a new one from the Manage DNS records section. Make sure you select Type A and insert the correct IP address into the Points to field, then click Add Record.

Wrong nameservers  also cause HTTP error 403 

If you have recently migrated from one web host to another and your domain may still be pointing to your old web host.

Once the old host cancels your account, it will cause 403 errors. Therefore, 403 errors when you change the web host, make sure your domain is pointing to the right web host.

Method 7 – Scan Website For Malware

Malware can be another cause of the HTTP 403 errors. 

Scan your website to identify any malware. There are plenty of security plugins that you can use for WordPress websites, such as Sucuri or WPScan, to do so.

Using security plugins you can remove malware by deleting or restoring them.

Method 8 –  Clear Web History/Cache

Your browser’s cache and cookies may also give rise to 403 errors. Cache stores data to make a website load faster for future visits.

However, it may be possible that the website’s link has been updated, and the actual & recent web page link is different from the cached version. So, clearing browser cache and cookies may also resolve this issue. 

Follow these steps to clear cache and cookies on Google Chrome:

• Click on the three-dot icon on the top right corner of the browser and select Settings.
• Go to the Privacy and Security section and click Clear browsing data.

• Select the time frame for data deletion. Then, check the Cookies and other site data and Cached images and files options.

• Finally, click Clear data.

Now you are done, you can check by visiting the website and logging in if HTTP error 403 gets resolved or not.

If the above-listed methods don’t work, we recommend contacting our support team to help you get out of this issue.