JWS header parameter 'url' required. about pebble HOT 4 CLOSED

@odedpriva As of today neither certbot nor dehydrated support the ACME protocol version that Pebble implements. I wouldn't expect they would work out-of-box with Pebble and this error about a missing JWS header parameter is one instance of why. These clients have implemented an ACME spec divergence from Boulder.

Can I ask why you're running Pebble instead of Boulder?

from pebble.

I'm looking for an internal ACME server for local development and staging environment.
We have a Docker based development environment and I would like to integrate an ACME service as part of it.

Boulder seems too much for our use case.

from pebble.

Hi @odedpriva,

Thanks for the explanation! That makes sense and I think Pebble will be a good fit for that setup one day but it's a little bit premature at this point since there are no compatible clients.

If you're interested in testing clients against an ACME server your best bet for the short term will be following Boulder's quick start guide, even if its a heavier weight option than you were hoping.

from pebble.

@cpu thanks. I will follow up on Pebble with anticipation.

from pebble.