services.json failed to open stream: Permission denied in Laravel 4

Question

I was playing around with a working Laravel 4 installation and moved everything into a sub folder. Then I decided to not do that and I moved it all back (all via the command line):

mv * /folder

and then

cd folder
mv * ../

Now, the site is throwing the following error:

file_put_contents(/var/www/quantquote/app/storage/meta/services.json): failed to open stream: Permission denied

Here is a screenshot of the full error:

https://i.stack.imgur.com/J8uTM.png

I've already tried setting permissions on the /storage folder to 777 to no avail.

Try running both `find app/storage -type d -exec chmod 777 {} \;` and `find app/storage -type f -exec chmod 777 {} \;` — Collin Henderson, Jul 30 '13 at 20:19
@CollinHenderson that did it, thanks. can you explain what this did? — JasonStockman, Jul 31 '13 at 00:52
Those commands changed the permission of all directories and files under `app/storage` to `777`. — Rubens Mariuzzo, Jul 31 '13 at 04:39
@RubensMariuzzo is correct. I'm going to copy this to a proper answer if you'd like to accept it. — Collin Henderson, Jul 31 '13 at 13:17
Forgive my naivete, but shouldn't we avoid giving everyone read, write, and execute privileges to this directory? Does the user that needs access to this location depend on the owner of the php program? — Spencer Williams, Nov 26 '13 at 23:56
setting the folder permissions to 777 can cause security issues. Please consider changing it to 775 instead, preventing giving write access to others. — eaykin, May 22 '14 at 10:54
This post is the correct answer to your question [Permission denied in Laravel 4][1] [1]: http://stackoverflow.com/questions/14345174/cant-make-laravel-4-to-work-on-localhost — Sam Arul Raj T, Nov 11 '14 at 09:45

score 29 · Answer 1 · edited Jun 20 '20 at 09:12

29

Spent a whole day for solving this and this command simply solved my problem.

If your permissions are 777 for Laravel App folder and you still get this error, it's because SEliux has blocked it. You can easily unblock your application's folder using this command:

su -c "chcon -R -h -t httpd_sys_script_rw_t /usr/share/nginx/YOUR_LARAVEL_APP/"

That's it!

BTW never disable SElinux: http://stopdisablingselinux.com/

edited Jun 20 '20 at 09:12

Community

1
1

answered Dec 09 '14 at 11:17

Sky

4,244
7
54
83

1

thanks so much! I'd like to add that my command ended up being `chcon -R -h -t httpd_sys_script_rw_t /var/www/laravel` since I am on a local machine running as root already, in case anyone else is vaguely sleep deprived and not reading things correctly. Again, thanks! – maggiekh May 18 '15 at 00:18
1

This is the answer to so many questions with Laravel and logging. Thanks for that. Saved another day of debugging – prog_24 Feb 01 '16 at 13:52

score 23 · Answer 2 · answered Jul 31 '13 at 13:18

23

As I stated in my comment:

find app/storage -type d -exec chmod 777 {} \;

find app/storage -type f -exec chmod 777 {} \;

This will chmod all directories and files in app/storage to 777.

answered Jul 31 '13 at 13:18

Collin Henderson

1,154
10
22

5

I would set the permissions to 775 instead of 777 and configure the file ownerships and groups accordingly. i.e. the group of the web server and the app/storage folder will be the same. – eaykin May 22 '14 at 10:52
4

As a security precaution, I'd recommend `chmod -R ug+rwX,o-rwx .` This will set directories only to execute, and prevent people outside of the group doing horrible things to your files. – DanielM Dec 01 '14 at 17:31
1

To read how to set your directory permissions in the right way check this answer: http://stackoverflow.com/a/37266353/987864 – Daan Oct 13 '16 at 08:30

score 11 · Answer 3 · answered Jul 31 '13 at 04:46

11

As the problem is related to permissions try re-giving the right permissions to app/storage and all its sub-directories and file.

You can do so from the root path of your Laravel app typing:

chmod -Rvc 777 app/storage

If for some reason this doesn't work, try:

find app/storage -type d -exec chmod -vc 777 {} \;
find app/storage -type f -exec chmod -vc 777 {} \;

answered Jul 31 '13 at 04:46

Rubens Mariuzzo

28,358
27
121
148

_Please, if you will downvote this answer then also provide any explanation so we can improve it._ Thanks. – Rubens Mariuzzo Sep 07 '15 at 18:57
Downvote: never use chmod 777 ! Suggesting such a dangerous command as a solution should be banned from SO. – Елин Й. Jan 13 '17 at 11:13
@ЕлинЙ. what would you recommend instead? – Rubens Mariuzzo Jan 13 '17 at 18:13

Igor Parra · Answer 4 · 2020-01-13T19:55:49.647

When chmod 777 or chmod 775 fails check that subdirectories really exists:

app/storage/
├── cache
├── logs
├── meta
├── sessions
└── views

in case these folders does not exists you must to create it:

cd app/storage/
mkdir meta logs cache sessions views
cd ../
find storage -type d -exec chmod 775 {} \;
find storage -type f -exec chmod 664 {} \;

UPDATE 2016 for laravel 5+

In a default Laravel 5+ application structure, storage is at the same level than app. So the previous command becomes:

cd storage/
mkdir meta logs cache sessions views
find . -type d -exec chmod 775 {} \;
find . -type f -exec chmod 664 {} \;

https://laravel.com/docs/5.0/structure

This answer helped me, I needed to create the folder structure under the storage folder. But in my case (for Laravel 5.0) the views, sessions and cache folders had to be in a subfolder named "framework". — BruceHill, Jan 21 '16 at 21:44

Eric Estrada Gómez · Answer 5 · 2015-04-09T21:57:55.237

7

If you're using CentOS7, follows these steps:

Change app/storage directory ownership
```
chown apache:apache app/storage
```
Change app/storage permissions
```
chmod -R 775 app/storage
```

Prevent SELinux from blocking the app/storage directory

su -c "chcon -R -h -t httpd_sys_script_rw_t [fullpath]/app/storage"

edited Apr 09 '15 at 21:57

answered Apr 09 '15 at 20:13

Eric Estrada Gómez

71
1
3

score 6 · Answer 6 · edited Nov 11 '15 at 06:15

6

just type this on terminal:

php artisan cache:clear

edited Nov 11 '15 at 06:15

Ori Lentz

3,668
6
22
28

answered Nov 10 '15 at 11:17

AmirAgha

135
2
6

score 5 · Answer 7 · edited May 23 '17 at 12:34

5

Never run a 777, in recursive mode. It's a security issue. For now, remove the services.json file, and try this :

Laravel 4: Failed to open stream: Permission denied

edited May 23 '17 at 12:34

Community

1
1

answered Mar 05 '14 at 20:58

François

706
1
7
9

3

Please post the relevant parts from the link, if the link dies, then the answer will not be helpful in the future. – Popo Mar 05 '14 at 21:18

score 0 · Answer 8 · edited Nov 14 '16 at 10:36

0

Try these commands one by one:

setenforce 0
setsebool -P httpd_can_network_connect_db on

edited Nov 14 '16 at 10:36

Petter Friberg

21,252
9
60
109

answered Nov 14 '16 at 10:31

Mahendra Parab

9
2

Why there is no up vote for this one? This works like a charm! :D thanks! – Ram Guiao Jul 31 '17 at 13:47
Because it is disabling SELinux, instead of learning how to use it, which is dangerous advice. Additionally, the poster hasn't actually explained what this 'solution' is doing. – charliefortune Nov 21 '19 at 12:29

services.json failed to open stream: Permission denied in Laravel 4

8 Answers8

Linked