-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inspector not working in Laravel app #99
Comments
Hi @binaryfire, If you are using it inside a Docker container, it might be something like:
Where Alternatively, the issue could be incorrect port mapping. If you map a port inside the container to your host server, like |
Hi @butschster Yeah actually I'm using the container name (
Also http-dumps to But Inspector doesn't with either of these:
or
|
Hmmm. I you the same settings in examples, services:
examples:
build: "./docker/examples"
environment:
APP_ENV: production
APP_KEY: xxx
LOG_LEVEL: debug
BROADCAST_DRIVER: log
CACHE_DRIVER: array
QUEUE_CONNECTION: sync
DB_CONNECTION: sqlite
DB_DATABASE: ":memory:"
MAIL_HOST: buggregator
MAIL_PORT: 1025
MAIL_ENCRYPTION: null
MAIL_FROM_ADDRESS: sender@site.com
MAIL_FROM_NAME: sender
RAY_HOST: ray@buggregator
RAY_PORT: 8000
VAR_DUMPER_SERVER: buggregator:9912
SENTRY_LARAVEL_DSN: http://sentry@buggregator:8000/123
LOG_SOCKET_URL: buggregator:9913
LOG_SLACK_WEBHOOK_URL: http://buggregator:8000/slack
INSPECTOR_URL: http://inspector@buggregator:8000
INSPECTOR_API_KEY: test
PROFILER_ENDPOINT: http://profiler@buggregator:8000
ports:
- 9020:8000
buggregator:
image: ghcr.io/buggregator/server:latest |
Weird. Sentry isn't working for me either:
Sending to sentry.io works, and I've had it working with Buggregator in other PHP apps with the same Docker setup. So I'm not sure what's going on with that one either. Could it be a problem with their new SDK? They released v4.0.0 last week which has some major changes: https://github.com/getsentry/sentry-laravel/releases |
In my opinion, no! There is the same problem with Sentry on Could you try to clear the config cache? I noticed that there are some main changes in the Laravel framework like this change in https://github.com/laravel/framework/blob/10.x/src/Illuminate/Foundation/Providers/FoundationServiceProvider.php#L96 which disable setting $app = new Illuminate\Foundation\Application(
$_ENV['APP_BASE_PATH'] ?? dirname(__DIR__)
);
// var dumper setting
$_SERVER['VAR_DUMPER_FORMAT'] = 'server';
$_SERVER['VAR_DUMPER_SERVER'] = 'if-buggregator:9912'; |
Hi @butschster. Thanks for the update! Sentry is working in Laravel now 🎉 But Inspector still isn't for some reason. This is my config:
Connecting to inspector.dev works and requests show up in the dashboard so the |
Hi @binaryfire. I'll try to cover your case with tests, and I'm confident everything will work fine. I'm currently working on the tests and addressing any incompatibilities |
Hi guys
It seems Inspector isn't working in Laravel. Sending to inspector.dev works correctly but not sending to Buggregator. I'm using the latest v1.0.0 Docker image.
The docs say this should be the config:
But this line in the Inspector
EventHandler
suggests the uri should end withinspector
?I tried the above config and the following two configs with no luck:
Any ideas?
Thanks again!
The text was updated successfully, but these errors were encountered: