I try to install gitlab. The setup script adds
deb https://packages.gitlab.com/gitlab/gitlab-ee/debian/ stretch main
deb-src https://packages.gitlab.com/gitlab/gitlab-ee/debian/ stretch main
as sources for additional Debian packages.
When I run apt-get update I get
W: Failed to fetch https://packages.gitlab.com/gitlab/gitlab-ee/debian/dists/stretch/InRelease FailReason: ConnectionRefused
obviously gitlab can’t be installed after that.
Hi, and welcome to the forum! 
Quick question: when you run apt update, is the gitlab archive the only one apt fails to connect to?
In other words, what’s the full output of apt update?
I’ve just tried this on my VPS running Ubuntu, and at least the gitlab archive for Ubuntu could be reached out to. That does not mean there might be something specific going on with the one for Debia.
It’s a fresh VM and the gitlab apt repro is the only one that fails.
root@gitlab:~# apt-get update
Err:1 https://packages.gitlab.com/gitlab/gitlab-ee/debian stretch InRelease
FailReason: ConnectionRefused
Hit:2 http://security.debian.org/debian-security stretch/updates InRelease
Ign:3 http://ftp.debian.org/debian stretch InRelease
Hit:4 http://ftp.debian.org/debian stretch-updates InRelease
Hit:5 http://ftp.debian.org/debian stretch Release
Reading package lists… Done
W: Failed to fetch https://packages.gitlab.com/gitlab/gitlab-ee/debian/dists/stretch/InRelease FailReason: ConnectionRefused
W: Some index files failed to download. They have been ignored, or old ones used instead.
This is hidden when running the script because the output from apt update is redirected to /dev/null
