Reminder to self GitLab pages on the gitlab.com are free, so Setting up a GitLab project so it is served over https as a gitlab.io and a custom subdomain comes with two caveats:
- Intermittent HTTP error 502 Bad Gateway
- [Archive] Jeroen Wiert Pluimers on Twitter: “Hi @gitlab, I configured pages for a gitlab.com public repository with a custom domain which mostly works fine, but every couple of days it will return a 502 error on loading. Refreshing it later then will reload correctly. What should I investigate further?” / Twitter
- Intermittent
NET::ERR_CERT_COMMON_NAME_INVALID(Chrome) orSSL_ERROR_BAD_CERT_DOMAIN(Firefox):- [Archive] Jeroen Wiert Pluimers on Twitter: “Hey @gitlab another issue I get on the same GitLab pages every now and then is an invalid certificate. This happens at least once a day. The actual serial presented then is
5b0c885bd0e0a1a52ad5c29dfor*.gitlab.io…” / Twitter- [Archive] Jeroen Wiert Pluimers on Twitter: “@gitlab When I refresh, I get the correct one with serial
04298abcf6ea3edafad05e8099878118571cfor … issued byCN = R3O = Let's EncryptC = USAs Let’s Encrypt certificates should only refresh every slightly less than 90 days, I wonder why this mismatch happens. …” / Twitter - [Wayback/Archive] On gitlab.com GitLab Pages projects with TLS and custom domain, certificate errors are intermittently returned (#6219) · Issues · GitLab.com / GitLab Infrastructure Team / production · GitLab
- [Archive] Jeroen Wiert Pluimers on Twitter: “@gitlab When I refresh, I get the correct one with serial
- [Archive] Jeroen Wiert Pluimers on Twitter: “Hey @gitlab another issue I get on the same GitLab pages every now and then is an invalid certificate. This happens at least once a day. The actual serial presented then is
–jeroen
