Laravel showing "Failed to clear cache. Make sure you have the appropriate permissions"

Question

Laravel was displaying to me "Access denied for user 'homestead'@'localhost' (using password: YES)". One solution for this was clearing the cache and the config cache stored, all this with these three commands:

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

After php artisan cache:clear, terminal says:

Failed to clear cache. Make sure you have the appropriate permissions. (with red background)

Doing the second and third code (php artisan config:clear and php artisan config:cache) works fine! But it still gives me the error when typing the first line. Can anyone explain why?

It worked for me when I changed the sequence (route:clear, config:clear, then cache:clear). — Ihab Shoully, May 10 '20 at 02:13
Use sudo if none of the suggested solutions work for you. ;) — Shafi, Sep 24 '20 at 03:39
This is honestly a problem every single time... im so tired of this problem... i have like a full page of notes on how to fix this, but it seems like the list is getting longer and longer... this time around i cant fix it at all.. deleted all cached files, created all the folders, tried to halt, tried to reload provision, tried to open terminal in administrator, tried to switch my cache drivers.... tried it all, this time it just wount do the storage link, so annoying — ii iml0sto1, Aug 25 '21 at 09:11

score 423 · Accepted Answer · edited Jul 18 '19 at 08:57

423

If the data directory doesn't exist under (storage/framework/cache/data), then you will have this error.

This data directory doesn't exist by default on a fresh/new installation.

Creating the data directory manually at (storage/framework/cache) should fix this issue.

edited Jul 18 '19 at 08:57

Kazmi

1,198
9
20

answered Sep 14 '18 at 11:00

Mytho XY

4,262
1
6
2

Right on the spot! I'm complete with your answer – E.Akio Sep 14 '18 at 14:21
64

I have `storage/framework/cache/data` and am still getting this message. – Jay Bienvenu Aug 07 '19 at 14:48
@JayBienvenu It should work without the data directory anyway - only `storage/framework/cache` this path must already exist (at least for newer Laravel versions 5.7+) - check if you are not overriding the default storage path and if not, check if your cache folder has sufficient permissions for webserver/php ; assuming default FileStore cache - the issue is probably happening in `vendor/laravel/framework/src/Illuminate/Cache/FileStore.php` - method `flush()` - you can start your debugging from there :) – jave.web Sep 23 '19 at 17:15
1

@JayBienvenu, try this https://stackoverflow.com/a/54442312/2140408 – Sid Aug 03 '21 at 09:51
Still having this error too... soooooo annoying... tried basically everything in my long list of possible solutions to this error.. – ii iml0sto1 Aug 25 '21 at 09:15
When I upgrade laravel 5.8 to 6 then I faced this problem. Solution is correct. – kodmanyagha Mar 11 '22 at 07:07

score 134 · Answer 2 · edited Feb 08 '21 at 14:18

134

Try deleting these cached files under bootstrap folder:

/bootstrap/cache/packages.php
/bootstrap/cache/services.php
/bootstrap/cache/config.php

Then run php artisan cache:clear

edited Feb 08 '21 at 14:18

Mahdi Bashirpour

17,147
12
117
144

answered Jan 30 '19 at 13:59

Sid

4,302
3
26
27

1

Cool...Its working, good option when you are working on cpanel and you dont have rights for terminal. – dipenparmar12 Mar 13 '20 at 15:22
I tried everything, my error was `In Find.php line 287: Authentication failed. ` config:cache, cache:clear config:clear, my cache was empty, nothing works. You save me, thanks! – Rodrigo Jun 10 '21 at 14:49
Dident work.. still cant do art storage:link – ii iml0sto1 Aug 25 '21 at 09:31
1

Thank you very much. This worked for me. I already had `storage/framework/cache/data` so above didn't work. – MoDzeus Nov 14 '21 at 16:00

score 60 · Answer 3 · answered Mar 16 '20 at 21:38

60

Calling

php artisan config:cache

before

php artisan cache:clear

fixed the issue.

answered Mar 16 '20 at 21:38

Martin Cup

2,399
1
21
32

Oh, that was it. I moved project's directory and running cache:clear was trying to clear the cache at old path which it didn't have access to (actually folder did not exist). Thanks! – Orkhan Alikhanov Aug 17 '20 at 17:56
2

