By Ryan

2013-10-10 01:00:28 8 Comments

I have 3 domain names and am trying to host all 3 sites on one server (a Digital Ocean droplet) using Nginx.

Only 1 of them works. The other two result in 403 errors (in the same way).

In my nginx error log, I see: [error] 13108#0: *1 directory index of "/usr/share/nginx/" is forbidden.

My sites-enabled config is:

server {
        return 301 $scheme://$request_uri;
server {

        root /usr/share/nginx/;
        index index.html index.htm index.php;

        location / {
                try_files $uri $uri/ /index.html index.php;

        location ~ \.php$ {
                fastcgi_split_path_info ^(.+\.php)(/.+)$;
                fastcgi_pass unix:/var/run/php5-fpm.sock;
                fastcgi_index index.php;
                include fastcgi_params;

All 3 sites have nearly identical config files.

Each site's files are in folders like /usr/share/nginx/, and then /usr/share/nginx/ is a symlink to that. (Same for mysite2 and mysite3.)

I've looked at Nginx 403 forbidden for all files but that didn't help.

Any ideas on what might be wrong?


@Credoz 2019-07-18 05:00:23

location / {
root  fileLocation;
index  index.html index.htm;
expires 0;
if_modified_since off;}

Here I used alias instead of root and that caused me the error. This configuration works fine.

@user9869932 2019-06-22 11:18:07

To fix this issue I spent a full night. Here's my two cents on this story,

Check if you are using hhvm as php interpreter. Then it's possible that it's listening on port 9000 so you will have to modify your web server's config.

This is a side note: If you are using mysql, and connections from hhvm to the mysql become impossible, check if you have apparmor installed. disable it.

@xoyabc 2019-06-17 14:02:46

when you want to keep the directory option,you can put the index.php ahead of $uri like this.

try_files /index.php $uri $uri/

@maz 2013-11-15 18:11:22

If you're simply trying to list directory contents use autoindex on; like:

location /somedir {
       autoindex on;

server {
        listen   80;
        access_log  /var/...........................;
        root   /path/to/root;
        location / {
                index  index.php index.html index.htm;
        location /somedir {
               autoindex on;

@Ryan 2014-05-14 14:37:30

I definitely don't want autoindex on; it would be a bad idea to expose my directory contents to the public.

@Bhargav Nanekalva 2014-12-17 06:38:59

@Ryan It always comes down to "What do you want to do?"

@Joe 2015-02-19 04:25:30

It's pretty clear he wants to remove 403 errors and get webpages to show not display the entire directory contents (esp given the discussion above)

@robin ong 2019-03-18 03:58:57

I resolved my problem, if i configure like follow:

location = /login {
    index  login2.html;

It'll show the 403 error.

[error] 4212#2916: *2 directory index of "D:\path/to/login/" is forbidden

I've tried autoindex on, but not working. If i change my configure like this, it works.

location = /login/ {
    index  login2.html;

I think the exact matching, if it's a path should be a directory.

@Ryan 2013-10-10 17:46:28

Here is the config that works:

server {
    return 301 $scheme://$request_uri;
server {
    #This config is based on

     # The location of our project's public directory.
    root /usr/share/nginx/mysite2/live/public/;

     # Point index to the Laravel front controller.
    index           index.php;

    location / {
        # URLs to attempt, including pretty ones.
        try_files   $uri $uri/ /index.php?$query_string;

    # Remove trailing slash to please routing system.
    if (!-d $request_filename) {
            rewrite     ^/(.+)/$ /$1 permanent;

    # pass the PHP scripts to FastCGI server listening on
    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
    #   # NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini
    #   # With php5-fpm:
        fastcgi_pass unix:/var/run/php5-fpm.sock;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param                   SCRIPT_FILENAME $document_root$fastcgi_script_name;


Then the only output in the browser was a Laravel error: “Whoops, looks like something went wrong.”

Do NOT run chmod -R 777 app/storage (note). Making something world-writable is bad security.

chmod -R 755 app/storage works and is more secure.

@OrangeTux 2014-03-15 11:03:52

NEVER run chmod -R 777 to get things working!

@Ryan 2014-05-14 14:32:45

Yeah, you guys are right; that's a bad idea. I'll update my answer. People also might benefit from

@complistic 2014-05-16 02:17:37

You may also have the option of changing the folders group to the nginx group ie www-data on debian. Then setting even stricter permissions on the folder like: chmod -R 640 app/storage then chown -R :www-data app/storage. This way the files are only visible to the app owner and the web server. And no-one at all can execute any of the stored (possibly uploaded) files directly. Nginx should only need read permission to access the files.

@Ryan 2014-06-02 00:29:42

Note to self: I just got this Nginx 403 again and again the problem was that I had accidentally left off public/ on root /usr/share/nginx/mysitename/public/;. After adding public/ and running service nginx restart, it worked.

@Himanshu Bansal 2019-05-27 04:50:40

what about windows?

@zeros-and-ones 2018-02-12 05:50:59

For me the problem was that any routes other than the base route were working, adding this line fixed my problem:

index           index.php;

Full thing:

server {

    root /var/www/example/public;
    index           index.php;

    location / {
        try_files $uri $uri/ /index.php?$query_string;

    location ~ \.php$ {
        include /etc/nginx/fastcgi_params;
        fastcgi_index index.php;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

@JCM 2016-06-27 04:49:26

If you have directory indexing off, and is having this problem, it's probably because the try_files you are using has a directory option:

location / {
  try_files $uri $uri/ /index.html index.php;
}                 ^ that is the issue

Remove it and it should work:

location / {
  try_files $uri /index.html index.php;

From what I can see, this is caused because nginx will try to index the directory, and be blocked by itself. Throwing the error mentioned by OP.

@Travis D 2016-10-06 00:15:54

This is exactly the problem I was having. I could not understand why try_files was not trying index.php, I just kept getting 403 with "directory index of ... is forbidden"

@joseluisq 2016-11-09 17:52:05

I removed $uri/ and it works

@pixeline 2016-11-26 23:44:27

same here: this is my accepted answer :)

@Ian Dunn 2017-04-13 20:49:56

@JCM, would you mind adding an explanation of why having $uri/ creates a problem?

@alariva 2017-06-06 19:22:52

Solved mine as well

@JCM 2017-06-09 21:46:41

@IanDunn because nginx will try to index the directory, and be blocked by itself. Throwing the error mentioned by OP.

@Ours 2017-10-04 11:27:15

Been looking for that all morning, couldn't figure it out. Thanks a lot!

@jivanrij 2019-04-02 04:01:37

I had the same error. I had 2 sites, both in a subdomain. Removing the $uri/ did the trick. Thanks!

@Syed Ali Taqi 2019-05-30 07:22:56

Been pulling my hair out for 2 days and there lies the answer, thank a lot man :)

@Ali Hashemi 2017-04-08 19:58:32

Because you're using php-fpm, you should make sure that php-fpm user is the same as nginx user.

Check /etc/php-fpm.d/www.conf and set php user and group to nginx if it's not.

The php-fpm user needs write permission.

@theDrifter 2016-03-30 13:21:53

I had the same problem, the logfile showed me this error:

2016/03/30 14:35:51 [error] 11915#0: *3 directory index of "path_scripts/viewerjs/" is forbidden, client: IP.IP.IP.IP,     server:, request: "GET /scripts/viewerjs/ HTTP/1.1", host: "domain", referrer: ""

I am hosting a PHP app with codeignitor framework. When i wanted to view uploaded files i received a 403 Error.

The problem was, that the nginx.conf was not properly defined. Instead of

index index.html index.htm index.php

i only included

index index.php

I have an index.php in my root and i thought that was enough, i was wrong ;) The hint gave me NginxLibrary

@mboy 2016-07-04 17:46:14

Thank man.. I was with the same boat.. I spent hours figuring out why my wordpress do't work at all! index directive is needed in the nginx main config for my wordpress installation to work include /etc/nginx/conf.d/*.conf; include /etc/nginx/sites-enabled/*; index index.html index.htm index.php;

@GeekHades 2018-02-28 07:04:37

It works for me!

@wave_1102 2015-03-12 12:49:21

location ~* \.php$ {
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;    

Change default

fastcgi_param  SCRIPT_FILENAME  /scripts$fastcgi_script_name;


fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

solved my problem.

@Raunaq Kochar 2016-02-17 12:45:51

6833#0: *1 directory index of "/path/to/your/app" is forbidden, client:, server:, request: "GET / HTTP/1.1", host: "localhost"    

I was running Ubuntu 15.10 and encountered the 403 Forbidden error due to a simple reason. In the nginx.conf(configuration file for nginx), the user was 'www-data'. Once I changed the username to [my username], it worked fine assuming the necessary permissions were given to my username. Steps followed by me:

chmod 755 /path/to/your/app    

My configuration file looks like this:

**user [my username]**;#I made the change here.
worker_processes auto;
pid /run/;
events {
worker_connections 768;
# multi_accept on;

http {

# Basic Settings

sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;
# server_tokens off;

# server_names_hash_bucket_size 64;
# server_name_in_redirect off;

include /etc/nginx/mime.types;
default_type application/octet-stream;

# SSL Settings

ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_prefer_server_ciphers on;

# Logging Settings

access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;

# Gzip Settings

gzip on;
gzip_disable "msie6";

# gzip_vary on;
# gzip_proxied any;
# gzip_comp_level 6;
# gzip_buffers 16 8k;
# gzip_http_version 1.1;
# gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

# Virtual Host Configs

include /etc/nginx/conf.d/*.conf;
include /etc/nginx/sites-enabled/*;

server {
    listen 80;

    server_name My_Server;

    access_log  /var/log/nginx/access.log;
    error_log  /var/log/nginx/error.log;

    location / {
        proxy_redirect     off;

        proxy_set_header   Host             $host;
        proxy_set_header   X-Real-IP        $remote_addr;
        proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;

@Manohar Reddy Poreddy 2015-08-19 07:22:16

I encountered similar error
--- "403 Forbidden" in the webpage
--- "13: Permission denied" in the error log at /var/log/nginx/error.log

Below 3 Steps worked for me:

1: Open Terminal, saw something like below

[email protected]:/home/www/

So, my user name is "user1" (from above)

2: Changed user in /etc/nginx/nginx.conf

# user www-data;
user user1;

3: Reloaded the nginx

sudo nginx -s reload  

Additionally, I have applied file/folder permissions (before I did above 3 steps)
(755 to my directory, say /dir1/) & (644 for files under that directory):
(I am not sure, if this additional step is really required, just above 3 steps might be enough):

chmod 755 ./dir1/
chmod 644 ./dir1/*.*

Hope this helps quick someone. Best of luck.

@Altaf Hussain 2015-09-15 07:10:51

Thanks bro, i had the same issue, and it was because of permissions. I set folder and file permissions, and now it is working fine.

@Manohar Reddy Poreddy 2015-09-15 07:39:08

Glad to hear I am helpful. (Help others, in your known domain, in your free time, if possible, without expecting anything back)

@Sandeep C 2018-05-22 11:15:45

This worked! Thanks!

@Manohar Reddy Poreddy 2018-05-23 12:26:34

Glad to hear it helped.

@Cameron Kerr 2015-09-26 19:06:18

You might get this because of Nginx policy (eg. "deny"), or you might get this because of Nginx misconfiguration, or you might get this because of filesystem restrictions.

You can determine if its the later (and possibly see evidence of a misconfiguration by using strace (except, the OP won't have access to that):

# pidof nginx
11853 11852

# strace -p 11853 -p 11852 -e trace=file -f
Process 11853 attached - interrupt to quit
Process 11852 attached - interrupt to quit
[pid 11853] stat("/var/www/html/kibanaindex.html", 0x7ffe04e93000) = -1 ENOENT (No such file or directory)
[pid 11853] stat("/var/www/html/kibana", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
^CProcess 11853 detached
Process 11852 detached

Here I'm inspecting the filesystem activity done by nginx while a ran a test (I had the same error as you).

Here's a selected part of my config at the time

    location /kibana/3/ {
        alias /var/www/html/kibana;
        index index.html;

In my case, as strace quite clearly shows, the joining of in the "alias" to the "index" was not what I had expected, and it seems I need to get into the habit of always appending directory names with a /, so in my case, the following worked:

    location /kibana/3/ {
        alias /var/www/html/kibana/;
        index index.html;

@kzahel 2016-03-03 19:41:34

Thanks for this. I knew I did not have a permissions problem and your comment helped me find the solution. I added a "/" to the end of my alias and it works fine.

@Agung Prasetyo 2016-11-11 17:08:09

you are my hero @Cameron Kerr, based on my experience the problem is nginx raise 403 for not found files on alias directory e.g /home/web/public. Why nginx try to access these not found files is because i forgot to remove this line index index.html index.htm index.nginx-debian.html; since thats files is not inside my public dir.

@Haimei 2015-02-24 04:23:07

In fact there are several things you need to check. 1. check your nginx's running status

ps -ef|grep nginx

ps aux|grep nginx|grep -v grep

Here we need to check who is running nginx. please remember the user and group

  1. check folder's access status

    ls -alt

  2. compare with the folder's status with nginx's

(1) if folder's access status is not right

sudo chmod 755 /your_folder_path

(2) if folder's user and group are not the same with nginx's running's

sudo chown your_user_name:your_group_name /your_folder_path

and change nginx's running username and group

nginx -h

to find where is nginx configuration file

sudo vi /your_nginx_configuration_file

//in the file change its user and group
user your_user_name your_group_name;

//restart your nginx
sudo nginx -s reload

Because nginx default running's user is nobody and group is nobody. if we haven't notice this user and group, 403 will be introduced.

@Rhys 2013-10-11 07:44:02

You need execute permission on your static files directory. Also they need to be chown'ed by your nginx user and group.

@complistic 2014-05-16 02:13:27

I think he only need needs read permission to the nginx process?

@Mohammad AbuShady 2013-10-10 08:13:34

change the try_files to point to the index.php path, in the "Laravel" that you mentioned it should be something like this

location / {
    try_files $uri $uri/ /public/index.php$request_uri;

And in the "codeigniter" project try it like this

location / {
    try_files $uri $uri/ /public_web/index.php$request_uri;

@Tomahock 2013-10-10 01:21:29

It look's like some permissions problem.

Try to set all permisions like you did in mysite1 to the others site.

By default file permissions should be 644 and dirs 755. Also check if the user that runs nginx have permission to read that files and dirs.

Related Questions

Sponsored Content

15 Answered Questions

3 Answered Questions

nginx change root folder for specyfic url

  • 2013-06-27 07:24:06
  • kabra
  • 13008 View
  • 6 Score
  • 3 Answer
  • Tags:   nginx path root

3 Answered Questions

[SOLVED] Share Nginx server configuration

  • 2014-06-11 04:04:32
  • Anam
  • 1557 View
  • 4 Score
  • 3 Answer
  • Tags:   php nginx

0 Answered Questions

Cannot get index.php page to display in docker container

  • 2019-02-06 04:42:32
  • sp156
  • 173 View
  • 0 Score
  • 0 Answer
  • Tags:   php docker nginx

1 Answered Questions

403 Forbidden Nginx

  • 2018-11-14 04:29:32
  • Janith
  • 1943 View
  • 0 Score
  • 1 Answer
  • Tags:   html nginx

34 Answered Questions

1 Answered Questions

[SOLVED] Strange Nginx behavior with trailing slashes

12 Answered Questions

1 Answered Questions

[SOLVED] 403 forbidden error at Nginx

  • 2013-07-20 22:33:13
  • ezdookie
  • 5643 View
  • 1 Score
  • 1 Answer
  • Tags:   nginx centos

3 Answered Questions

Sponsored Content