There is no existing directory at /storage/logs and its not buildable: Permission denied

Question

I have a problem with my Laravel deployment on a OVH web server. After made

composer update

php artisan cache:clear

php artisan route:clear

php artisan dump-autoload

I have this answer:
There is no existing directory at /storage/logs and its not buildable: Permission denied
I put all the files on 777 chmod but I have always this answer.

just as a note to anyone who tries this and it is not used to artisan commands or composer (we all make the same mistake from time to time) the command is composer dump-autoload, not artisan :) cheers! — Nelson, Apr 10 '20 at 21:16
php artisan dump-autoload? you might mean 'composer dump-autoload' — steve sonius, May 25 '20 at 00:12
In my case, I just forgot a `;` in a file... so check if you don't have errors in any files. — Madriesen, Oct 21 '21 at 12:27

score 246 · Answer 1 · edited Aug 27 '19 at 12:49

246

Please try the following commands

php artisan route:clear

php artisan config:clear

php artisan cache:clear

Note: In case you are a Homestead & VirtualBox user, please be sure that your VirtualBox is up to date.

It helped in this thread at laracasts

edited Aug 27 '19 at 12:49

Novocaine

4,692
4
44
66

answered Jun 27 '18 at 14:45

frankfurt-laravel

3,731
2
20
29

2

This sequence (route, config, then cache) worked for me! – Ihab Shoully May 10 '20 at 02:00
1

For last command: Failed to clear cache. Make sure you have the appropriate permissions. – Chanchal Raj Jun 18 '20 at 13:53
3

Chanchal: Here you go https://stackoverflow.com/questions/52231248/laravel-showing-failed-to-clear-cache-make-sure-you-have-the-appropriate-permi Was a one sec search. – frankfurt-laravel Jun 18 '20 at 17:34
This works great... in my case it was also the config... But does anyone understand what the underlying problem is? Is it an issue in the configuration? or an error in how the config cache is built (e.g. ignoring .env or something like that?) It seems that folders are there, have the right permissions, etc. so something seems to be smelly, I just can't point at it... – Canelo Digital Jul 02 '20 at 19:48
Only Jesus know why this is related with `Redis error: cannot assign requested address ` but now is fixed. – insign May 11 '21 at 05:34
If this problem persists while running Laravel locally inside a Docker container, make sure you execute these commands inside the container. – qotsa42 Jan 26 '22 at 18:18

score 133 · Answer 2 · edited Aug 13 '19 at 13:50

133

Clear the cache and config, then deploy to the live server.

If you've already uploaded to the live server, then you have to follow these steps:

Delete bootstrap/cache/config.php
Delete all log files in storage/logs.

edited Aug 13 '19 at 13:50

Chris Forrence

10,042
11
48
64

answered Dec 14 '18 at 09:28

Aditya Chauhan

1,331
1
6
2

3

The best answer for shared hosting – Ali Hassan Feb 08 '20 at 22:57
I do this and it gets rid of the error stated in the question here, but then I get a 500 Internal Error in its place. Any thoughts? – hannebaumsaway Feb 02 '21 at 04:26
Great, thanks! Worked for me with Docker. – shasi kanth Jul 12 '21 at 18:05
Looks kind of crazy but it actually worked, have been messing with permissions which looked fine for hours. Yet it was not permission issue at all. Thanks much! – Lema Jul 10 '23 at 11:02

score 63 · Answer 3 · edited Dec 21 '22 at 11:42

63

You don't need to add any permission on the storage file.

The main problem here is in the compiled file, and due to which laravel try to show an error.
By default in laravel, storage file not having permission to show in the console (error shows from the error.log file).
So the thing you need to fix is to fix compile file. which can be done thought this single command

Use this

php artisan optimize:clear

This command will clear all your cache

Compiled views
Application cache
Route cache
Configuration cache

edited Dec 21 '22 at 11:42

TarangP

2,711
5
20
41

answered Apr 02 '19 at 11:50

Vikas Rinvi

1,158
12
28

7

You're a life saver! I had some stupid CORS issue and solved by the command. – Amirreza Nasiri Jun 21 '19 at 17:56
3

I am happy that it helps. @AmirrezaNasiri Thanks for your comment too. – Vikas Rinvi Jun 21 '19 at 18:01
1

Worked, even if it said "Failed to clear cache. Make sure you have the appropriate permissions." :-) – Alexander Taubenkorb Nov 19 '19 at 09:06

score 29 · Answer 4 · edited Jun 10 '21 at 12:29

29

After changing local conf i got the same error over and over, try this, probably will help.

rm bootstrap/cache/config.php

and then

php artisan cache:clear

depending on your scenario, reloading auto-loader file can solve your issue, for that use :

composer dump-autoload

or sometimes just try :

composer install

this do the two the commands listed above.

edited Jun 10 '21 at 12:29

Sølve T.

4,159
1
20
31

answered Dec 18 '19 at 13:53

dijux

541
5
8

Well this solve the issue. Thank you so much! – Mystogan Nov 15 '21 at 01:56
1

just removing the config file and clearing the cache worked for me (no need for composer commands).. thx for the help – Dany Balian Nov 28 '21 at 18:13

