Skip to content

Commit 15f96b7

Browse files
committed
Fix to handle LE overload status 503 appropriately
- LE HTTP response status 503 is not an error, it must be handled via sleep and retry - s. https://community.letsencrypt.org/t/new-service-busy-responses-beginning-during-high-load/184174 fixes #4530
1 parent d4befeb commit 15f96b7

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

acme.sh

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2229,6 +2229,12 @@ _send_signed_request() {
22292229
_debug3 _body "$_body"
22302230
fi
22312231

2232+
if [ "$code" = '503' ]; then
2233+
_sleep_overload_retry_sec=3
2234+
_info "It seems the CA server is currently overloaded, let's wait and retry. Sleeping $_sleep_overload_retry_sec seconds."
2235+
_sleep $_sleep_overload_retry_sec
2236+
continue
2237+
fi
22322238
if _contains "$_body" "JWS has invalid anti-replay nonce" || _contains "$_body" "JWS has an invalid anti-replay nonce"; then
22332239
_info "It seems the CA server is busy now, let's wait and retry. Sleeping $_sleep_retry_sec seconds."
22342240
_CACHED_NONCE=""

0 commit comments

Comments
 (0)