Ошибка failed permission denied 13

I am using the default config while adding the specific directory with nginx installed on my ubuntu 12.04 machine.

server {
        #listen   80; ## listen for ipv4; this line is default and implied
        #listen   [::]:80 default ipv6only=on; ## listen for ipv6

        index index.html index.htm;

        # Make site accessible from http://localhost/
        server_name localhost;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to index.html
                root /username/test/static;
                try_files $uri $uri/ /index.html;
                # Uncomment to enable naxsi on this location
                # include /etc/nginx/naxsi.rules
        }
...

...
}

I just want a simple static nginx server to serve files out of that directory. However, checking the error.log I see

2014/09/10 16:55:16 [crit] 10808#0: *2 stat() "/username/test/static/index.html" failed (13: Permission denied), client:, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "domain"
2014/09/10 16:55:16 [error] 10808#0: *2 rewrite or internal redirection cycle while internally redirecting to "/index.html

I’ve already done chown -R www-data:www-data on /username/test/static, I’ve set them to chmod 755. I don’t know what else needs to be set.

Symptom:

Could not upload images to WordPress Media Library.

Cause:

(CentOS) yum update

Error:

2014/10/22 18:08:50 [crit] 23286#0: *5332 open() "/var/lib/nginx/tmp/client_body/0000000003" failed (13: Permission denied), client: 1.2.3.4, server: _, request: "POST /wp-admin/media-new.php HTTP/1.1", host: "example.com", referrer: "http://example/wp-admin/media-new.php"

Solution:

chown -R www-data:www-data /var/lib/nginx

answered Oct 22, 2014 at 18:14

Change your nginx.conf user property to www-static files owener.

#   * Official English Documentation: http://nginx.org/en/docs/
#   * Official Russian Documentation: http://nginx.org/ru/docs/

user your_user_name;

# same other config

answered Feb 1, 2019 at 3:39

By default the static data, when you install the nginx, will be in /var/www/html.
So you can just copy your static folder into /var/html/ and set the

root /var/www/<your static folder>

in ngix.conf (or /etc/nginx/sites-available/default)

This worked for me on ubuntu but I guess it should not be much different for other distros.

Hope it helps.

answered Mar 29, 2016 at 1:10

In my case, the folder which served the files was a symbolic link to another folder, made with

ln -sf /origin /var/www/destination

Even though the permissions (user and group) where correct on the destination folder (the symbolic link), I still had the error because Nginx needed to have permissions to the origin folder whole’s hierarchy as well.

answered Oct 12, 2017 at 1:57

I had the same issue, I am using Plesk Onyx 17 with Centos7. I could see this error in proxy_error_log under the affected domain’s logs. All the dirs/files in /var/www/vhosts/ are owned by respective users (domain owners) and you can see that all of them are in psacln group. So solution was to add nginx also to this group, so he can see what he needs:

usermod -aG psacln nginx

And indeed, restart nginx and reload page with Ctrl+F5.

answered Mar 22, 2017 at 23:46

answered May 8, 2018 at 9:53

answered May 28, 2020 at 16:15

You can also add which user will run the nginx. In the nginx.conf file, make the following changes:

user root;

You can add the above line as the first line in your nginx conf.
You can write the name of any user who has the permission to write in that directory.

answered Dec 7, 2019 at 8:38

I am trying to migrate my website data to a new server and keep getting this error. I set up public key access and was able to complete rsync with a .txt file I then wanted to try a directory and it isn’t working. This is my first time using rsync so please let me know if you need more information.

Edit: both are remote servers the old is Ubuntu 14.04.4 and the new is Ubuntu 18.04.3

I have sudo permissions on each but I probably dont own the directory I am trying to move. I don’t know how to find out.

$ rsync -rt /var/www kiana@123.456.789.00:/home
rsync: recv_generator: mkdir "/home/www" failed: Permission denied (13)
*** Skipping any contents from this failed directory ***
rsync: readlink_stat("/var/www/vhosts/testing.site.org/wp-config.php") failed: Permission denied (13)
rsync: readlink_stat("/var/www/vhosts/testing.site.org/wp-mail.php") failed: Permission denied (13)
rsync: readlink_stat("/var/www/vhosts/testing.site.org/wordpress") failed: Permission denied (13)
rsync: readlink_stat("/var/www/vhosts/testing.site.org/wp-signup.php") failed: Permission denied (13)
rsync: readlink_stat("/var/www/vhosts/testing.site.org/wp-trackback.php") failed: Permission denied (13)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.0]

asked Sep 11, 2019 at 14:15

This part here:

rsync: recv_generator: mkdir "/home/www" failed: Permission denied (13)

seems to say that the user kiana does not have sufficient permission on the /home-folder of the remote server in order to write to it.

How to check folder permissions

Performing ls -l | grep home from / on the remote server should give you a tell of who owns the folder and what access permissions it has. Standard for the home-folder is that root:root owns it with 755 as folder permissions (read more about folder and file permissions here)

$ ls -l | grep home
drwxr-xr-x   3 root root  4096 21 mar 14.24 home

This output states that the user root with group root owns the folder (d) home and has full permission (rwx), while others of the group root as well as others has read/execute permission (r-x) but not write permission.

A user having sudo-rights means that said user may temporarily have root-privileges after authentication, which is not really plausible with rsync.

Conclusion

As you are not the actual root user performing the rsync (which by security reasons you shouldn’t be), you do not have write-permission on /home folder. I would suggest that you try to save the webserver data in another place where user kiana may be able to write (e.g. /tmp/, /opt/ etc).

answered Sep 11, 2019 at 15:04

Another solution is to add --rsync-path="sudo rsync" to the local rsync command. Then your next problem is, that you cannot type on the remote server (no tty, no interactive prompt). At least one workaround for that is to temporarily set NOPASSWD: (insecure: no password to sudo!) at the sudoers line for your user. Once the rsync command is running, you can remove the insecure config.

Someone first needs to have logged into your server to abuse the temperate sudo insecurity. But weigh the pros and cons.

answered Dec 10, 2022 at 4:11

The is directory permissions /home is typically only writeable by root.
For example, running ls on my machine shows root/root:

$ ls -laF /home
total 12
drwxr-xr-x  3 root     root     4096 Aug 20  2018 ./
drwxr-xr-x 24 root     root     4096 Sep  3 09:00 ../

Your best option is to create a directory in /home by ssh’ing into that machine running:

#Note the sudo, or you'd have to su to root
sudo mkdir /home/www 
#Then change the ownership so the user kiana can write to it:
sudo chown kiana:kiana /home/www