Laravel throws 'The bootstrap/cache directory must be present and writable' error after update

Question

I used 'composer update', which updated a few packages. During the updating process the website still functions. However, after it says 'The compiled services file has been removed', the website doesn't load and instead says:

Exception in ProviderRepository.php line 190:
The bootstrap/cache directory must be present and writable.

The weirdest thing is, when I run 'composer update' again, the website starts to work again, until the compiled services file is removed, at which point it throws the same error again. I have already tried the usual things that should be done when this error appears (chown -R everything to the right user/group and chmod all the files and folders 664 and 775 respectively).

I don't know what to do anymore, as the error doesn't seem 'correct'..

I forgot to say that 'composer update' updated the laravel framework as well, from 5.4.18 to 5.4.21 — Peter Bennink, May 01 '17 at 11:32
in my case `mkdir -p bootstrap/cache/ && sudo chown -R user bootstrap/cache/` — Adiii, Oct 21 '20 at 15:24

score 230 · Accepted Answer · answered May 05 '17 at 17:31

230

Try this after you have run the composer update:

php artisan cache:clear

answered May 05 '17 at 17:31

Jim Wright

2,444
1
11
7

1

A warning is appropriate here. Before running this on production stop and ask yourself if you really want top wipe out your cache. Otherwise, you might end up crippling your app like it happened to me. – Mugoma J. Okomba Jun 30 '17 at 20:33
1

Not working? i dont have have a cache folder inside bootstrap folder – Shamseer Ahammed Jun 14 '18 at 05:14
Also, if this solution doesn't work straight away - check if you have something like OPCache running you may have to restart your PHP-FPM / clear your OPCache cache. :) – Grant Jun 01 '21 at 01:25

mpalencia · Answer 2 · 2019-11-19T05:06:56.000

31

On your Laravel directory file, run:

sudo chmod -R 777 bootstrap/cache/

edited Nov 19 '19 at 05:06

answered May 01 '17 at 15:37

mpalencia

5,481
4
45
59

7

I'm pretty sure 777'ing any folder on a web server isn't such a good idea security-wise. Besides, 775 should and has worked. – Peter Bennink May 01 '17 at 16:53
I'm sorry, I wasn't clear. 775 has worked **in the past**. At the moment I still have the same problem, as I stated in the original post, I already tried 775'ing and 664'ing everything. The problem is exactly that: I fix what the error says should be fixed, but I still get the same problem. – Peter Bennink May 03 '17 at 10:18
Must be `sudo chmod -R 777 bootstrap` then only runs fine. – 151291 Dec 03 '18 at 11:09

score 15 · Answer 3 · edited Feb 18 '23 at 18:29

15

The best way to resolve this error is:

Open your project folder
Move to the bootstrap directory
Create an empty folder named as cache
Then do PHP artisan cache:clear

This will work for sure

edited Feb 18 '23 at 18:29

Marcin Orlowski

72,056
11
123
141

answered Dec 12 '19 at 06:56

Mohit Poddar

171
1
2

This solved it for me. I just created a new cache folder. Thanks! – Jhonattan Rapprecht Jan 16 '23 at 00:22

score 7 · Answer 4 · answered May 30 '17 at 13:23

Short version: If uploading using something like AWS eb cli Verify if bootstrap/cache folder (not talking about its contents) is being deployed.

Some background behind my answer

I am using Amazon Web Services' Elastic Beanstalk to host my Laravel project. As I just started using Laravel I do not have much idea about its functioning. Two days back My new deployments were all crashing midway with OP's error message.

Earlier that day, I realised that I was not using

 php artisan config:cache

to cache configurations to make things faster. And I added the same in composer.json's "post-install-cmd" and "post-update-cmd" clauses.
And I also added statement in .ebignore file to not upload the content of /bootstrap/cache (as its content is environment dependent a.k.a my localhost configurations have no meaning on my production server)

And facepalm I did not realise that this will stop the bootstrap/cache folder from being uploaded (as Like git, eb cli ignores empty folders).
So, when I started to deploy at night The deployments were meant to crash.

So, now I have just placed empty-placeholder (say) .gitkeep file in bootstrap/cache. And deployments are working once again :)
(Though the problem was so simple I realised the reason after ssh-ing and digging an EBS EC2 instance for some sweet sleep hours ~.~ )

It would be very kind of you if you can tell me why you **downvoted** my answer. Because as much as I can see, it solves a **specific** occurrence of the asked problem. — Vinay Vissh, Nov 19 '19 at 10:00

score 5 · Answer 5 · answered Oct 05 '20 at 16:15

5

For me, I manually created the cache folder inside bootstrap.

answered Oct 05 '20 at 16:15

eaglebearer

2,060
1
13
9

Me too, just delete the current cache folder and recreate it, then problem will be fixed – Giangimgs Jun 20 '22 at 04:25
That is an easy way to fix this prob. thanks – Sagor Islam Oct 15 '22 at 11:43

