Daniel McCarney

@icelava What version of acme-dns are you running? Since v0.8 `acme-dns` has used `certmagic` to handle renewing its API certificate. It currently uses the default times configured by that library....

> Another solution that was brought up by @webprofusion-chrisc would be to actually create support script (probably within the acme-dns project itself!) to initialize the database, and create preprimed accounts...

Based on the error message failing to parse a JSON response that has a leading `

@rayrapetyan Thanks for reporting. I opened a similar issue on https://github.com/kristapsdz/acme-client-portable/issues/46 but forgot to cross-post to this issue. > Should be updated to:https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf This would fix this immediate breakage but...

hi @mhoran, +1 for supporting this. It's an important feature Let's Encrypt relies on to update subscribers about certificate expiration and other important subscriber agreement changes. > Here's the relevant...

I have the same requirement and have been considering different approaches to work around not having creation timestamp in `KeysetInfo`, none of which seem ideal (separate metadata, abusing key IDs...

@tholenst Thanks for commenting :-) > However, at the moment I personally tend to the variant that we have an always incrementing ID in the keyset instead of the creation...

> I just look at a lot of code in other libraries which do similar things and which has a creation time. Doing so, I found more issues with the...

Do you have any logs of the JWS that doesn't validate?

Unfortunately the logs at the top don't contain the JWS object. Perhaps @mholt knows if it's possible to have Caddy log the JWS with a config change or whether it...