Staging Certificate Generation Failure

We see this issue on multiple domains on the staging server as 6:30 UTC (perhaps after the boulder update)

My domain is:

We use Acme4j.

It produced this output:
Challenge fails:
"type": "urn:ietf:params:acme:error:malformed",
"detail": "Method not allowed",
"status": 405

Many thanks,
Danny Mann, Duda

1 Like

We're going to need MOAR LOGS if we're to understand what's happening.

Best guess right now is you're sending a GET where you should send a POST.

1 Like

Hello, Thanks for the quick reply.

This is an example of the logs we see:
WARN Failed Challenge for domain! result: INVALID (

We have the exact same code on production which points to the production acme ENV, in which it works fine.

As I've said, this started suddenly today without any change in our code (as far as I know...), we generate certificates all the time.


1 Like

That URL I think wants a POST. (a signed POST)

See if you can find the "order" URL instead of the "challenge" one.

1 Like

I'm sorry I'm not sure I understand.
Which URL do you think wants a POST? The /acme/chall-v3/... ?

This was related to an issue with Acme staging env ("Increased remove validation failures"), this was resolved by Let's Encrypt.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.