New to GitLab, and I can’t believe nobody else is having this problem but I’m not finding it anywhere. I installed GitLab v13.6.3 on RHEL 8 using Jeff Geerling’s Ansible playbook (which in turn uses the Omnibus package). It works fine for a couple of days, then goes into permanent 502 mode. Resta…

New installation, GitLab-CE, dies after a couple days with 502 errors

iwalker December 16, 2020, 7:01pm 6

OK, so one more to check with selinux, make sure you have these packages installed (check the link): Upgrade to 13.5.1 failed

libsemanage-static libsemanage-devel policycoreutils

Topic		Replies	Views
Works after installation but gets 502 error after first restart How to Use GitLab	4	5502	February 12, 2021
Gitlab instance not working with error 502 Self-managed	2	494	December 28, 2020
Gitlab 502 all sockets connection refused Self-managed	19	20974	November 30, 2021
GitLab CE never wakes up after a a few days of inactivity How to Use GitLab	1	833	August 4, 2016
Upgrade from 12.10.14 to 13.0.0 fails - 502 General upgrade	3	647	February 13, 2021