Issue in cache laravel

@omeratayilmaz Yes, I've checked the laravel.log file, but no errors are appearing there.

@mounak Start by showing what the error is. 500 is just a status code that denotes a server error. Check the logs at storage/logs/laravel.log.

@JussiMannisto Nothing show in laravel.log at time get server error i have checked laravel.log but there nothing show any error but after use this command sudo chmod 777 storage && php artisan cache:clear && php artisan config:clear it start working. Also i mention that i am using aws lightsail ubuntu server and also using laravel scheduler.

@mounak If you just chmod the directory, the files inside might still not be writeable. You have to check the file permissions too.

But 0777 is really insecure. That means any user can overwrite the files. You should instead make sure the files and directories are owned by your web server user, e.g. www-data or apache. Then you can use the typical 0644 for files and 0755 for directories.

If you still don't get any errors in laravel.log after that, it's an indication that something is going wrong before the framework finishes booting up. You should check your web server logs.

You should also run all artisan commands as the web server user. Otherwise some files and directories - particularly those inside storage/framework/ - may get created with the wrong owner. That could also explain your cache issues if you're using the file based cache driver.

Which cache driver are you using?

@JussiMannisto cache_driver=file. should i run all this commad : php artisan cache:clear php artisan config:clear php artisan route:clear php artisan view:clear

and also chmod 0775 run this command.

@mounak

1. What web server are you using: Nginx, Apache, or something else?
2. What user does the web server run as: www-data, apache, or something else?

Let me know if you can't figure these out.

and also chmod 0775 run this command.

That changes the ownership of a single file or directory. So if you run chmod 0775 storage, the file storage/laravel.log will be unaffected.

should i run all this commad : php artisan cache:clear php artisan config:clear php artisan route:clear php artisan view:clear

If you run artisan commands, you should run them as the web server user, e.g.:

sudo -u www-data php artisan cache:clear

If you run them as yourself, any directories or files created will be owned by you, and Laravel won't be able to modify them.

@JussiMannisto What web server are you using: Nginx, Apache, or something else? Ngnix