SSL validation failure during ghost setup ssl

ACME Challenge Failures in Ghost CLI

The ghost setup ssl command automates the acquisition of Let's Encrypt certificates and the corresponding Nginx configuration. This process relies on the ACME protocol, which requires the server to be publicly reachable via port 80 and 443 to validate domain ownership through DNS A-records.

When the validation process fails due to network restrictions or DNS propagation delays, the CLI may leave the Nginx configuration in an inconsistent state. There is uncertainty regarding the internal mechanism the CLI uses to track repeated failed attempts and how it interacts with Let's Encrypt rate limits.

Does the Ghost CLI implement a local cooldown or retry logic to prevent hitting ACME rate limits during repeated setup attempts? If a validation failure occurs, does the tool automatically revert Nginx configuration changes to maintain site availability?