A quick question for a wider audience, I am seeing this from several domains on several servers in the last few days. Very long term deployments and stable configurations. Are others seeing "urn:ietf:params:acme:error:connection" ... "Timeout after connect (your server may be slow or overloaded)" …

I've checked over the configurations and logs and am seeing the same as you describe tomryder-inspirenet , the HTTP->HTTPS (301/302) subsequent requests aren't arriving. First thing that comes to mind is an accidental outbound firewall issue on the LE outbound servers (80=Accept, 443=Whoops).

That is not enough info to work with. There is a wide variety of problems that cause that. If it only happens after redirect a common cause is if you have IPv6 AAAA records for your domain that don't work properly. Let's Encrypt will fallback/retry with IPv4 but only for the initial request - not…

I posted about a generic issue that I'm seeing across domains/servers, within 30 minutes there was confirmation from tomryder-inspirenet , and his information was excellent. a common cause is if you have IPv6 AAAA records for your domain that don't work properly No, not in what I'm observing. …

Thank you, I have created a new thread with the templated information you requested: HTTPS connection failures (timeouts) from validation servers

[image] jc-rimu: I posted about a generic issue that I'm seeing across domains/servers Sure, but, often times the same symptoms are from very different causes. And, different posters have different skills so the debug steps vary. Even the full error message would help. Let's Encrypt has 5 v…

This is the LE response for a new certificate earlier today (it failed in the same way as the renews per above). Of the information I can share this one is not too private. The well-known file is still present, you can curl that and see there is no issue requesting the file. The domain name neoq…

*(don't try trouble shooting it now...)

On one of our affected servers I set the MTU to 1280 and the renew worked. This is good debug information for the Let's Encrypt team. I have reverted that server's MTU as a workaround is not a solution. Thanks MaxHearnden for the suggestion and tomryder-inspirenet for doing an initial try with th…

I have repeated this on all affected servers. Reduce MTU to 1280 -> LE renew -> MTU reverted to 1500. This MTU workaround is not a solution, escalation to the Let's Encrypt team absolutely required. fyi tomeryder-inspirenet

In this thread are two independent hosting providers in New Zealand that are affected. This Let's Encrypt issue is in its day 5th day of being present (Thurs -> Mon so far), I allowed the weekend to see if any transient issue sorted itself out before raising it here. The other thread for reference…

"your server may be slow or overloaded" acme-v02.api

Help

Bruce5051 December 9, 2025, 1:01am 17

Statuses for New Zealand Internet posted here: HTTPS connection failures (timeouts) from validation servers - #22 by Bruce5051

Topic		Replies	Views
HTTPS connection failures (timeouts) from validation servers Help	35	1013	December 14, 2025
Failed to connect to the Let's Encrypt server https://acme-v02.api.letsencrypt.org Help	17	29538	October 24, 2019
Let's Encrypt server has trouble acessing my server Help	6	1718	September 14, 2018
ConnectTimeout: HTTPSConnectionPool (host='acme-v02.api.letsencrypt.org', port=443) Help	11	10179	September 12, 2018
Urn:ietf:params:acme:error:connection Status: 400 Timeout after connect (your server may be slow or overloaded) Help	3	864	November 26, 2023

"your server may be slow or overloaded" acme-v02.api

Related topics