But my application can only push events on the old DSN and also on this https://newHash@my-old-hostname but as you can see, the hostname is not the good one…
@BYK thanks i checked this but i already did the changes. Maybe the changes has not been used by containers. Must i do docker-compose down && docker-composer up -d ? or anything else ?
If you are using a recent version of the on-premise repo (March 13th or more recent), simply restarting the containers as @sagar.s suggested should be enough. If not you need to run
docker-compose down && docker-compose build && docker-compose up -d
I tryed both restart but my version must be older than March 13th so i also tried the dow/build/up -d
I generate a new key for one project, and i run a test script, but it still only work with old hostname.
Is there a way to get logs or may i need to check my reverse proxy (if i can access Sentry app, then event should also access it ?)