Skip to content

Commit

Permalink
Fix to handle LE overload status 503 appropriately
Browse files Browse the repository at this point in the history
- 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
  • Loading branch information
mhoffrog committed Mar 1, 2023
1 parent d4befeb commit 15f96b7
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions acme.sh
Original file line number Diff line number Diff line change
Expand Up @@ -2229,6 +2229,12 @@ _send_signed_request() {
_debug3 _body "$_body"
fi

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

0 comments on commit 15f96b7

Please sign in to comment.