Level 2
Check write permissions on storage folder!
Try: "sudo chmod -R 777 storage/" (i known that 777 is a bad thing to do, only do this to test).
1 like
Feb 24, 2015
7
Level 1
Blank 500 error pages instead of Traceback in Laravel 5.0.1
I just set up a new site for development, and for some reason things like syntax errors are producing a blank white page, with no laravel debug info. My app is definitely in debug mode, because 404 errors correctly display the traceback, and I can confirm this in tinker. Anyone have any ideas on what would cause this?
Level 1
Huh, that worked, and I wasn't expecting it to. As I always do immediately after installing a new laravel project, I set owner:group to www-data:developers, and permissions to 775. But apparently something in there didn't have the right permissions, because re-running those commands made it all work now. I'm not sure how I would have gotten views to work in the first place while still having permission errors, nor how 404 errors seemed to work just fine, but I must have messed something up.
Thanks for pointing me in the right direction!
Level 65
775 is fine, probably www-data isn't the web server user. Check what user it is.
cat /etc/passwd | grep www // or just omit the | grep www
Level 1
No, it is. Sorry for not being clear. I just ran
sudo chown -R www-data:developers storage/
sudo chmod -R 775 storage/
and it all works now. The confusing part to me is that, I'm pretty sure I ran those exact commands after installing the framework (in fact, I just now looked back through my bash history, and I did run them). So either I messed up the permissions somehow between then and now, or something else happened. Either way, it does work now, and I know where to look if I get white screens instead of errors from now on.
Level 65
Weird one then :)
Please or to participate in this conversation.