- Sentry running on a standalone machine, behind a corp FW which allows only https
- nginx running on corp firewall, terminating https connections
BUT: I had to set the SENTRY_URL_PREFIX to "https", as redirects were coming back "http" and not getting through the corp fw.
The problem:
- the problem I think I am having is that the client key is now https.
- events that are getting sent to the sentry using that client key are just getting silently dropped by sentry.
My question:
is having the client key "https" going to cause an ssl negotiation? Is that the reason sentry is silently dropping these POSTs?
client key: https://83cd6477dad24a98b01a544fde8e3cbb:823b4ca7b1d1463abefa8d84281b1dd3@sentry:8080/2
My PC =====https=====corpFWrunningNginx-------http-------sentryBoxListeningOn8080
corpFWrunningNginx config
if ($host = sentry) {
access_log /var/log/nginx/sentry.access.log;
}
sentryBoxListeningOn8080
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')