Mrten

I used to run it like this: ``` acmetool --xlog.severity=debug > dump 2>&1 ``` Have always made my config by hand, so no detailed clues.

just a small question for those that keep being reminded to upgrade (haven't tried myself yet): have you changed [the URL for](https://community.letsencrypt.org/t/staging-endpoint-for-acme-v2/49605) the endpoints? This is the old one: ```...

I'm thinking that you could differentiate on `prod.api.letsencrypt.org` between `acme-v01` and `-v02` via Host: headers, anyway, I'll try and report back.

[This](https://community.letsencrypt.org/t/staging-endpoint-for-acme-v2/49605) says: ``` This is a non-backward-compatible version of the API, so ACME v1 clients (almost all clients available today) will not work with the ACME v2 endpoint. Existing clients...

``` acme@acme:/var/lib/acme$ cat conf/target request: provider: https://acme-staging-v02.api.letsencrypt.org/directory [...] ```

other then upgrading go, no.

Just FYI: You are asking the author of rilts not to use his own licensing ways. https://github.com/hlandau/rilts/blob/master/RILTS.md

probably same as [this answer](https://github.com/hlandau/acme/issues/215#issuecomment-259084412)?

0.0.58 does not help.

Understood! Change this into a feature request for `acmetool cleanup` then perhaps?