@hansw @nommon

this wont happen again, I actually already do get alerts I just didnt realize I had to act on it.

Ya see all the custom domain certs on gitlab, along with every cert for every site I host is behind a framework I wrote that automatically obtains and renews certificates, so I didnt really think I had to do anything and that they would auto renew.

What I forgot is that while custom domains themselves for sites hosted on our git lab do indeed auto renew the default domain of *.qoto.io does not (its the only domain that doesn't. The reason for this is because the certbot doesnt support obtaining or renewing wildcard domains and are the only type of domain you have to renew manually. So I totally forgot that I actually **do** need to pay attention to the alerts.. next time I will.

Anyway it is fixed now and all is good.

@freemo @hansw @nommon

(60)➜ ~ curl https://nomnom.qoto.io/ curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above.

btw the certificate is doing fine on browsers, but it doesn’t work with all those command line tools, e.g. curl. it seems that the chain is incomplete (one in the trust chain needs extra download). is there any way to fix this?

@ShyKana

Interesting, this is the first im hearing of it... Do you know if curl has this problem with all LE certs or is it unique to qoto?

@hansw @nommon

@ShyKana

I can confirm I have the same issue when i try this through curl by the way... ill see what i can ddig up and what the solutions might be.

@hansw @nommon

@ShyKana

I just checked and the issue only shows up on the wildcard domain. I will look into this more tomorrow, might be a configuration issue on gitlab

@hansw @nommon