This is the right answer. You can't clear what you don't have. – Chuck Le Butt Jan 14 '21 at 15:57
Thats the right answer, unfortunate that it even happends with ´php artisan optimize:clear´ – beeftony Jun 23 '22 at 07:45
This work for me. Thnx. – Memo Dec 19 '22 at 13:58
nothing work for me – Alauddin Afif Cassandra May 23 '23 at 15:19

score 44 · Answer 4 · edited Nov 18 '18 at 10:53

44

Just only add folder named data in storage/framework/cache/ and try:

php artisan cache:clear

edited Nov 18 '18 at 10:53

MBT

21,733
19
84
102

answered Nov 17 '18 at 17:34

Kamlesh

5,233
39
50

1

added data folder in /application/storage/framework/cache, and its working. Thank you! – Avinash Raut Jan 11 '21 at 06:50

Saroj Shrestha · Answer 5 · 2021-09-08T09:57:12.427

42

Calling the following 4 commands should fix most of the permission issues on laravel.

sudo chown -R $USER:www-data storage
sudo chown -R $USER:www-data bootstrap/cache
chmod -R 775 storage
chmod -R 775 bootstrap/cache

Basically, chown -R $USER:www-data what this does is it set current user $USER as owner and www-data as group and chmod -R 775 gives 7 to user,7 to group and 5 to other.

#PS: You need to run above command from the laravel project directory, else, you need to provide full path like /var/www/project_name/storage

edited Sep 08 '21 at 09:57

answered Apr 19 '21 at 05:07

Saroj Shrestha

2,696
4
21
45

the problem with this approach is that it keeps resetting to not-working. – Sumit Wadhwa Nov 29 '21 at 07:53
@SumitWadhwa I don't think that's a problem, with the approach, let's say if you go with different user, or updated the permission while pulling code, then it might not work, else it should be fine. Instead, if you don't want to give permissions to current user, you could also another approach by adding user to group `www-data`, like: `sudo usermod -a -G examplegroup exampleusername`, and you just have to give permissions to `www-data` thereafter. – Saroj Shrestha May 21 '22 at 06:42
1

Thank you. In attempting to fix something else, I had set both user and group to www-data, which apparently was causing the specified issue. This fixed it. Thanks! – dgo Apr 02 '23 at 20:58

score 38 · Answer 6 · answered Oct 03 '20 at 04:36

38

First try:

Check if there is a "data" folder inside "storage/framework/cache/". If there is not, then create it manually. (create a new folder with name "data")

Option 2:

If there is a "data" folder inside "storage/framework/cache/". Remove ALL existing folders inside there.

Then final, running this:

php artisan cache:clear

This should fix this issue: "Failed to clear cache. Make sure you have the appropriate permissions."

answered Oct 03 '20 at 04:36

Raymond

1,309
14
10

1

glad to hear @KimTormes – Raymond May 22 '21 at 17:59
1

Finally this worked for me.. Thanks, +1 up vote! – Christopher Kikoti Oct 07 '21 at 09:22
1

you are the best – ahmednawazbutt Oct 29 '21 at 06:36
1

thanks @ChristopherKikoti – Raymond Nov 05 '21 at 18:01
1

thanks @ahmednawazbutt if this solution could help you. – Raymond Nov 05 '21 at 18:02

score 21 · Answer 7 · answered May 10 '21 at 06:44

21

In Laravel 8 I solved my issue by first running composer dump-autoload and then used php artisan config:cache

answered May 10 '21 at 06:44

Abid_niazi_15

825
8
6

4

Works like a charm! – Ajith Gopi Jul 30 '21 at 17:35
This appears to be the solution for Laravel 8 with Homestead and Vagrant. I'm sure it works in other environments as well, but this did the trick for me with these two. The other comments are largely valid when it comes to setting permissions however when doing `ls- l` to see ownership if everything appears correct this step of regenerating autoload files appears to be the quickest way to flush out anything wonky that is too hard to get eyes into. – Jem Sep 19 '21 at 21:44
Worked perfectly for me without requiring any permission changes, thanks! I just ran "php artisan config:cache" first and then I was able to successfully run "php artisan cache:clear". – bstonehill Sep 29 '21 at 21:42
Laravel 5.6 also works! – tanteng Dec 16 '22 at 02:47

Ranjan Fadia · Answer 8 · 2021-08-11T11:45:19.947

9

You should update the permission using the below steps:

Check user using command "whoami" then let output is "ironman"
Run below command if "data" folder exists in the cache directory

sudo chown -R ironman:ironman storage/framework/cache/data/

This will resolve your below issue

