I am trying to configure sentry on my local machine and trying to setup ssl, everthing works fine with http, so i am able to access the sentry dashboard using http://localhost:9000, but i would ideally want to either access it via https
I am trying to use nginx as a reverse proxy but i am getting the following error
ERROR: for nginx Cannot start service nginx: driver failed programming external connectivity on endpoint onpremise_nginx_1 (87eaa55cbb9d0da49847246ed193d5dfec153dbdcb8805b86d13dd084a502cc7): Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error (Failure EADDRINUSE)
ERROR: Encountered errors while bringing up the project.
Sorry but this is not enough for anyone to help you. What exactly is not working? Are you getting any errors? What exactly is the issue are you facing with?
PS: This also doesnβt seem to have anything w/ Sentry or on-premise so you may wanna look for help elsewhere, specifically a place with more experts regarding nginx and Docker. (Iβm happy to try here tho, just saying)
Hi BYK, mant thanks for the reply and my apologies for not explaining this correctly.
I am trying to have the sentry url secured by https and have tried the steps as mentioned here https://docs.sentry.io/server/nginx/, i have the exact same copy of nginx file as specified in the link here but just the host name is different in my case i have specified βmy-sentry.example.comβ as the host.
my docker-compose.yml looks like this, with service nginx referring to ngnix image i have built locally. As recommended i have set the SENTRY_USE_SSL env variable to true. I have tried to define the port mapping like β41230:80β under service ngnix but the application does not load. I am new to docker compose, can you please help me point in the right direction as to what changes i need to make to docker compose file to ensure sentry can be accessed by https
That sounds about right if the public URL of your service has changed (Iβm assuming http is no longer an option and you just accept https). That said I think you can change this value from https://your.sentry.domain/manage without the need to rebuild. If that doesnβt work, yeah, youβd need to change this value in your config.yml and rebuild your Sentry on-premise image.