Laravel shows blank page (continuously loading)

Question

After having installed Laravel 5.1 on a local desktop, I installed it on a webserver (debian 8, php 5.6.17), set the directory permissions for storage and bootstrap/cache tp 1777. All worked fine. Next I installed it on another webserver, same method, same settings, but now it only shows a coninuously loading page. Tried a re-install, with the same result

Started manual debugging and the code falters in the index.php at $kernel->terminate(.... I also changed caching and session storage to redis, which made no difference.

Have been reading through the 'blank pages' posts, and been googling on it too, without any helpfull result so far.

If I let the script die before the '$kernel->terminate(...' line it shows the page else it just shows the page loading ... Unfortunately, pagination, and sorting a.o. do not work due to the premature ending of the script.

Anyone encountered this peculiar behaviour before

Cheers,

[look here](http://stackoverflow.com/questions/20678360/laravel-blank-white-screen) — Pionas, Feb 10 '16 at 08:10
Did you change permission in public folder and storage folder to writable? — John Roca, Feb 10 '16 at 08:41
Yes, storage and sub dirs are currently 777 and bootstrap/cache dito. Did that on installation — C. Gellings, Feb 10 '16 at 09:44
Probably permission issue. try setting right permission. example `sudo chmod -R 775 /var/www/laravel/storage` and sudo `chown -R :www-data /var/www/laravel` — Emeka Mbah, Feb 10 '16 at 10:05

score 1 · Answer 1 · answered Feb 10 '16 at 11:16

1

It happens most probably due to permission issue.Try this

chmod 777 -R storage/

Storage folder existed inside the Laravel folder.If nothing works, try to give full permission to Laravel Project folder and try again.

answered Feb 10 '16 at 11:16

see my response to John Roca above, I even set the sticky bit to 1 chmod -Rv 1777 ./storage and checked the result with the verbose (v) option – C. Gellings Feb 10 '16 at 12:10

score 0 · Answer 2 · answered Feb 19 '16 at 10:06

0

Problem caused by NFS filesystem. It doesn't allow file locking. Solved the problem by writing sessions to memcached

answered Feb 19 '16 at 10:06

C. Gellings

141
1
11

score 0 · Answer 3 · edited May 23 '17 at 12:16

0

For me what fixed my issue was removing some laravel comment in my blade files. Especially comments of html code on multiple lines. It took afew days to figure it out!! Very annoying. {{-- html code here --}}

see: Blade Comments in Laravel are crashing apache Laravel - Blade comments , blade rendering causing page to crash

edited May 23 '17 at 12:16

Community

1
1

answered Feb 28 '16 at 15:39

cdoshi

23
6

Laravel shows blank page (continuously loading)

3 Answers3