How to configure VPS so that it is not nessacery to have 777 permissions on public_html for wordpress installation?

December 17, 2013 3.4k views
marcel
By:
marcel
I am doing an installation of Wordpress on my VPS. During isntallation I had to set public_hml permissions to 777. Of course, I changed it back after installation, but how can I prevent this on the next installation? I am intending to install multiple wordpress sites soon, and want the installation to be as smooth as possible. And of course, I am just curious how this works. My folder and files all have owner of my server, and since 750 on public_html gives enough permission for a owner to install wordpress I am curious how it is possible that I have unsufficient permissions. Thanks!
Log In to Comment
5 Answers
marcel December 17, 2013
I have digged in existing questions on this matter, and found this (possible) solutions:
sudo usermod -a -G apache username

Is that what I need to do, or has that nothing to do with this?
Reply
marcel December 17, 2013
Ok, I tried doing this, but user group apache does not exist is what I get..
Reply
marcel December 17, 2013
Apologies for all these comments, but I found out that on Ubuntu it has to be www-data instead of apache. I have run that command, and restarted apache, but still my I have not sufficient rights to do almost anything. For example, I cannot install plugins and upload files unless I set permissions to 777
Reply
etel December 17, 2013
Check out this article-- it may address your issue:

https://www.digitalocean.com/community/articles/how-to-configure-secure-updates-and-installations-in-wordpress-on-ubuntu
How To Configure Secure Updates and Installations in WordPress on Ubuntu
by Justin Ellingwood
WordPress is the most popular content management system (CMS) on the web currently. While WordPress can be a great way to manage you content, there are some very insecure configurations that are given throughout the internet. This article will cover how to set up secure updates and installations using SSH keys instead of FTP, which is an inherently insecure protocol.
Reply
marcel December 17, 2013
Hi, Thanks! Very usefull article, added to favorites.

For now, I fixed it by setting owner of all wordpress files to www-data.
Reply
Have another answer? Share your knowledge.