I use hosted Sentry in production. I’m currently working on dockerizing development environments, including running Sentry’s official docker images
getsentry/onpremise, to get as close as possible to production.
On one side I have the composed
getsentry/onpremise with all defaults.
The web interface works great and submitting events to it through
sentry-cli from my host with the DSN works as expected.
On the other side I have a composed stack including PHP 5.6.x and Node 6.x LTS. As these are old versions, they need to use
sentry/sentry^1 (for php; rather than the current 2.x) and
These submit events properly to the hosted Sentry instance.
They are connected with the Sentry network using
docker network connect onpremise_default exampleapp.
But when reporting to the local Docker DSN, it 400s, so never gets saved in Sentry. All that shows up in the container’s logs is:
- For the PHP client:
"POST /api/2/store/ HTTP/1.1" 400 233 "-" "sentry-php/1.10.0"
- For the Node client:
"POST /api/2/store/ HTTP/1.1" 400 233 "-" "-"
As comparison, the from
sentry-cli send-event to the same DSN, the logs show:
"POST /api/2/store/ HTTP/1.1" 200 366 "-" "-".
I thought this could be some config/version thing because they are the old (deprecated) clients, even though those old clients work fine on the hosted DSN…
Would anyone have pointers as to what could be the issue?
Thanks for your help!