Make sure you haven't messed up one of your config files. That happened to me once.

Check your server / laravel log files if no errors are displayed on screen.

Check access permissions on storage (and all subfolders) - these folders need to be writeable.

Check that you haven't gone into maintenance mode ... you might need to call

php artisan up

Unlikely, but sometimes it's the obvious answer. :)

 sudo chmod -R 777 app/storage
 php composer.phar dump-autoload

and if it doesnt work, got tail your php error log.

and you still cant find it, do the old fashion way of var_dump('here'); die;

untill you get to the place it breaks.

I started seeing this after I upgraded to Laravel 4.1. There seem to be a few configuration issues that cause it. In my case, I forgot to set permissions to app/storage/sessions. To trap errors that break Laravel before it starts handling errors itself, put this at the end of public/index.php:

try {
    $app->run();
}
catch (\Exception $e) {
    var_dump($e);
}

(you probably won't want to leave that in a production system; just to find a particular issue so it can be fixed)

Hi. Thanks for replies.

A few things:

1 -

I did chmod 777 storage

drwxrwxrwx 9 root admin 306 11 Mar 07:08 storage

2 - If I try to access a controller that does not exist I get this:

Error in exception handler: The stream or file "/Applications/XAMPP/xamppfiles/htdocs/ben/app/storage/logs/laravel.log" could not be opened: failed to open stream: Permission denied in /Applications/XAMPP/xamppfiles/htdocs/ben/vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:70

3 - If I try to access an existing controller I get a blank page

4 - When I check any of these pages nothing goes inside laravel.log

5 - I don't think I am in maintenance mode since I still get error fro inaccessible controllers as I mentioned above. I get this anyways:

php artisan up Mcrypt PHP extension required.