Right order to request certificate

[cpu]

@hiawatha

Are you sure that’s the same issue? In that one, the status is ‘pending’. My issue is about the status being ‘processing’.

It's a variant of the same order state transition problems. This issue should cover the problem you're experiencing: ACMEv2 - Errors during finalization leave order stuck processing. · Issue #3403 · letsencrypt/boulder · GitHub

@hiawatha

I removed my account key, created a new one and registered a new account. From then on, every certificate request failed. Even for the ones that worked fine with my previous account key. I changed my code to where it first does the status polling before finalizing. Now, every certificate request results in a certificate, even for that website that previously had a ‘processing’ state.

Can you please open a Boulder issue with a log showing the ACME messages sent/received during the case where every certificate status fails, and in the case where you've made the described polling change and can issue successfully? I'm not sure I understand what's going on and it would be much easier to debug with some logs Thank you.