I’m having trouble setting up gitlab behind a external CaddyServer. I’ve used these instructions https://gitlab.com/gitlab-org/gitlab-recipes/tree/master/web-server/caddy and get a 502 bad gateway error.
The Caddy Server is in our DMZ, with firewall rules allowing ports 22, 80, 443 and 8181 through. The Gitlab server is listening on port 8181
user@gitlab:~$ netstat -ntlp | grep LISTEN
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
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 127.0.0.1:9168 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:8181 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:9121 0.0.0.0:* LISTEN -
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 -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::25 :::* LISTEN -
But, the Caddy server can’t see the ports available on the gitlab server
user@caddy:~# nmap 10.0.0.180
Starting Nmap 7.01 ( https://nmap.org ) at 2017-08-23 11:01 AEST
Nmap scan report for 10.0.0.180
Host is up (0.0010s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
I’ve also tested this from another server and pc which has full access through the firewall and get the same port issue. Is there something I’m missing in the gitlab settings?