7 ms·
It would not have been sticky for the entire day. If it was sticky at all, it would have been only during the 90 minute period I referenced. It's most likely th
by jaas 3mo ago
It would not have been sticky for the entire day. If it was sticky at all, it would have been only during the 90 minute period I referenced. It's most likely that there is some other issue with how you're requesting the cert. Folks can help debug at: https://community.letsencrypt.org/ https://community.letsencrypt.org/
- widdakay 3mo agoI ran the exact same command now and it's working, so it is possible I was unlucky and was hitting all the worst possible cases.
- sgt 3mo agoCould it be that he was simply throttled while retrying? That seems plausible, and it would make it seem like a long outage.
- widdakay 3mo agoI updated the post title to say (Fixed) now.
- jaas 3mo agoSince Let's Encrypt wasn't down most of the day if would be helpful if you could update the title to reflect that.
- widdakay 3mo agoI updated the title. Let me know if you think it's more accurate. It did appear as down for me though.
- jaas 3mo agoYeah, thanks
- widdakay 3mo agoI did not intend this to hit the top of the front page lol. I just posted it and then came back 15 minutes later to it having exploded.
- jaas 3mo agoNo worries
- taspeotis 3mo agoThanks for securing the web
- sam_lowry_ 3mo agoThank them for making the web depend on a single US-based shady org, as if DNS was not enough.
- cpach 3mo agoFeel free to launch your own CA.
- sam_lowry_ 3mo agoNo-no, I would rather go back to the good old HTTP/1.1. P.S. JS injection into TCP packets and other meddling with passthrough data should be banned legally, not technically via encryption.
- soco 3mo agoI wish you good luck in court trying to get compensation for the damage you've got through a JS injection attack. Because people prefer to lock their valuables instead of constantly having to identify and sue thieves.