Amar Takhar created an issue: https://gitlab.rtems.org/administration/gitlab/-/issues/123
GitLab pages is broken it's not serving any pages and giving a `502`. I'm opening this issue up after the fact since it was expressing itself in different ways and ended up being something simple. I spent a lot of time debugging this and now after the fact I can see there _was_ one error that would have tipped me off at the start. Writing this down here to document the time spent as well as help anyone else out there who runs into the same issue. The error in pages was: * `could not fetch domain information from a source` I read around about this error and it gave a lot of conflicting, old information. We use UNIX sockets for most things so pointing pages to an internal URL was not possible. I did make the change to use TCP sockets and that did not fix the problem. I finally decided to run `gitlab-pages` from the commandline and noticed in the shell output requests to: * `/api/v4/internal/pages?host=rtems-source-builder-0fd01f.rtems.io` That were failing with 500 errors. I looked in the log and discovered it was gitving bad password errors. The `gitlab-pages` secrets file that somehow got the wrong permissions on it. Both `gitlab-pages` and GitLab need to access this file so they can communicate. Unrelated to this there were two other issues going on that I won't bring up here as this topic is just about what it took to get pages fixed. -- View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/123 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
