Why it is not showing debugbar?

[shankhadevpadam]

Why it is not showing debugbar?

Route::get('/debug', function () {
    dump(App\Models\User::find(1));
});

PHP: 8.4
Laravel Version: 12.18.0
Debuger Bar: 3.15.4

But Laravel old folder structure.

[parallels999]

Route::get('/debug', function () {
    dump(App\Models\User::find(1));
});

[barryvdh]

@shankhadevpadam anything in the laravel log or browser console?

[f-liva]

Same for me, doesn't show the bar

[Vladimir1247]

And for me. And it's very mysterious: everything is fine locally, but not on the remote server. There's nothing even in the page code. APP_DEBUG=true, laravel log and browser console are clean. What could be the reason?

[ubedthaheem]

After re-installing with fruitcake namespace, debugbar is not showing in Laravel 11.44.1 I am using "fruitcake/laravel-debugbar": "^3.16",
Before it was with baryvhd namespace & working fine.

[barryvdh]

hmm strange. No errors? Did package discover run correctl?

[ubedthaheem]

Yes. everything works fine; I upgraded Laravel from an old version to newer version & found that issue.

Now I ran checkout --vendor and composer to rollback everything. Without debugbar is very hard to remember pages & files :D

[barryvdh]

Hmm not sure why that is. Just installed a fresh laravel 12 and installed the fruitcake version, it detected it correctly.

[erikn69]

This has happened to me when there's an error, for example, with an old config file.
When the error happens, everything works normally except the debugbar, it isn't showing
It was hard to find the problem; try with a fresh config file, or by checking the laravel log or browser console

[shez1983]

i m having the same issue, locally debugbar is working - on my staging server, i can see in vendor debugbar folder is there, debug = true but no debugbar,, (i do have a basic auth so people cant access my staging site). but even before i added this i didnt see debugbar.

[justinkluever]

If running inside sail or other containers, debugbar may use the internal hostname unless DEBUGBAR_ROUTE_DOMAIN (route_domain in config) is set, this could be the cause as it will try to access the javascript files from there.

I have noticed this because i use sail and debugbar was not visible for me either until i have forced it to be a accessible value as we don't use laravel.test

[danieladarve]

Im running containers, also opcache, fixed by:
setting .env:

DEBUGBAR_ROUTE_DOMAIN

blacklisting "vendor/barryvdh/laravel-debugbar/*" in php.ini config opcache.blacklist_filename=

[whitespacecode]

If running inside sail or other containers, debugbar may use the internal hostname unless DEBUGBAR_ROUTE_DOMAIN (route_domain in config) is set, this could be the cause as it will try to access the javascript files from there.

I have noticed this because i use sail and debugbar was not visible for me either until i have forced it to be a accessible value as we don't use laravel.test

I'm also having issues when i update to the new version (we use sail):

GET https://exampleproject.localhost/_debugbar/assets?type=css&mtime=1780559641 net::ERR_ABORTED 404 (Not Found)
(index):898  
GET https://exampleproject.localhost/_debugbar/assets?type=js&mtime=1780559641 net::ERR_ABORTED 404 (Not Found)
client:851 [vite] connecting...
client:955 [vite] connected.
(index):902 Uncaught ReferenceError: PhpDebugBar is not defined
    at HTMLDocument.renderDebugbar ((index):902:21)