Fail to load resource from 'https://acme-v02.api.letsencrypt.org/acme/new-order': urn:ietf:params:acme:error:badNonce

[kimbirkelund]

I've started getting the following error when renewing certificates:

Exception setting up Let's Encrypt certificate: Fail to load resource from 'https://acme-v02.api.letsencrypt.org/acme/new-order'.
urn:ietf:params:acme:error:badNonce: JWS has an invalid anti-replay nonce: "0001nQHjcj8V0RNRp1k9MRB5NheGz8TT0wLMJgZ9gaSqEiQ"

It happens in FluffySpoon.AspNet.LetsEncrypt.Certes.LetsEncryptClient.PlaceOrder.

Any idea how to solve this?

[ffMathy]

That's new. Never seen that before. Let's see if anyone else is having the same issues.

[kimbirkelund]

Looking a bit deeper I'm thinking this might actually be an issue with Certes instead. Still investigating.

[kimbirkelund]

Never mind, turns out to not be an issue - my problem is elsewhere.

[eliezer15]

@kimbirkelund one of our applications is running into a similar issue, do you have any insights of what the problem was? :)

Thanks in advance!

[kimbirkelund]

No, I never did get it working. I switched to using Azures native certificate creation.

[MarkCiliaVincenti]

I'm having this issue.

[ffMathy]

I am so sorry, but I have not got a lot of time lately to fix this. PRs are very welcome!

[MarkCiliaVincenti]

To be honest I restarted the application and the problem got resolved on its own but it was giving that error for days before so something got stuck.

…

On Sat, 29 May 2021, 22:12 Mathias Lykkegaard Lorenzen, < ***@***.***> wrote: I am so sorry, but I have not got a lot of time lately to fix this. PRs are very welcome! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7U7YGQE4XME3Q32XR4SJLTQFDEJANCNFSM4KGBJD3A> .

[ffMathy]

Interesting. Any idea on the cause? And thank you for sharing this with us.

[MarkCiliaVincenti]

Earlier I had errors that it couldn't connect to the resource; I think let's encrypt was down.

…

On Sun, 30 May 2021, 09:15 Mathias Lykkegaard Lorenzen, < ***@***.***> wrote: Interesting. Any idea on the cause? And thank you for sharing this with us. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7U7YCOT6XI2N2YC7IKA63TQHQ2DANCNFSM4KGBJD3A> .

[MarkCiliaVincenti]

I was getting this again after a while. Reverted back to using FluffySpoon.AspNet.LetsEncrypt

[ffMathy]

The project is not dead. PRs are very welcome, and will be reviewed and merged.

Also, log files etc would be helpful.