2 ms·

We had this issue with a desktop client, this seems to be working for us as a fix: https://twitter.com/Zap42/status/1443647882045927427 https://twitter.com/Zap

We had this issue with a desktop client, this seems to be working for us as a fix: https://twitter.com/Zap42/status/1443647882045927427 https://twitter.com/Zap42/status/1443647882045927427 Also, just waiting, or maybe rebooting. Edit: ah wrong thread sorry! This is re: letsencrypt.

judge2020 5y ago
Sounds like that's a different issue then, because that solves the LetsEncrypt issue - the Slack issue is thanks to DNSSec (and Slack uses a Digicert HTTPS certificate[0]) 0: https://crt.sh/?Identity=slack.com&exclude=expired&match== https://crt.sh/?Identity=slack.com&exclude=expired&match==
kelnos 5y ago
Slack doesn't appear to use LetsEncrypt (checking their cert on slack.com and app.slack.com shows a DigiCert cert), so this will not do anything to help.