Gitlab-CE Throwing 503 on CentOS 7

How to Use GitLab
1

I’ve managed to setup Gitlab-CE(11.4.5) on my VPS running CentOS 7(3.10.0).

I’ve made it to communicate over SSL(via Let’s Encrypt) and I’ve used Apache in the process rather than Nginx since I’ve already got Apache up and running. Here is the sample Apache config template I’ve used.

The problem is that when I go to my Gitlab domain, I’m presented with a 503 error message.

Upon further investigation from the error logs, I’ve determined the root cause of the problem:

[Wed Nov 14 14:30:02.265118 2018] [proxy_http:error] [pid 5070] [client 2.247.254.27:48855] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Wed Nov 14 14:33:31.666268 2018] [proxy:error] [pid 5034] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:8181 (*) failed

A similar question is asked here without an accepted answer. Although since it’s for a machine running Ubuntu, I’m guessing maybe it’s related to CentOS, specifically SELinux. Because another question here relates a similar problem to SELinux. But I’ve had no luck with the suggested solution unfortunately.

Any ideas?

2

Alright, I handled it.

It was about the port 8181. Actually, on the template Apache config I’ve used, it was mentioned on the top of it to set gitlab-workhorse to the port 8181 by the following statements: gitlab_workhorse['listen_network'] = "tcp" and gitlab_workhorse['listen_addr'] = "127.0.0.1:8181" .

1 Like