Setup Sentry on premise on a server with http proxy

Hi there! I’m trying to setup Sentry on premises. The server is behind an HTTP proxy, so when the install.sh script is building the image I’m having the following errors:

Err:1 http://deb.debian.org/debian buster InRelease
  Could not connect to prod.debian.map.fastly.net:80 (151.101.216.204), connection timed out Could not connect to deb.debian.org:80 (151.101.218.133), connection timed out
Err:2 http://deb.debian.org/debian buster-updates InRelease
  Unable to connect to deb.debian.org:http:
Err:1 http://deb.debian.org/debian buster InRelease
  Could not connect to prod.debian.map.fastly.net:80 (151.101.216.204), connection timed out Could not connect to deb.debian.org:80 (151.101.218.133), connection timed out
Err:2 http://deb.debian.org/debian buster-updates InRelease
  Unable to connect to deb.debian.org:http:
Err:3 http://security.debian.org/debian-security buster/updates InRelease
  Could not connect to prod.debian.map.fastly.net:80 (151.101.216.204), connection timed out Could not connect to security.debian.org:80 (151.101.64.204), connection timed out Could not connect to security.debian.org:80 (151.101.0.204), connection timed out Could not connect to security.debian.org:80 (151.101.128.204), connection timed out Could not connect to security.debian.org:80 (151.101.192.204), connection timed out
Reading package lists...
W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease  Could not connect to prod.debian.map.fastly.net:80 (151.101.216.204), connection timed out Could not connect to deb.debian.org:80 (151.101.218.133), connection timed out
W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease  Could not connect to prod.debian.map.fastly.net:80 (151.101.216.204), connection timed out Could not connect to security.debian.org:80 (151.101.64.204), connection timed out Could not connect to security.debian.org:80 (151.101.0.204), connection timed out Could not connect to security.debian.org:80 (151.101.128.204), connection timed out Could not connect to security.debian.org:80 (151.101.192.204), connection timed out
W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease  Unable to connect to deb.debian.org:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.
Err:3 http://security.debian.org/debian-security buster/updates InRelease
  Could not connect to prod.debian.map.fastly.net:80 (151.101.216.204), connection timed out Could not connect to security.debian.org:80 (151.101.192.204), connection timed out Could not connect to security.debian.org:80 (151.101.64.204), connection timed out Could not connect to security.debian.org:80 (151.101.0.204), connection timed out Could not connect to security.debian.org:80 (151.101.128.204), connection timed out
Reading package lists...Reading package lists...

Building dependency tree...
Reading state information...W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease  Could not connect to prod.debian.map.fastly.net:80 (151.101.216.204), connection timed out Could not connect to deb.debian.org:80 (151.101.218.133), connection timed out
W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease  Could not connect to prod.debian.map.fastly.net:80 (151.101.216.204), connection timed out Could not connect to security.debian.org:80 (151.101.192.204), connection timed out Could not connect to security.debian.org:80 (151.101.64.204), connection timed out Could not connect to security.debian.org:80 (151.101.0.204), connection timed out Could not connect to security.debian.org:80 (151.101.128.204), connection timed out
W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease  Unable to connect to deb.debian.org:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.

E: Unable to locate package cron
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package cron
Removing intermediate container 1b3a03ea2233
Removing intermediate container 22d5cd15a5c7
Err:1 http://deb.debian.org/debian stretch InRelease
  Could not connect to deb.debian.org:80 (151.101.218.133), connection timed out
Err:2 http://deb.debian.org/debian stretch-updates InRelease
  Unable to connect to deb.debian.org:http:
Err:3 http://security.debian.org/debian-security stretch/updates InRelease
  Could not connect to security.debian.org:80 (151.101.192.204), connection timed out [IP: 151.101.192.204 80]
Reading package lists...
W: Failed to fetch http://deb.debian.org/debian/dists/stretch/InRelease  Could not connect to deb.debian.org:80 (151.101.218.133), connection timed out
W: Failed to fetch http://security.debian.org/debian-security/dists/stretch/updates/InRelease  Could not connect to security.debian.org:80 (151.101.192.204), connection timed out [IP: 151.101.192.204 80]
W: Failed to fetch http://deb.debian.org/debian/dists/stretch-updates/InRelease  Unable to connect to deb.debian.org:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package cron

Docker daemon is already using the proxy server because I can pull images without problems, however the problem is in the dockerfile. It is not passing the build-args http_proxy and https_proxy. Is there a way to say Sentry to use the env vars http_proxy and https_proxy or passing the proxy server in some config file?

Thanks!

Hi!

I think this should help you: https://stackoverflow.com/a/34992794/90297

You may want to create a docker-compose.override.yml to put these in.

Thanks for the response! But I will also need to set the proxy server in the Dockerfile files right? Like something like this:

ARG http_proxy
ARG https_proxy 

In sentry/Dockerfile and cron/Dockerfile .

Correction, this should be the answer, so no need to change the repo files: https://medium.com/@airman604/getting-docker-to-work-with-a-proxy-server-fadec841194e#002b

Nice, thanks!

1 Like