Here is my experience: First, I set the DNS TXT record properly. Then I triggered the challenge, invoke the /finalize API immediately and got the error response: {u\'status\': 403, u\'type\': u\'urn:ietf:params:acme:error:orderNotReady\', u\'detail\': u\'Order\\\'s status ("pending") is not accep…

[image] Osiris: First check the order status, then go to /finalize. That's possible, but that's not really a solution you should use. Better: Create all challenges Confirm all challenges, so Letsencrypt starts to check every challenge check every challenge, if the challenge is valid / inva…

A question about Order Status: pending to ready

Client dev

griffin December 25, 2020, 5:18am 13

Basically. Technically Let's Encrypt checks once from its primary server then three more times from three different AWS instances.

2 Likes

Topic		Replies	Views
Order status pending, is not acceptable for finalization Client dev	17	6374	April 3, 2020
Staging v2: order stuck in "pending" state even if authorization is "valid" Client dev	4	4517	June 6, 2018
A question about /finalize API Client dev	13	830	January 20, 2021
Pending, pending, … suddenly valid? Client dev	14	1746	April 17, 2020
Orders stuck on ready Client dev	15	607	August 2, 2024

A question about Order Status: pending to ready

Related topics