1

I got message

To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed.

The solution is here

https://www.digitalocean.com/community/questions/why-i-can-t-install-a-new-plugin-on-my-wordpress

However, I don't quite understand about ownership.

Who owns the file?

enter image description here

The owners of the file is 1001?

Who the hell is 1001?

3
  • I would set the ownership to the user that your web server runs as ( Apache/Nginx ), e.g. on some servers, it's www-data, but what will work for you is going to be specific to your server and how you set it up
    – Tom J Nowell
    Sep 12, 2018 at 1:24
  • How to know who the owner should be?
    – user4951
    Sep 12, 2018 at 8:49
  • As I said, that's entirely dependent on how you set up your server. You want an owner that the PHP/Apache/Nginx process can write with, that's a non-WP question though that would be better on serverfault. In all likelihood the answer is in the original tutorial on setting up your server, or ping your hosting provider
    – Tom J Nowell
    Sep 12, 2018 at 14:36

1 Answer 1

2

To fix this issue: Set WordPress directory and file permissions to allow your webserver's user account execute+read+write access. (Typically this means setting permissions 0775 for directories and 0664 for files.)

However, I don't quite understand about ownership.

I'd recommend a review of Understanding Linux File Permissions at Linux.com - it never hurts to know what's going on at the system level.

The owners of the file is 1001?

Who the hell is 1001?

1001 is the first "userland" user created on the system (system-level users typically have ID's in the 0-1000 range).

In this case, the user entry may be missing from /etc/passwd or Filezilla doesn't have read access to /etc/passwd to display the username associated with UID 1001.

Ensure that /etc/passwd has 0644 permissions (owner read+write, group and global read) and an entry for 1001 exists or contact your hosting provider for assistance.

4
  • What exactly I should write in SSH
    – user4951
    Sep 12, 2018 at 9:17
  • 1
    find /path/to/wordpress -type d -exec chmod 775 {} \; then find /path/to/wordpress -type f -exec chmod 664 {} \; then figure out which user your webserver runs under and run chown -R x:x /path/to/wordpress where "x:x" is your UID and the GID of the webserver user.
    – Gray
    Sep 12, 2018 at 9:25
  • Thanks. How do I find out which user or webserver runs under? Who own the webserver
    – user4951
    Sep 13, 2018 at 7:26
  • Run ps aux | grep -E "apache|nginx" and take note of the USER column (far left) to get the username associated with the webserver service (if you're running something other than Apache or nginx, change the grep expression accordingly).
    – Gray
    Sep 13, 2018 at 9:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.