Troubleshooting
Find the right troubleshooting guide
Start with what failed. A missing toolbar, a disconnected agent, and an empty inspector need different checks.
-
No working bar
Check whether Laravel captured the response and whether the browser loaded the interface. -
No agent connection
Check the local command, PHP runtime, and the five advertised tools. -
Missing evidence
Check the selected profile, retained data, and response limits.
What stopped working?
| Symptom | Start here |
|---|---|
| The bar is missing, blank, or will not open | The bar is missing or will not open |
| The agent cannot start the server or find its tools | Fix an MCP connection |
| The right request, inspector, or value is missing | Find missing profiles and data |
| A queued job still looks pending | Follow the job into its worker profile |
| An EXPLAIN plan is unavailable | Check the query and its retained bindings |
| A form stays on the same screen | Inspect the validation attempt |
Keep one useful piece of evidence
Repeat one action and note its method, path, time, and the X-NewDebugBar-Profile response header when present. Keep the exact browser or MCP error. That separates a new failure from an old profile or a background request.
For installation problems, record the package versions and the PHP version used by the command that failed:
php -v
composer show newdebugbar/newdebugbar
composer show livewire/livewire
php artisan env
If the focused checks do not resolve it
- Describe the smallest action that reproduces the problem and what you expected to happen.
- Include PHP, Laravel, Livewire, and The New Debug Bar versions, plus the relevant local runtime: host PHP, container, or worker.
- Include the exact error and a small relevant excerpt. An expired profile ID by itself is not a portable bug report.
- Say which guide checks you tried and what each returned.
Open an issue in the package issue tracker.