3 ms·

I'm not sure if your higher error rate is sticky per user or something, but I've tried 10+ times throughout the day and have had 0 successes. They all come back

I'm not sure if your higher error rate is sticky per user or something, but I've tried 10+ times throughout the day and have had 0 successes. They all come back as internal server error. That's why I eventually posted.

jaas 5mo 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 5mo ago
  I 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 5mo ago
  Could it be that he was simply throttled while retrying? That seems plausible, and it would make it seem like a long outage.
- widdakay 5mo ago
  I updated the post title to say (Fixed) now.
  - jaas 5mo ago
    Since Let's Encrypt wasn't down most of the day if would be helpful if you could update the title to reflect that.
    - widdakay 5mo ago
      I updated the title. Let me know if you think it's more accurate. It did appear as down for me though.
      - jaas 5mo ago
        Yeah, thanks
        widdakay 5mo ago
        I 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 5mo ago
        No worries
        taspeotis 5mo ago
        Thanks for securing the web
        sam_lowry_ 5mo ago
        Thank them for making the web depend on a single US-based shady org, as if DNS was not enough.
        cpach 5mo ago
        Feel free to launch your own CA.
        sam_lowry_ 5mo ago
        No-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 5mo ago
        I 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.
teekert 5mo ago
Why are you trying? Doesn’t Caddy (or something) just takes care of this well in advance and should have no issues with one or several days of my service at all at any time? Edit: my bad. I’ve tried as well recently, when you’re rushing to get your new domain up of course…

jaas 5mo 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 5mo ago
I 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 5mo ago
Could it be that he was simply throttled while retrying? That seems plausible, and it would make it seem like a long outage.
widdakay 5mo ago
I updated the post title to say (Fixed) now.
- jaas 5mo ago
  Since Let's Encrypt wasn't down most of the day if would be helpful if you could update the title to reflect that.
  - widdakay 5mo ago
    I updated the title. Let me know if you think it's more accurate. It did appear as down for me though.
    - jaas 5mo ago
      Yeah, thanks
      - widdakay 5mo ago
        I 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 5mo ago
        No worries
        taspeotis 5mo ago
        Thanks for securing the web
        sam_lowry_ 5mo ago
        Thank them for making the web depend on a single US-based shady org, as if DNS was not enough.
        cpach 5mo ago
        Feel free to launch your own CA.
        sam_lowry_ 5mo ago
        No-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 5mo ago
        I 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.

teekert 5mo ago

Why are you trying? Doesn’t Caddy (or something) just takes care of this well in advance and should have no issues with one or several days of my service at all at any time? Edit: my bad. I’ve tried as well recently, when you’re rushing to get your new domain up of course…