4 ms·
Could be related to the currently ongoing Let's Encrypt certificate expiration event(1) that is causing fun for engineers today(2). (1) https://community.letse
by nathanyz 5y ago
Could be related to the currently ongoing Let's Encrypt certificate expiration event(1) that is causing fun for engineers today(2).
(1) https://community.letsencrypt.org/t/help-thread-for-dst-root-ca-x3-expiration-september-2021/149190 https://community.letsencrypt.org/t/help-thread-for-dst-root...
(2) https://twitter.com/search?q=letsencrypt&src=typed_query&f=live https://twitter.com/search?q=letsencrypt&src=typed_query&f=l...
- betaby 5y agoNo. DNSSEC has nothing to do HTTPS.
- nathanyz 5y agoInterdependencies among services can cause all sorts of unexpected issues.
- eropple 5y agoNo, it's not. This is a fault that appears to be from removing DNSKEY and DNS records at the exact same time. Let's Encrypt doesn't have anything to do with that even if somebody uses it. Slack uses DigiCert.
- kelnos 5y agoIt can, but it did not, in this case. Slack uses DigiCert, not LetsEncrypt, and if you poke entries into your /etc/hosts file for various slack hostnames, things work just fine (which they wouldn't if it was a TLS cert problem).