Gitlab Pages problem after v13->v14 upgrade


We’ve just upgraded GitLab v13 to v14 and have encountered some problems with our gitlab-pages config. Pages was working fine with v13, but with v14 we are now getting 502 errors when attempting to access the hosted pages.

The error seems to be ca-cert/authority related. The last entry in /var/log/gitlab/gitlab-pages/current is

{“error”:“failed to connect to internal Pages API: Get “https://gitlab-vm.intranet/api/v4/internal/pages/status”: x509: certificate signed by unknown authority”,“level”:“warning”,“msg”:“attempted to connect to the API”,“time”:“2021-07-08T10:35:35Z”}

Here, gitlab-vm is the server name of the VM hosting gitlab and gitlab-pages, but our pages are accessed at https://project.gitlab-pages.intranet. I wouldn’t expect the name of the machine to appear in the api url (in the log entry above), but nevertheless the ‘unknown authority’ rather than a ‘cert not found’ type message would tend to suggest that paths are resolving correctly and that it’s an issue with the ca itself (which was previously working fine).

Has anything changed with regard to how CAs / certs are handled in GitLab v14? Any pointers to where to start looking to fix this would be much appreciated.

NB. I can confirm we did follow the upgrade path to 13.12.x before upgrading to v14.

Also, having this issue after upgrading from 13 to 14. Followed all migration steps as well, but hitting exact same error.

I’m having the same issue as well after upgrading from 13 to 14. 13 to 14 has been the only “config” change made.