[SOLVED] [L5] New: Can't display errors, 500 internal server error

• Got any error settings in virtual host config?
• Does it work for plain PHP file with error?
• Got Xdebug installed?
• What is the http status code of the blank page?

whoops is no longer part of L5. Here's the link to install it back: https://laracasts.com/discuss/channels/general-discussion/whoops-removed-from-laravel-5?page=4

You could also just use Xdebug like @bashy wrote.

@andy the issue is that he's not seeing errors at all not that he's not seeing useful or pretty errors. ;)

Did you give your tmp folder 777 permission? Or delete storage/meta/compiled.php file. or try " 'php artisan optimize' in your app's directory

Hi, to everyone for answering.

@bashy

Got any error settings in virtual host config? error_reporting(-1), display_error = On Does it work for plain PHP file with error? It works, but as i said before, if i write anything wrong inside the controller, i get only a blank page Got Xdebug installed? No What is the http status code of the blank page? 500 Internal Server Error

@willvincent I see nothing :(

@kingpabel I will check

I will check the status code, it seems that something wrong is happening, since i get an status code 500.

I noticed a similar problem some time ago when hhvm was enabled.

Try disabling it or remove it from Homestead.yaml:

hhvm: false

Check log files for web server (Apache/Nginx) and PHP. Also anything in Laravel's log file?

You also haven't said what your web server setup is. Homestead? WAMP? XAMPP? Apache/Nginx?

the WelcomeController, method index() works correctly, if i do an echo 'Hi'; die; I get 'Hi', but if i write something wrong like function_unkown();, i get nothing

I might be reading this wrong or I've must have hit my head pretty hard yesterday snowboarding but isn't this expected behavior?

You can't create "Unknown Function" as a method, that doesn't make sense.

but if i do the same in the public/index.php, errors are showing.

Because the code is being executed procedurally.

ETA:

Can you show us some code? Try adding this to your routes.php file:

Route::resource('demo', 'DemoController');

And visit /demo, do you see any errors now? Something along the lines of DemoController not found.

They probably mean normal PHP errors.

@alenabdula I took it to mean, something like this inside the welcome controller:

// This works
public function index() {
  echo "Hi";
  die();
}

// This doesn't work, obviously, but does not display any errors either.
public function index() {
  foo_bar_baz() // Call to non-existent function, should make php blow up.
}
// results in blank page, NOT error message as expected.

The latter should result in a FatalErrorException Call to undefined function App\Http\Controllers\foo_bar_baz() (it does for me)

@Eduardo Perhaps your env file isn't being read for some reason. Try manually setting debug mode to true within config/app.php

// Update to this:
'debug' => true, //env('APP_DEBUG'),

But, if @alenabdula is correct and rather than your unknown_function() being within the index method, but instead being created as a different method, that's not going to cause an error since it wouldn't be getting called. That seems fairly obvious though.

That seems fairly obvious though.

@willvincent I guess I was thrown off by "I'm new here" thinking OP is a beginner with Laravel so what seems so obvious to us, might be difficult for them. Idk. @Eduardo can you elaborate little bit, show us some code examples maybe...?

@Eduardo You can select your answer to be the correct one. Your post would be automatically solved.

@Eduardo For your first question, it was in your log right? The documentation tells you about that ;) For your second question I would also refer to the documentation: http://laravel.com/docs/5.0#configuration (Read under the permission header)

Another person not following the configuration guide :)

Also on your dev server you should have PHP to display errors, maybe Xdebug as well?

@bashy

As i mentionned before, my php.ini is configured to display errors, but laravel overrides that configuration, hidding the errrors, so i wasn't able to see the exception, telling me that the folder storage wasn't writtable. Easy to debug if it wasn't for that.

@Eduardo I use Xdebug so that could differ. Also you would be checking error logs for web server? There should always be some sort of way to see them even if Laravel overrides the displaying of them on the page.

sitesense's answer solved it for me also when using Homestead: "

I noticed a similar problem some time ago when hhvm was enabled.

Try disabling it or remove it from Homestead.yaml: hhvm: false

"

We need to care about the Directory permission and ownership. For solving this problem we have to set the app directory permission to 777

sudo chmod 755 -R {app_directory}

And change the ownership of the /storage directory too

chmod -R o+w {app_directory}/storage

For those of you having this problem with HHVM enabled on Homestead, You can modify Foundation\Bootstrap\HandleExceptions.php to display errors while HHVM is being used.

The fix is posted here: https://github.com/laravel/framework/issues/8744#issue-76454458

I got the same problem , but solved using 777 .... but i think 775 is the proper permision but dont work using that.

before trying out all the complex solutions, try these inside your laravel application: chmod -R o+w storage/

Hi guys !!

I haven't been through all the comments. But doing following helped me to resolve the similar issue.

I used Log::debug statements in my API handler. But Lumen didn't have permission to write logs in log file. I just gave the appropriate permissions and server started responding with desired result.

hope this might help somebody

Like some of you, I ran into this problem last night. My problem was that I put a Log::debug() call inside of the HTTP kernel and I was getting a weird "Uncaught RuntimeException: A facade root has not been set." error. However, upon removing these statements the issue went away and everything was working again.

Got the same issue.. Everything is logged, I try to play with Service provider, no more exception, trace, error info..

I found this shitty line:

       if (! $app->environment('testing')) {
            ini_set('display_errors', 'Off');
        }

Why ? As developer, I want to see everything.

Is it somewhere else a setting problem ?