Question

Laravel 4.1 - blank page

I made a new laravel app today (tested it locally and is working), then I pushed it to bitbucket and cloned it on my droplet. After that I did a sudo chmod 777 -R app/storage, but I’m still getting a blank page on the root.

My droplet is running Cent OS 6 and other (older) laravel apps are working fine.

Any ideas?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

In my case there STILL IS a problem with paths:

W Apache error log I see this [Tue Sep 01 08:20:02.915639 2015] [:error] [pid 18311] [client 101.12.127.169:37789] PHP Warning: require(/var/www/niepozwalam/bootstrap/vendor/autoload.php): failed to open stream: No such file or directory in /var/www/niepozwalam/bootstrap/autoload.php on line 17 [Tue Sep 01 08:20:02.915737 2015] [:error] [pid 18311] [client 101.12.127.169:37789] PHP Fatal error: require(): Failed opening required ‘/var/www/niepozwalam/bootstrap/vendor/autoload.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/niepozwalam/bootstrap/autoload.php on line 17

As you see, the path /var/www/niepozwalam/bootstrap/vendor/autoload.php should be related to website root and is not.

I don’t know how to solve this issue

After installing laravel in my server .the home page displaying as blank page without any error message.How can i solve it?

How are you serving your apps? Are you seeing anything in the web server’s log files (e.g. /var/log/nginx/error.log or /var/log/apache2/error.log)?