Gitlab only show “Deploy in progress” page

I installed Gitlab (gitlab-ee 13.1.2-ee.0) on Ubuntu 20.04 following this instructions:

I did not have any errors but I see only the “Deploy in progress” page when i open my gitlab site.

“gitlab-ctl status” outputs the following:

run: alertmanager: (pid 130184) 29s; run: log: (pid 2823) 16536s
run: gitaly: (pid 130200) 28s; run: log: (pid 2824) 16536s
run: gitlab-exporter: (pid 130224) 28s; run: log: (pid 2844) 16536s
run: gitlab-workhorse: (pid 130227) 27s; run: log: (pid 2829) 16536s
run: grafana: (pid 130239) 27s; run: log: (pid 2833) 16536s
run: logrotate: (pid 130269) 26s; run: log: (pid 2837) 16536s
run: node-exporter: (pid 130279) 26s; run: log: (pid 2854) 16536s
run: postgres-exporter: (pid 130288) 26s; run: log: (pid 2836) 16536s
run: postgresql: (pid 130296) 25s; run: log: (pid 2851) 16536s
run: prometheus: (pid 130324) 25s; run: log: (pid 2827) 16536s
run: puma: (pid 130418) 24s; run: log: (pid 2834) 16536s
run: redis: (pid 130424) 24s; run: log: (pid 2826) 16536s
run: redis-exporter: (pid 130429) 23s; run: log: (pid 2843) 16536s
run: sidekiq: (pid 130435) 23s; run: log: (pid 2842) 16536s

Hi Fabian!

It seems that the example config from that blog posts redirects 503 errors to that /deploy.html page. Please try following our own docu to configure Apache and use one of our own web-server recipes.

If it still doesn’t after applying that docu, please check the logs for more details of the 503 error.

Some context about that “deploy page” can be found here, but I’m guessing our down command will not work in your case.

Just for completeness & posterity’s sake: our official installation guide is here.

Continuing the discussion from Gitlab only show “Deploy in progress” page:

Hi and thank you for your reply!

I followed the intructions and getting a 502 now ( Whoops, GitLab is taking too much time to respond.).
In the workhorse error log i can see the following:

badgateway: failed to receive response: dial unix /var/opt/gitlab/gitlab-rails/sockets/gitlab.socket: connect:      connection refused

my gitlab.rb:

external_url ''
gitlab_rails['trusted_proxies'] = ['', 'fe80::20c:29ff:fea6:2049/64', '']
registry_external_url ''
gitlab_workhorse['listen_network'] = "tcp"
gitlab_workhorse['listen_addr'] = ""
web_server['external_users'] = ['www-data', 'git']
nginx['enable'] = false
mattermost_external_url ''

Thank you for your help.

Is that workhorse error the only one? Oftentimes, that error is only a symptom of another problem.

Please check gitlab-ctl status again. Is any part of it down / not running?

yes everything seems to run:

sudo gitlab-ctl status
run: alertmanager: (pid 2976) 982316s; run: log: (pid 2960) 982316s
run: gitaly: (pid 2981) 982316s; run: log: (pid 2966) 982316s
run: gitlab-exporter: (pid 2988) 982316s; run: log: (pid 2971) 982316s
run: gitlab-workhorse: (pid 2982) 982316s; run: log: (pid 2969) 982316s
run: grafana: (pid 2984) 982316s; run: log: (pid 2967) 982316s
run: logrotate: (pid 2292334) 3105s; run: log: (pid 2958) 982316s
run: mattermost: (pid 2983) 982316s; run: log: (pid 2968) 982316s
run: node-exporter: (pid 2978) 982316s; run: log: (pid 2963) 982316s
run: postgres-exporter: (pid 2986) 982316s; run: log: (pid 2970) 982316s
run: postgresql: (pid 2980) 982316s; run: log: (pid 2965) 982316s
run: prometheus: (pid 2973) 982316s; run: log: (pid 2957) 982316s
run: puma: (pid 2300298) 2s; run: log: (pid 2964) 982316s
run: redis: (pid 2974) 982316s; run: log: (pid 2959) 982316s
run: redis-exporter: (pid 2975) 982316s; run: log: (pid 2961) 982316s
run: registry: (pid 2979) 982316s; run: log: (pid 2962) 982316s
run: sidekiq: (pid 2985) 982316s; run: log: (pid 2956) 982316s

Is this forum still active and supported?

Yes, on a best-effort basis. Your setup seems more complicated than the test environments I’ve used so far. Thus I’m unfortunately not sure where to start debugging this.

As we also have released 13.2 in the mean-time, I suggest you install that according to our official docu and add configure your config items one-by-one, with git reconfigure in between and a quick manual test like logging into the web interface and creating a small test project with just a

1 Like