Open lemrouch opened 5 months ago
I wonder if this is https://github.com/getsentry/self-hosted/issues/2305 making a re-appearance...
same error here at 24.4.2
same issue with 24.5.1
my best guess would be that the sentry sdk inside the worker container/process does not honor the system certificate installed while starting the container. maybe the corresponding option in the sentry sdk needs to be set. (https://docs.sentry.io/platforms/python/configuration/options/#ca-certs)
Container sentry-self-hosted-sentry-cleanup-1
has the same problem.
Workaround:
docker exec -it sentry-self-hosted-sentry-cleanup-1 bash
cat >> /.venv/lib/python3.11/site-packages/certifi/cacert.pem <<EOF
-----BEGIN CERTIFICATE-----
MII...
-----END CERTIFICATE-----
EOF
Do it in both containers. I don't think Certifi is willing to accept some environment variable to override it's built-in default.
Self-Hosted Version
24.2.0
CPU Architecture
x86_64
Docker Version
26.0.0
Docker Compose Version
2.20.3
Steps to Reproduce
Add our own CA to the certificates directory. Set system.url-prefix to https://sentry.ourdomain.com. Run self-hosted Sentry with certificate signed with our own CA.
I was able to work around the problem by appending our CA to the certifi module storage in the worker container. But I guess the worker container should use the system.internal-url-prefix instead.
Expected Result
No errors reported.
Actual Result
Logs from sentry-self-hosted-worker-1 contain:
Event ID
No response