Nginx Acces Local Website 403

Nginx Access Local Website 403


Nginx is an open source software platform used for web server management and processing requests made by web clients. It is often used as a Reverse Proxy server, where it receives requests from a browser or other user and then passes them through to the application or web server. Nginx is also capable of caching requests, serving static resources, and setting up access control.

The “403 forbidden” error is a particularly common Nginx error, and is typically caused by a misconfiguration of Nginx, or the client attempting to access the website didn’t have the right privileges. If you’re new to web hosting and using Nginx, understanding this error can be challenging, but this article will explain the most common causes of a 403 error and give you some steps to take to try to resolve it.

How to Fix Nginx Access Local Website 403 Error?

Check Permissions

Before doing anything else, it’s important to note that this error could be caused by incorrect permissions set in Nginx. This can occur if the directory containing the website has read, write, or execute permissions set for the wrong user or group. To check your Nginx permissions, use the following terminal command:

$ sudo nginx -t

This will return the permissions set in Nginx, along with a warning if they are incorrect. If your permissions are out of order, you can modify them by editing your server configuration file, located at /etc/nginx/nginx.conf.

Check Nginx Configuration

Sometimes a 403 forbidden error can occur when Nginx itself is not correctly configured. To check your configuration for mistakes, enter the following command in the terminal:

$ nginx -t

This will open a detailed report on your Nginx configuration, pointing out any errors or issues. You can also check your configuration manually by opening the file at /etc/nginx/nginx.conf in a text editor.

Check for Firewall Rules

In some cases, a 403 forbidden error can occur due to firewall rules blocking access to certain websites or directories. To check if this is the case, try disabling your firewall temporarily and reloading the website. Alternatively, you can use the following command in the terminal to check if the firewall is blocking access:

$ sudo ufw status

If this command returns any active firewall rules for the website or directory you are trying to access, you will need to adjust them in order to gain access. You can do this by entering the following command:

$ sudo ufw allow

Where is the port number associated with the website or directory you are trying to access.

Use Logs to Troubleshoot

If none of the other methods have worked, you can check your Nginx logs for more detailed information on the nature of the problem. The Nginx logs are located at /var/log/nginx/access.log. There you will find the full error message along with the IP address of the client that was blocked. This can be incredibly helpful in pinpointing the problem, as you may be able to determine if the IP address belongs to a website crawler, an attacker, or an an improper configuration.


In most cases, a 403 forbidden error caused by Nginx is relatively easy to troubleshoot and fix. The important thing to note is to check the permissions, configuration, and firewall rules to make sure they are all correctly configured. If none of those solutions fix the problem, you can check the Nginx logs to investigate further.


  • What is the Nginx 403 forbidden error?

    The Nginx 403 forbidden error is a message returned by the web server, indicating that the client trying to access the website does not have sufficient privileges to do so.

  • How do I fix a 403 forbidden error?

    The best way to fix a 403 forbidden error is to check the file permissions and Nginx configuration, and also to make sure there is no firewall blocking the website. If those don’t fix the problem, you can check the Nginx logs for an explanation of the problem.

  • Where are the Nginx logs located?
    The Nginx logs are located at /var/log/nginx/access.log.

Thank you for reading this article. Please read other articles for more tips and tricks related to web hosting and Nginx.

Leave a Reply

Your email address will not be published. Required fields are marked *