Magento – Magento 2 installation & Linux file folder permission

file-permissionsinstallationlinuxmagento2

I am using Linux Mint. I installed a quick package of Magento 2 Theme. I tried to browse Admin Panel. But I couldn't browse. Then I found I have to change file & folder permission. I tried below command to change file permission.

foysal@foysal-laptop /var/www/html/aloquick $ find . -type f -exec chmod 644 {} \;

I got below result.

chmod: changing permissions of './var/generation/Magento/Weee/Model/Tax/Proxy.php': Operation not permitted

I tried below command to change folder permission.

foysal@foysal-laptop /var/www/html/aloquick $ find . -type d -exec chmod 775 {} \;

I got below result.

chmod: changing permissions of './var/generation': Operation not permitted

Where is the issue ? Am I using wrong commands ?

UPDATE

I executed (sudo find . -type f -exec chmod 644 {} \; sudo find . -type d -exec chmod 775 {} \;) this commands. But I can't browse both front end and back end of the site.

Best Answer

Give 775 permission to your var and pub/media directory.

Run below command for the same.

sudo chmod -R 775 /var/generation
sudo chmod -R 775 /pub/media

If in case in your server 775 not work then try same command with 777 for those 2 folders and check.

Related Solutions

Magento – Magento 2 Development permissions issue

Try fix permissons by commands below

sudo find var vendor pub/static pub/media app/etc -type f -exec chmod g+w {} \; && sudo find var vendor pub/static pub/media app/etc -type d -exec chmod g+ws {} \; && sudo chown -R $USER:www-data . && sudo chmod u+x bin/magento
sudo find var pub/media pub/static -type d -exec chmod g+ws {} \;
sudo find var pub/media pub/static -type f -not -name .htaccess -exec chmod g+w {} \;
sudo find -L vendor/bin -type f -exec chmod u+x {} \;

Magento – In production mode the site does not load

At a quick glance, you're probably running into one or more missing classes. In production mode, Magento doesn't generate any files; instead, it expects you to manually run bin/magento setup:di:compile and bin/magento setup:static-content:deploy on your own.

I see you run bin/magento setup:static-content:deploy; however, you never compile the dependency injection code. This generates all the interceptors, proxies, and other "missing" classes that are normally generated on-the-fly when in developer mode.

I would look in your Apache error logs to see the caught 500 error. You could also check the PHP error logs, as well as the exception and system logs in Magento.

When building a deployment for my site, I do the following steps:

Update branch to be deployed: git fetch && git pull
Set the deployment mode to production (just to be sure): bin/magento deploy:mode:set production
Install composer dependencies: composer install --no-dev --no-suggest --optimize-autoloader
Run upgrade to bring database up-to-date: bin/magento setup:upgrade
Run Magento compilation for dependency injection files: bin/magento setup:di:compile
Generate static content: bin/magento setup:static-content:deploy <lang_Code(s)>

At this point, you should have a bunch of files in the generated, var/view_preprocessed and pub/static folders. The files that you are most likely missing are those in the generated folder.

Best Answer

Related Solutions

Magento – Magento 2 Development permissions issue

Magento – In production mode the site does not load

Related Topic