The Let's Encrypt certificate for the website seems to have expired, resulting in a warning when trying to visit the website.
The Let's Encrypt certificate for the website seems to have expired, resulting in a warning when trying to visit the website.
<!-- github-sync-id:2267486807 -->
Could you provide an URL and perhaps a screenshot?
For me, wiki.znc.in has a certificate that was issued on April 24th and is valid until July.
Could you provide an URL and perhaps a screenshot?
For me, wiki.znc.in has a certificate that was issued on April 24th and is valid until July.
<!-- github-comment-id:2081437593 -->
The problem was first identified through a GitHub Action, so I don't think this is something local on my side.
Sure, https://wiki.znc.in/ZNC
https://cdn.ravshort.com/rEGU2/pUVUyuLI79.png
https://cdn.ravshort.com/rEGU2/WOtAdiLA21.png
Edit:
The problem was first identified through a [GitHub Action](https://github.com/awesome-selfhosted/awesome-selfhosted-data/actions/runs/8863010642/job/24336573157#step:4:2700), so I don't think this is something local on my side.
<!-- github-comment-id:2081444526 -->
I can observe the same problem, outdated certificate served to both me (Android tablet) and ssllabs.com over IPv4.
My connection is not IPv6 capable (sigh…) but ssllabs.com tests both, and the updated certificate was served for wiki.znc.in over IPv6 when checked.
Numerous forum and Stack Exchange threads over the years refer to various issues with nginx not using an updated certificate for some reason. Not knowing the exact setup, I won't speculate too much, but it does sound like sometimes nginx fails to replace all worker processes upon config reload. 🤷♂️
(These days I use Caddy for TLS, so my nginx debugging is rusty)
I can observe the same problem, outdated certificate served to both me (Android tablet) and ssllabs.com over IPv4.
My connection is not IPv6 capable (sigh…) but ssllabs.com tests both, and the updated certificate _was served_ for wiki.znc.in over IPv6 when checked.
Numerous forum and Stack Exchange threads over the years refer to various issues with nginx not using an updated certificate for some reason. Not knowing the exact setup, I won't speculate too much, but it does sound like sometimes nginx fails to replace all worker processes upon config reload. 🤷♂️
(These days I use Caddy for TLS, so my nginx debugging is rusty)
<!-- github-comment-id:2081470520 -->
Ah, yup. Thanks for that info and sorry for not checking ipv4 / ipv6 myself. The certificate is indeed valid over IPv4:
```
$ curl -6 https://wiki.znc.in
$ curl -4 https://wiki.znc.in
curl: (60) SSL certificate problem: certificate has expired
```
<!-- github-comment-id:2081475570 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Let's Encrypt certificate for the website seems to have expired, resulting in a warning when trying to visit the website.
Could you provide an URL and perhaps a screenshot?
For me, wiki.znc.in has a certificate that was issued on April 24th and is valid until July.
Sure, https://wiki.znc.in/ZNC
https://cdn.ravshort.com/rEGU2/pUVUyuLI79.png
https://cdn.ravshort.com/rEGU2/WOtAdiLA21.png
Edit:
The problem was first identified through a GitHub Action, so I don't think this is something local on my side.
I can observe the same problem, outdated certificate served to both me (Android tablet) and ssllabs.com over IPv4.
My connection is not IPv6 capable (sigh…) but ssllabs.com tests both, and the updated certificate was served for wiki.znc.in over IPv6 when checked.
Numerous forum and Stack Exchange threads over the years refer to various issues with nginx not using an updated certificate for some reason. Not knowing the exact setup, I won't speculate too much, but it does sound like sometimes nginx fails to replace all worker processes upon config reload. 🤷♂️
(These days I use Caddy for TLS, so my nginx debugging is rusty)
Ah, yup. Thanks for that info and sorry for not checking ipv4 / ipv6 myself. The certificate is indeed valid over IPv4: