Proxy support about sentry-telegram

[butorov]

@AlwxSin @vyuldashev @notarseniy now you can try to solve your problem with the api_origin option.

[vyuldashev]

Any ETA on this?

[AlwxSin]

@vyuldashev please, look at getsentry/sentry#6784

[vyuldashev]

@AlwxSin Well, its not finished

[notarseniy]

+1

[ybolotnikov]

Hi! We get to work telegram with next scenario:

1. Setup nginx with self-signed certs in local network:
   server {
   listen 443 ssl;

    ssl_certificate     /etc/ssl/certs/fakeapi.crt;
    ssl_certificate_key /etc/ssl/certs/fakeapi.key;
   
    server_name api.telegram.ru;
   
    location / {
            proxy_pass http://ourhetznerserver.ip:443;
    }
   

}
2. Nginx on hetzner VM:
server {
listen 443;

    server_name api.telegram.org;

    location / {
            proxy_pass https://api.telegram.org;
    }

}

I think there is one nginx in hetzner enough, but with this we get an error with our another alert services:
curl: (35) Unknown SSL protocol error in connection
(updating rootCA.pem didn't help)

3. Add line to Dockerfile:
   RUN apt-get update && apt-get install -y python-pip && pip install sentry-telegram && sed -i 's/verify_ssl=True/verify_ssl=False/g' /usr/local/lib/python2.7/site-packages/sentry/http.py

4. Add record witn local nginx to hosts in docker-compose.yml:
   extra_hosts:

   • "api.telegram.org:192.168.110.35"

5. Rebuild sentry:
   docker-compose build && docker-compose run --rm web upgrade && docker-compose up -d

Profit!