Magento 1.9 – Fix 403 Error for Admin Images and JS

adminerrorfile-permissionsmagento-1.9permissions

I am going through the painstaking process of upgrading from 1.6 to 1.9

I choose to do a fresh install of 1.9 instead of each variation.

I followed these steps and seem to have gotten pretty good results but with some hiccups along the way.

(This answer is what I used for the upgrade: https://stackoverflow.com/questions/24043812/how-to-upgrade-magento-1-6-to-magento-1-9)

Problem:
When I log into the admin.. nothing is clickable or updatable, also the Magento logo does not appear, but the files are on the server and the are linked with the correct paths.

When I go to a .js file or image file I am getting a 403 forbidden access to this resource on the server denied!

I'm pretty sure this is an .htaccess issue with permissions but I have been playing with it and no luck.

NOTE: FIXED THIS, May Be Related: I was getting a warning first time i logged into admin and it was because an .htaccess file was missing in the app/etc/ directory… I added it with deny and that warning is now gone in the admin screen.

UPDATE! The permissions for the /skin/adminhtml/default/default/images

The folder Dir are set to 755, but the files themselves are set to 644

I changed the logo file to 755 – and now it pops up on the admin page…

Is there a correct way to set all these files including the JS files to 755 so its not 403? I could try and go in there 1by1 but I assume there is a better way and correct way for the rest of the store not getting these errors…

Please see screenshot of admin with console current trouble:

Assume:
So assume this has something to do with global access.

Best Answer

You should only use 755 for directories and 644 for files (they don't need the executable permission).

Use these commands in the skin directory to apply the permissions recursively:

find . -type f -exec chmod 644 {} ;
find . -type d -exec chmod 755 {} ;

The first line finds all files and chmods them to 644, the second line finds all directories and chmods them to 755.

Related Solutions

Magento – 403 error while installing Magento – is the install guide correct

TLDR; version of why Magento gives those instructions: you want things to be writable during installation (700 directories and 600 files), then afterwards assign ownership to the web server running user and restrictive permissions (500 directories, 400 files) that allow read only except for media/ and var/ directories.

This will work on a server that has been set up specifically with security in mind. Web servers can have a lot of variation in their setup especially shared hosts.

Your system sounds like it needs group and/or global read permissions for the web server to read your login user owned files. Check to see who owns the var/cache/ sub folders and the files they contain, you probably will find it's different.

From the question, you didn't get to the next step. They then have the After Installation settings which are even more restrictive.

Running recommendation is:

500 for directories
400 for files
for media/ and var/
700 for directories
600 for files.

The key to understanding all this is the need to know the server user

On a dedicated server, in the instructions they tell you how to find the server user by checking the apache2.conf or httpd.conf file for the User config line.

Typically, this will be something like nobody, www-data

And so with this bit of information on a dedicated server you then assign all directories and files to be owned by the server user

chown -R {web-server-user-name-here} .

On a hosted system, if you're using Apache MPM-ITK or litespeed, the web server will run with your login name as the server user.

Once the ownership is set properly then you change all the directories and files as follows:

find . -type f -exec chmod 400 {} \;
find . -type d -exec chmod 500 {} \; 
find var/ -type f -exec chmod 600 {} \; 
find media/ -type f -exec chmod 600 {} \;
find var/ -type d -exec chmod 700 {} \; 
find media/ -type d -exec chmod 700 {} \;
chmod 700 includes
chmod 600 includes/config.php

Now comes the massive headache part. Any time you upload files you no longer have write permissions except where you have allowed them (var/, media/) so every time you want to do maintenance outside these folders, you must change everything back by:

find . -type d -exec chmod 700 {} \;
find . -type f -exec chmod 600 {} \;

And on the dedicated server, also probably change ownership to the login user name so you will have permission to write stuff.

Also, if you used Magento Connect (on dedicated server, leave ownership as the web server user), anything it installs will be given 777 permissions.

Because you have to remember to undo and redo the process every time you change something, or are running on a system where the web server needs group/global read permissions, the following permissions have probably become the defacto standard among lesser technically skilled website owners:

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chmod o+w var app/etc
chmod 550 mage
chmod -R o+w media

Magento – Magento uploaded images and 777 permissions

You can download magentocleanup.php and run the file to set the correct Files/Folder permission.

Best Answer

Related Solutions

Magento – 403 error while installing Magento – is the install guide correct

Magento – Magento uploaded images and 777 permissions

Related Topic