edited Aug 11 '21 at 11:45

answered Oct 14 '20 at 10:17

Ranjan Fadia

1,363
1
14
18

1

this is the only proper solution. Others are maybe correct in some cases. Maybe this solution can be apply on "storage & bootstrap/cache" – Ali Özen Apr 10 '23 at 21:53
@AliÖzen Thanks for your genuine comment, you can Upvote this answer to support me. – Ranjan Fadia Apr 12 '23 at 07:39
1

This works when you're unable to delete the `storage/framework/cache/data/` (I'm using Sail and L9)! Make sure to replace "ironman" with the output of the first command of course – pu4cu Jul 22 '23 at 15:18
@pu4cu good to know that it is working for Laravel 9 – Ranjan Fadia Jul 24 '23 at 07:49

score 8 · Answer 9 · answered Mar 05 '21 at 16:36

8

Deleting and adding back the ./storage/framework/cache/data folder worked for me.

answered Mar 05 '21 at 16:36

Thomas Jones

96
1
2

score 5 · Answer 10 · answered Mar 01 '22 at 08:34

5

Delete all subfolders under:

storage/framework/cache/data/

answered Mar 01 '22 at 08:34

Skywalker

1,717
1
22
25

score 3 · Answer 11 · answered Feb 25 '22 at 19:50

3

In my case the problem was I had 'CACHE_DRIVER=memcached' in .env but didn't have memcached installed. Switching to the file driver or installing memcached fixed the problem for me.

answered Feb 25 '22 at 19:50

Step29

51
1
4

In addition you need to start memcached as if not it will simply fail with the "Failed to clear cache. Make sure you have the appropriate permissions." – Alex Aug 05 '22 at 06:11
It was the solution for me. Thanks a lot @Step29! – Petitemo Apr 25 '23 at 13:45

score 2 · Answer 12 · answered Aug 19 '19 at 00:32

I ran my project in a docker container, then later tried accessing it via laragon, I had similar issue, this was due to compiled configurations in /bootstrap/cache/config.php.

I fixed fit by running php artisan config:clear, this deletes the /bootstrap/cache/config.php file automatically.

score 2 · Answer 13 · edited Aug 31 '20 at 20:42

I had the same problem but noticed if you run php artisan config:clear it also by default runs cache:clear right after it so when you run it again there is not cache in it and gives that error. you only need to run php artisan config:clear. I am not sure why cache:clear fails when its ran alone but running the config:clear is a good alternative.

Here is a helpful alias i use to clear everything in the app.

laraclear='php artisan config:cache && php artisan config:clear && php artisan view:clear && php artisan route:clear && php artisan telescope:clear && php artisan debugbar:clear'

Remove any unwanted commands that you do not use in it.

score 2 · Answer 14 · answered Oct 02 '20 at 09:59

2

Can't this solve it?

$php artisan optimize:clear
Compiled views cleared!
Application cache cleared!
Route cache cleared!
Configuration cache cleared!
Compiled services and packages files removed!

answered Oct 02 '20 at 09:59

n00

41
2

score 2 · Answer 15 · edited Feb 10 '22 at 16:12

2

(For MAC Users)

Sometimes, it means current user don't have sufficient permission to the storage/framework/cache/data/ folder. Run

sudo chmod -R ug+rwx storage/framework/cache/data/

then

php artisan cache:clear

Hope sometimes it work for you.

edited Feb 10 '22 at 16:12

radrow

6,419
4
26
53

answered Aug 14 '21 at 18:56

Junayed

91
6

score 1 · Answer 16 · answered Sep 08 '18 at 08:53

1

You may need to clear the autoloader with composer dump-autoload

If that doesn't work you can manually remove the following non-tracked (usually) files to clear the autoloader and cache if they get jammed up:

/bootstrap/cache/packages.php

/bootstrap/cache/services.php

answered Sep 08 '18 at 08:53

jeremykenedy

4,150
1
17
25

I've seen this answer (of deleting both packages and services files from bootstrap/cache folder) on another topic, but why should it be a resolution? Plus, there was no changes after removing them or using dump-autoload. – E.Akio Sep 08 '18 at 16:11
If the autoloader gets jammed up with cached configuration settings that are not what you want such as the DB connections, you can get into a place where they cannot clear. – jeremykenedy Sep 08 '18 at 16:22

score 1 · Answer 17 · answered Apr 11 '21 at 11:13

1

Giving 775 permission to the storage directory solved this problem for me.

