GitLab runner throws "connect: permission denied" errors after registration

Hi,

I have installed GitLab runner on a Fedora Server 29 VM using the official repository. I followed this documentation article step-by-step. Everything went well, until after registering the runner.

The runner is listed in my GitLab admin interface, but the “Last contact” column remains on “Never”. The logs for the runner show the following error:

Mar 25 05:08:04 fedora-server-1 gitlab-runner[791]: WARNING: Checking for jobs… failed runner=removed status=couldn’t execute POST against https://git/api/v4/jobs/request: Post https://git/api/v4/jobs/request: Post https://git/api/v4/jobs/request: dial tcp 10.0.0.144:443: connect: permission denied

I have verified that the runner VM is able to contact the GitLab instance (which I’d assume is redundant given the fact that the runner is successfully registered):

[thomas@fedora-server-1 ~]$ ping git
PING git (10.0.0.144) 56(84) bytes of data.
64 bytes from git (10.0.0.144): icmp_seq=1 ttl=64 time=0.284 ms
64 bytes from git (10.0.0.144): icmp_seq=2 ttl=64 time=0.268 ms
64 bytes from git (10.0.0.144): icmp_seq=3 ttl=64 time=0.319 ms
^C
— git ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 15ms
rtt min/avg/max/mdev = 0.268/0.290/0.319/0.025 ms

[thomas@fedora-server-1 ~]$ nc -zv git 443
Ncat: Version 7.70 ( https://nmap.org/ncat )
Ncat: Connected to 10.0.0.144:443.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.

Where should I look next?

  • GitLab 11.9.0
  • GitLab runner 11.9.0

It turns out that I am experiencing this issue. Looks like it’s not going to get resolved anytime soon, yay…