Bleh. @musllibc and related domains had expired certs because umask in my @letsencrypt script resulted in .well-known files being mode 600.
-
-
Replying to @RichFelker
Had a similar problem: new
@letsencrypt ToS wasn't accepted and the automated tool failed to report/refresh the certificates1 reply 0 retweets 0 likes -
Replying to @lafp
My problem was purely in my script invoking acme_tiny.py, not anything
@letsencrypt did to break things.1 reply 0 retweets 0 likes
Replying to @RichFelker @lafp
I had run the script to check it after making changes but apparently the problem only triggered when certs actually needed renewal.
5:16 PM - 5 Oct 2016
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.