Cannot connect to gitlab registry from oracle vm

Infrastructure as Code & Cloud Native
1

i cannot login to gitlab registry at all from my oracle virtual machine. it seems that gitlab is actively refusing connections from my vm.

Error response from daemon: Get "https://registry.gitlab.com/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

i also cant pull any images hosted in my gitlab container registry. meanwhile logging in and pulling from docker hub works 100%. any reason for blocking this specific provider? thanks.

2

Where is the VM hosted - your local desktop computer, or somewhere in the cloud/data center? Might be interesting to see which network route is taken, maybe a provider on the way is intercepting or blocking the request. I have seen some organizations use specific packet filters that proxy/optimize traffic which can be a source of errors, too.

traceroute registry.gitlab.com

Please share the command line that leads to this error message, too.

3

basically if i am trying to pull docker images from my repository i get (often) timeout errors. currently i can login but i still facing errors on pulling images such as:
docker pull registry.gitlab.com/ivanjx/home-server/server:latest

traceroute result:

traceroute to registry.gitlab.com (35.227.35.254), 30 hops max, 60 byte packets
 1  192.168.20.11 (192.168.20.11)  0.361 ms  0.401 ms  0.385 ms
 2  10.10.10.1 (10.10.10.1)  18.910 ms  18.917 ms  19.464 ms
 3  172.20.0.1 (172.20.0.1)  20.385 ms  20.592 ms  20.597 ms
 4  140.91.232.6 (140.91.232.6)  20.852 ms 140.91.232.14 (140.91.232.14)  20.859 ms 140.91.232.15 (140.91.232.15)  20.845 ms
 5  31898.sgw.equinix.com (27.111.229.44)  21.602 ms  21.796 ms  21.731 ms
 6  * * *
 7  254.35.227.35.bc.googleusercontent.com (35.227.35.254)  247.830 ms  246.793 ms  248.256 ms

my network:
server (at home) → my home isp → oracle server (as vpn) → global internet

i also tried pulling the docker image on the oracle server directly with same results.

another timeout error message:

Error response from daemon: Get "https://registry.gitlab.com/v2/ivanjx/home-server/server/manifests/sha256:d1d6b7cf81be74f16a9b239a8cbad285d766a851a02fe47d958972e19b524056": dial tcp 35.227.35.254:443: i/o timeout
4

Could you sort it out?

I’m facing the same problem, which I could analyse a bit further. I checked form two machines in the same data center, and only one has problems:

  • The problematic machine used to work perfectly, and suddenly it stopped.
  • curl https://registry.gitlab.com/v2/ blocks, and tcpdump shows the remote machine is not answering.
  • curl https://gitlab.com/ works with no issues.
  • ping registry.gitlab.com works perfectly, and I see the ICMP responses coming through.
  • There are no firewalls differences or any other network configuration differences between the two.
  • The problematic machine does have a newer kernel, but is minimal (6.8.0-40 vs 6.8.0-39)

I presume registry.gitlab.com is somehow blocking my ip, but there’s no way I can check that, I guess. Perhaps this get sorted out with time…

5

Hi everyone!
I had the same problem, everything worked fine until a certain point. A few days ago registry.gitlab.com stopped responding. Timeout error. ICMP works.
I also use the free version, and I have no way to write to technical support.

I checked on the cloudfire website, the region is determined correctly .

My IP address is 62.72.47.172.

~$ curl --connect-timeout 5  https://registry.gitlab.com
curl: (28) Connection timed out after 5001 milliseconds

~$ ping   registry.gitlab.com
PING registry.gitlab.com (35.227.35.254) 56(84) bytes of data.
64 bytes from 254.35.227.35.bc.googleusercontent.com (35.227.35.254): icmp_seq=1 ttl=57 time=230 ms
64 bytes from 254.35.227.35.bc.googleusercontent.com (35.227.35.254): icmp_seq=2 ttl=57 time=239 ms
64 bytes from 254.35.227.35.bc.googleusercontent.com (35.227.35.254): icmp_seq=3 ttl=57 time=236 ms
64 bytes from 254.35.227.35.bc.googleusercontent.com (35.227.35.254): icmp_seq=4 ttl=57 time=245 ms
64 bytes from 254.35.227.35.bc.googleusercontent.com (35.227.35.254): icmp_seq=5 ttl=57 time=226 ms
^C
--- registry.gitlab.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 226.113/235.220/244.939/6.598 ms

~$ curl --connect-timeout 5  https://254.35.227.35.bc.googleusercontent.com
curl: (28) Connection timed out after 5001 milliseconds

Who solved this problem and how?

6

I believe your curl command should have been:

curl --connect-timeout 5 https://registry.gitlab.com

do not expect to be able to connect directly to the googleusercontent address. The connection to those entries has to go via the correct url - registry.gitlab.com

7

see what network route