SSL certificates issues on some GitLab hosted pages with custom domains

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Since 20240312T1727Z I get PagerDuty alerts from HetrixTools for some GitLab pages with custom domains.

https://status.gitlab.com/ and https://twitter.com/gitlabstatus indicate there are no problems, but my local browsers, SSLabs and certcheckerapp indicate the autogenerated Let's Encrypt TLS certificate for one of the domains has expired for quite a while.

SSLabs is quite overloaded right now, so some of their links below can return a HTTP 503 response or time-out. That's why I included certcheckerapp links below as well: they they seem not overloaded.

These are the affected domains with corresponding GitLab pages projects and various checks.

martijn.pluimers.com domain

ans.pluimers.com domain

Remarks

  • I know that most of the DNS servers for pluimers.com are down right now: a move that didn't work well. Working on that too, but given some health issues I can only do so much per day.
  • The odd thing is that PagerDuty only started warning about the martijn.pluimers.com TLS certificate issue today while it has been expired 23 days ago on 2024-02-18.
  • On hetrixtools, I have put ans.pluimers.com checking into "maintenance mode" to ensure I could sleep through the night (preventing 20+ PagerDuty phone calls)

My main questions

  1. could the expired certificate on martijn.pluimers.com be a GitLab thing, or is this a DNS thing? (and if it is a DNS thing: what more than the above checks can I do?)
  2. how can I get details on why a Let's Encrypt TLS certificate renewal fails?
  3. are the intermittent time-out errors on ans.pluimers.com (see the hetrixtools link there) related to the certificate problem of martijn.pluimers.com?

Thanks in advance for getting back at this.

--jeroen

Edited by 🤖 GitLab Bot 🤖