Magento – Magento users/permissions web server & group

groupinstallationmagento2permissions

So a prior question led me to this, I am trying to use Magento2, (very frustrating)

I have a VPS, with all the proper things for Magento2 to run.

I can install it but have huge permissions issues, because the part of the documentation I cannot understand is the part about Put the Magento file system owner in the web server's group

http://devdocs.magento.com/guides/v2.0/install-gde/prereq/apache-user.html#install-update-depend-user-add2group

when I do:
[~]# egrep -i '^user|^group' /etc/httpd/conf/httpd.conf

I get:

User nobody 
Group nobody 
UserDir 
public_html 
UserDir 
disabled 
UserDir disabled

and I don't know how to proceed from here.

Any help would be appreciated.

UPDATE### I have now completely started over… I wiped the host account clean and created a new one, starting from scratch, trying to follow the install directions from magento. everything is good up until the point where I have to: Put the Magento file system owner in the web server's group – I'm stuck there, since my user and group are both "nobody" I don't know what to do next, is says to do this THEN install magento… so I'm just stuck here now.

Best Answer

This command egrep -i '^user|^group' /etc/httpd/conf/httpd.conf is to help you to grab apache user and group automatically. But you can do it also manually:

Try to open your httpd.conf (using some editor, for example vim). And find this strings:

# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
#
User www
Group www

In this particular case my Apache user is www and Apache group is www.

Also from output of your command I can see that your apache user and group is nobody so you can proceed starting from http://devdocs.magento.com/guides/v2.0/install-gde/prereq/apache-user.html#install-update-depend-user-add2group (just keep in mind that you need to use user and group nobody instead apache)

If you have any questions or need more details - just let me know. Thank you.

Related Solutions

Magento Server Setup – How to Set Proper Permissions for Magento

Please check and verify below steps:

Check if your server is compatible with Magento. Download file from this link Magento Server Compatibility check and follow the instructions given.
Check for the .htaccess in each folder and in root too. Magento has .htaccess in almost all folders. Verify it for media folder in case the problem is with image
Execute the following server commands going into your project folder:
```
find ./ -type f | xargs chmod 644
find ./ -type d | xargs chmod 755
```
This gives 644 permission to files and 755 to folders.
Next give 777 permission to var and media folder if the problem still persists, use the following commands for it:
```
chmod -Rf 777 var
chmod -Rf 777 media
```
Also check the html folder permission of your server. It should be 755.

Hope this should resolve your problem.

Magento – Internal server error when setting full permissions

Depending on your server configuration and running webusers you need to setup write access to some directories. All other files should be read only to the webuser! This will make sure your website isn't defaced easily.

First of all, there are a lot of reasons to not have a /downloader directory on production environments. There have been some patches in the past for the downloader. Add some sort of security with basic auth on these directories

First of all, reset all to read only/default.

# In your Magento root directory
# This will put all files in readonly for group/other and write for user
chmod ugo-rwx,ugo+rX,u+w -R .

# Some files need execute rights
chmod +x cron.sh mage

# Some directories need write access
chmod go+w -R media var downloader includes

Also remove downloader/connect.cfg so it will re-initiate.

Best Answer

Related Solutions

Magento Server Setup – How to Set Proper Permissions for Magento

Magento – Internal server error when setting full permissions

Related Topic