I’ve inherited a Gitlab set-up which has been running fine for sometime. After a brief power outage stopping all of our servers, they have been started up (with an annoying amount of manually starting stuff), but Gitlab is the only one remaining not fully functional.
The error is as above, this is from trying to do a
git clone ... with
fatal: unable to access ‘https://…/tbps/’: Failed to connect to … port 443: Connection refused
Similarly, trying to access the web interface gives a message including - 10.10.0.7 refused to connect.
I had to manually start the docker container as it wasn’t set to start automatically, but I’m not sure if there are any processes in the server which are involved in the whole process (the docker container exposes 80 and 443) so wasn’t sure where I should be looking.
Sorry for the lack of knowledge, if there is anything that I should be doing/information that would help then please let me know.
After checking the docker container, although it’s configure to expose port 443, running
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:9090 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:9187 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:9100 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 44841/nginx
tcp 0 0 127.0.0.1:9168 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 44936/sshd
tcp 0 0 0.0.0.0:8060 0.0.0.0:* LISTEN 44841/nginx
tcp 0 0 127.0.0.1:9121 0.0.0.0:* LISTEN -
tcp6 0 0 :::22 :::* LISTEN 44936/sshd
which looks like it’s not listening on port 443. Not sure if this is correct (as in something is missing) or ssl was being terminated in the host machine and there currently isn’t anything being run on there.
After trying to get nginx configured to run the web site (our normal proxy configuration), found that it was using Apache instead. Starting the Apache service resolved the problem.