Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

TGM's avatar
Level 1

How to read laravel debuging output

Hello,

How does one actually read the debugging information?

I intentionally added a typo in the .env config file, and below is the error message laravel returned. It does not show any trace related to the .env file.

" 1/1 RuntimeException in Encrypter.php line 43: The only supported ciphers are AES-128-CBC and AES-256-CBC with the correct key lengths.

in Encrypter.php line 43
at Encrypter->__construct('XR�gݽq������$h�O�L]m/h�@��V', 'AES-256-CBC') in EncryptionServiceProvider.php line 27
at EncryptionServiceProvider->Illuminate\Encryption\{closure}(object(Application), array()) in Container.php line 731
at Container->build(object(Closure), array()) in Container.php line 629
at Container->make('encrypter', array()) in Application.php line 709
at Application->make('encrypter') in Container.php line 849
at Container->resolveClass(object(ReflectionParameter)) in Container.php line 804
at Container->getDependencies(array(object(ReflectionParameter)), array()) in Container.php line 773
at Container->build('App\Http\Middleware\EncryptCookies', array()) in Container.php line 629
at Container->make('App\Http\Middleware\EncryptCookies', array()) in Application.php line 709
at Application->make('App\Http\Middleware\EncryptCookies') in Pipeline.php line 127
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 104
at Pipeline->then(object(Closure)) in Router.php line 644
at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 618
at Router->dispatchToRoute(object(Request)) in Router.php line 596
at Router->dispatch(object(Request)) in Kernel.php line 267
at Kernel->Illuminate\Foundation\Http\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Debugbar.php line 49
at Debugbar->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in CheckForMaintenanceMode.php line 46
at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Pipeline.php line 104
at Pipeline->then(object(Closure)) in Kernel.php line 149
at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 116
at Kernel->handle(object(Request)) in index.php line 53"

This is just an example, in which you can easily identify the problem, but when other errors appear that rely on the backtrace , how do you read the output?

0 likes
8 replies
TGM's avatar
Level 1

laravel-debugbar it's great. But it dosen't add anything new to the allready ongooing traces, it's just an interface that handles the given output.

ohffs's avatar

Sometimes the debug output is really useful, sometimes it's more of 'oh, it's that error again - that must mean...'. I'm not entirely sure what could be done to improve it without a whole lot of fragile heuristics though...

TGM's avatar
Level 1

Here is another helpfull debuging package http://devmarketer.io/learn/prettier-helpful-error-pages-laravel-5-2-5-3/

I've been going thru the files one by one, and nothing except that error message to indicate what the problem is. Is pretty disappointing to rely on the web for finding out where the problem is. In any given application at any given time you should be able to identify the problem by the source code alone.

Why do I got the feeling that everybody around here is flying blindfolded taking the result "as it is".

bugsysha's avatar

Why do I got the feeling that everybody around here is flying blindfolded taking the result "as it is".

Google is creating Idiocracy (search IMDB).

ohffs's avatar

For me anyway, I think I've just been beaten into submission over time ;-) Anything that gives me a clue is like manna ;-) I still spend a huge amount of time with applications that, at best, give you 'Error! Crash!' ;-) Not so long ago I wasted "quite some time" with an application which was mysteriously just bombing out (no error - just died). Eventually figured out that even though the application was 64bit, if the users ID number was >32bit the program just crashed. Fun fun fun...

You could aways install xdebug I guess. Or dive into the exception handler code and see if you can figure out a better way of doing it.

1 like
phpMick's avatar

+1 for XDebug, couldn't live without it.

Please or to participate in this conversation.