score 5 · Answer 5 · answered Sep 09 '18 at 11:09

5

go to your vagrant

then run

vagrant ssh

php artisan config:cache

answered Sep 09 '18 at 11:09

Farid shahidi

318
4
9

Could you give a little more detail on what this accomplishes – PilouPili Sep 09 '18 at 12:11
First you need to run your vagrant env, then you should connect to its bash script using vagrant ssh, config cache will clear the cached config files, then rebuild them. – Farid shahidi Dec 06 '20 at 08:25

score 5 · Answer 6 · answered Feb 07 '20 at 14:12

Run the following command if you can access your server terminal

php artisan route:clear && php artisan cache:clear && php artisan config:clear && php artisan config:cache

If you are on shared hosting and cant access the terminal go to your web route file in routes/web.php and make a temporary link such as shown:

Route::get('reset', function (){
    Artisan::call('route:clear');
    Artisan::call('cache:clear');
    Artisan::call('config:clear');
    Artisan::call('config:cache');
});

Then go to http://your-domain/reset to execute the commands. there after you can now access your website as normal

score 3 · Answer 7 · answered Oct 06 '18 at 17:26

3

If you are using homestead (vagrant) in Laravel then follow the steps @Farid shahidi provided

vagrant ssh
cd /home/vagrant/code <-- your file usually resides here; see your Homestead.yaml configuration
php artisan config:cache

answered Oct 06 '18 at 17:26

jrran90

668
12
18

1

If you are using vagrant/docker/etc make sure to run `php artisan config:cache` from _inside_ the machine. – Erik Donohoo Jan 13 '20 at 23:28

score 2 · Answer 8 · edited Oct 29 '21 at 15:55

2

This one-line command solves my issue:

php artisan config:cache

edited Oct 29 '21 at 15:55

linktoahref

7,812
3
29
51

answered May 10 '20 at 10:56

Felix Labayen

385
3
8

score 2 · Answer 9 · edited Sep 29 '20 at 20:00

2

You Have to try artisan command in this way

```
php artisan cache: clear
```
```
php artisan config:cache
```
```
php artisan cache: clear
```

edited Sep 29 '20 at 20:00

β.εηοιτ.βε

33,893
13
69
83

answered Sep 29 '20 at 14:13

neel

111
3

Thanks! This helped me a lot! – Donny van V Dec 01 '20 at 13:29

score 1 · Answer 10 · answered Apr 17 '20 at 21:08

1

Delete bootstrap/cache/config.php from your laravel deployment on the server.

answered Apr 17 '20 at 21:08

r3n4y

77
3

simple and working solution thanks alot – Sohaib Khan Mar 19 '22 at 08:38

score 1 · Answer 11 · answered Feb 08 '23 at 20:22

1

For those of you using sail, do:

sail artisan optimize:clear

answered Feb 08 '23 at 20:22

Ulrik McArdle

601
4
9

score 0 · Answer 12 · edited Jan 22 '19 at 17:54

0

Please run the below commands:

php artisan route:clear
php artisan config:clear
php artisan cache:clear

edited Jan 22 '19 at 17:54

ETO

6,970
1
20
37

answered Jan 22 '19 at 17:22

Eliecer Narvaez

87
1
2

score 0 · Answer 13 · answered Feb 05 '19 at 21:47

0

This one worked for me in case your project is located within /var/www/html/

sudo chmod -Rf 0777 /var/www/html/{project-name}/bootstrap/cache sudo chmod -Rf 0777 /var/www/html/{project-name}/storage

answered Feb 05 '19 at 21:47

Tony Okoth

157
1
4

score 0 · Answer 14 · answered May 15 '19 at 10:02

0

You need to run this command from the terminal.

php artisan config:clear
php artisan config:cache

answered May 15 '19 at 10:02

Jigar

3,055
1
32
51

Buddhika · Answer 15 · 2020-06-17T02:19:15.337

0

I got the same issue, I change the permissions of the folders inside the the storage folder.

chmod 777 <folder_name>

I'm not sure about this security wise. but this resolve my problem.

I change my file settings to 755 also work for me.

edited Jun 17 '20 at 02:19

answered Jun 16 '20 at 17:38

Buddhika

163
1
7

1

Using `777` permission is a REALLY bad permission and it has so many security issues because it give `RWX` permission to every body! – Farbod Ahmadian Jun 16 '20 at 19:41
1

@FarbodAhmadian thanks, I change my permissions to 755 also work for me. I edit my above answer also after your comment. – Buddhika Jun 17 '20 at 02:20

score 0 · Answer 16 · edited Jun 18 '20 at 07:38

0

try this

remove your "vendor" folder

Run "composer install" or "composer install --ignore-platform-reqs" on your cmd or terminal

php artisan config:cache

php artisan config:clear

php artisan cache:clear

php artisan route:cache

php artisan view:clear

php artisan config:cache

if you are using linux:

service apache2 restart (just in case)

if you using xammp:

just restart your xammp

edited Jun 18 '20 at 07:38

jizhihaoSAMA

12,336
9
27
49

answered Jun 18 '20 at 07:02

Masudzzaman Ullash

9
3

There is no existing directory at /storage/logs and its not buildable: Permission denied

16 Answers16

Linked

Related