score 4 · Answer 6 · answered Feb 12 '20 at 10:27

4

Try this too after you have run the composer update:

php artisan config:clear

answered Feb 12 '20 at 10:27

Waleed Muaz

737
6
17

score 3 · Answer 7 · answered Aug 31 '18 at 17:03

Im using cmder on windows 10 in non elevated mode (Non-Admin). command php artisan cache:clear did not work for me. The folder bootstrap/cache did not exist. I created the folder and removed readonly from both bootstrap and bootstrap/cache folder. Both composer install and composer update are working now.

score 3 · Answer 8 · answered Nov 24 '19 at 23:56

3

sudo chmod -R ug+rwx storage bootstrap/cache

hopefully, this will solve the problem.

answered Nov 24 '19 at 23:56

Arif.0o7

61
2

mohamed elshazly · Answer 9 · 2019-04-03T12:11:17.540

1

it work for me run in project folder

 sudo chmod -R 777 bootstrap/cache

than run

 composer update

than run

 cache:clear

edited Apr 03 '19 at 12:11

answered Feb 07 '19 at 13:21

mohamed elshazly

508
3
8

2

it's not bootstrap/cashe but bootstrap/cache – Apr 02 '19 at 12:53
You shouldn't advice to add chmod 777 to a directory. This is a major security flaw. That way anyone could read, write and execute files in that folder. You can test the security of a given chmod here: https://chmod-calculator.com/ – Francisco Solis Jan 23 '23 at 19:39

score 1 · Answer 10 · answered May 19 '21 at 09:06

1

First make sure bootstrap/cache dir is exist if not create a new one mkdir -p bootstrap/cache/
Then run php artisan config:cache

answered May 19 '21 at 09:06

Ayman Elshehawy

2,746
23
21

score 1 · Answer 11 · edited Oct 09 '21 at 23:38

1

Simple. There are applications that can block the directory. Like google drive synchronizer, One driver synchronizer, or any other application that is using windows explorer.

Delete cache folder. Create this again.

edited Oct 09 '21 at 23:38

cigien

57,834
11
73
112

answered Oct 09 '21 at 22:53

Lesnier Gonzalez

39
2

score 0 · Answer 12 · answered Dec 17 '19 at 07:21

0

Try executing the following commands in your project root directory

composer update

then do

composer dumpautoload

this will avoid the necessity of messing with cache files which may lead to whole new sort of issues

answered Dec 17 '19 at 07:21

Software Developer

778
8
14

CodeToLife · Answer 13 · 2020-06-29T14:14:04.410

0

I don't imagine what I got done wrong with that before and no games around with that cashclearings had sense. But as it claims there was no 'cache' folder inside /bootstrapp . Had to have create it manually. Now it all rocks ok again

edited Jun 29 '20 at 14:14

answered Jun 29 '20 at 14:06

CodeToLife

3,672
2
41
29

Zellerich · Answer 14 · 2022-01-19T11:44:33.740

0

I had to create these five folders to be able to run artisan again.

mkdir bootstrap/cache
mkdir storage/framework
mkdir storage/framework/cache
mkdir storage/framework/views
mkdir storage/framework/sessions

Answer was found in this related question: "Please provide a valid cache path" error in laravel

edited Jan 19 '22 at 11:44

answered Jan 19 '22 at 10:02

Zellerich

96
2
8

score 0 · Answer 15 · answered Feb 03 '23 at 01:27

0

In my case, I've found out that the bootstrap/cache is missing in my project during a fresh clone.

Re-adding the cache directory manually solved my issue.

Then running composer install now works fine.

answered Feb 03 '23 at 01:27

Gams Basallo

1,071
1
11
16

Murat Çakmak · Answer 16 · 2023-03-26T20:00:28.110

OS: Linux Ubuntu

If you are using Docker, maybe try this:

services:
php:
    restart: always
    container_name: app-php
    user: 'www-data:www-data'
volumes:
    - ./:/var/www/html # synchronous

And Open Terminal

sudo chown -R $USER:$USER <your_project>

Now try this:

docker exec -it <your_container_name> /bin/bash
chown -R www-data:www-data bootstrap/
chown -R www-data:www-data storage/

ls -l # You are see folders/files USER/GROUP
php artisan cache:clear # success
php artisan route:clear # success
composer dump-autoload # success

score -1 · Answer 17 · answered Aug 25 '17 at 22:09

-1

If a web server (e.g. Apache or Nginx) is being used as a front-end the solution is to make the directory bootstrap/cache owned by web server group. For Nginx:

 $ sudo chgrp -R nginx bootstrap/cache

answered Aug 25 '17 at 22:09

Mugoma J. Okomba

3,185
1
26
37

Laravel throws 'The bootstrap/cache directory must be present and writable' error after update

17 Answers17

Linked

Related