Two repos for example, same exact code both accessible from here: https://git.garman.io/home
Group Pages
https://git.garman.io/home/home.garman.io < this should be accessible at home.garman.io
Project Pages
https://git.garman.io/home/test-page < this is accessible at home.garman.io/test-page/
When I try to browse to the group page, I get a GitLab 404 page. When I try to browse to the project page. Everything works fine.
The pipelines run fine, I’ve tried restarting gitlab, Nginx, etc. I confirmed the files do exist.
root@04b008193d16:/var/opt/gitlab/gitlab-rails/shared/pages/home# ls
home.garman.io test-page
root@04b008193d16:/var/opt/gitlab/gitlab-rails/shared/pages/home# pwd
/var/opt/gitlab/gitlab-rails/shared/pages/home
root@04b008193d16:/var/opt/gitlab/gitlab-rails/shared/pages/home# ls home.garman.io/
config.json public
root@04b008193d16:/var/opt/gitlab/gitlab-rails/shared/pages/home# ls test-page/
config.json public
My current configuration is running the gitlab ce docker with a letsencrypt container reverse proxying to the gitlab container. Everything else seems to be working, the https termination, redirecting http to https, ssh, even pages works when a project page is attempted to be used.
What would my next step in debugging me, I couldn’t find any other cases of this happening outside of a lot of reports of gitlab.com user/group pages not being generated but there was a patch to gitlab ee that resolved it when waiting around for deployments wasn’t the solution.
Thanks in advance for any help!
edit: this is running off my home media server, I’m also currently having internet issues (thanks a lot att) so if you get a server error or can’t connect type error - blame att but it should be back up not too long after. Intermittent internet on for a few days then a few hours of downtime for the past month without any answers and everyone says “its out of my hands” 