sudo chmod -R 775 storage

answered Apr 11 '21 at 11:13

habib

1,454
17
31

score 1 · Answer 18 · answered Mar 17 '22 at 09:35

1

For Laravel Homestead on Windows:

In your .env file, change your CACHE_DRIVER from file to memcached.

Run php artisan cache:clear.

answered Mar 17 '22 at 09:35

score 1 · Answer 19 · answered Dec 04 '22 at 10:59

1

Solution : update the permission :

get user name by this command : whoami
Run command if "data" folderexists in the cache directory.

sudo chown -R YourUSERName:YourUSERName storage/framework/cache/data/

answered Dec 04 '22 at 10:59

Mohammed AL MahmoOd

91
1
8

score 0 · Answer 20 · answered Oct 28 '20 at 17:04

0

Had the same problem on my vagrant/homestead VM. All the other things in this thread didn't help.

The solution was vagrant reload --provision

answered Oct 28 '20 at 17:04

Pixelprotagonist

11
1
5

score 0 · Answer 21 · edited Feb 18 '22 at 08:58

0

I am running my project in Homestead.

My environment :

Ubuntu1~20.04+ Laravel 6.20.26

My output

display real fatal info

Edit src/Illuminate/Filesystem/Filesystem.php 598:14 original code:

if (! $preserve) {
    @rmdir($directory);
}

debug code

if (! $preserve) {
    rmdir($directory);
}

Then re-execute php artisan cache:clear The output changed:

Then, I just resolve Text file busy

edited Feb 18 '22 at 08:58

Md. Yeasin Sheikh

54,221
7
29
56

answered Feb 15 '22 at 11:16

zzr

11
3

score 0 · Answer 22 · edited Nov 22 '22 at 07:53

0

Ensure APP_URL is properly set on .env file. Changing http to https in the APP_URL variable on .env file solved it for me.

edited Nov 22 '22 at 07:53

SEYED BABAK ASHRAFI

4,093
4
22
32

answered Nov 22 '22 at 07:14

Bravo Gidi

11
3

score 0 · Answer 23 · answered Jan 20 '23 at 07:00

In my case, there is no cache available that's why the artisan is unable to delete or reset the cache.
First browse the website and allow it to create some cache then try to clear it.
You can check whether the cache is available or not in directory storage/framework/cache/*

score 0 · Answer 24 · answered Mar 06 '23 at 08:34

For my case, I have all the directory, but we have 2 users.

deployer
www-data

The cache path are created with www-data, but the deployer has no write access . So we need to give the access to the deployer user.

setfacl -R -m u:deployer:rwx /var/www/html

score 0 · Answer 25 · answered Mar 15 '23 at 17:42

You just need to UPDATE the cache folder owner:

First check the current user with: whoami // output: miratech

Second run sudo chown -R mirad:mirad storage/framework/cache/

Finally re-run php artisan cache:clear

This error:

Will be FIXED and you should see something similar to:

enter image description here

score 0 · Answer 26 · answered Mar 24 '23 at 05:54

Ubuntu 20.04 
My Problem is.
UnexpectedValueException 

There is no existing directory at "/home/mehedihasansagor/work-place/all-code/nik/storage/logs" and it could not be created: Permission denied

When I removed these files, Then the problem is solved

config.php
packages.php
routes-v7.php
services.php

php artisan optimize:clear

score -1 · Answer 27 · answered Mar 05 '21 at 14:01

-1

got the same error. try giving chmod 777 permission in the concerned folder

answered Mar 05 '21 at 14:01

Tanzeela Yousuf

1
1
2

1

This was already discussed, the idea is to not give 777 permission – E.Akio Mar 06 '21 at 05:03

score -2 · Answer 28 · answered Apr 14 '21 at 10:24

-2

My guess is you have a permission/ownership problem. Either set up the permissions correctly or recursively delete the cache folder manually and re-create it:

sudo rm -Rf storage/framework/cache
mkdir storage/framework/cache

answered Apr 14 '21 at 10:24

Rishi Ranjan

165
2
8

score -3 · Answer 29 · answered Jan 05 '21 at 05:48

-3

Incase non of these works for you, simply run your php artisan cache:clear command with sudo. e.g. sudo php artisan cache:clear Thank me later~!

answered Jan 05 '21 at 05:48

Devmaleeq

541
6
9

Laravel showing "Failed to clear cache. Make sure you have the appropriate permissions"

29 Answers29

Linked