I'm using acmetool 0.67 as the client, and I see it is still listed in ACME Client Implementations - Let's Encrypt Today I received the following email: Hello, Action is strongly recommended to prevent problems with your Let's Encrypt certificate renewals. A client you have used to access the …

[image] cpu: I suspect users of acmetool were mistakenly included in this email batch. Yes, confirmed. Requests from acmetool are using a unique UserAgent and were only mistakenly included in the Go-http-client-focused email batch. Sorry for the confusion!

Hi @bago please read [image] Let's Encrypt client user-agent problem Client dev i… That's the same problem.

As a fellow acmetool user, I’d suggest slowly changing to another client. It looks increasingly unlikely that the author is going to rescue it before the ACME v1 switch-off happens.

I’m using Acme.sh, too, but I still have acmetool on legacy systems, so I’d like to understand how long I can “live” with acmetool and if/when I will be forced to switch to acme.sh the legacy deployments.

I’m not sure I understand: if the problem is ONLY the useragent I could tweak acmetool on my own and make sure it uses an useragent. But if the problem is in the number of requests, then I’d waste my time doing the patch. From the email content I cannot tell if fixing the user-agent could be all I …

I’ve checked acmetool sourcecode and it sounds like it is declaring a complete user-agent: [image] hlandau/acme :lock: acmetool, an automatic certificate acquisition tool for ACME (Let's Encrypt) - hlandau/acme “acmetool acmeapi Go-http-client/1.1 linux/amd64” …

[image] bago: do you have more info/details about this? I don't use / know that client. And I didn't only read the other topic, so I've added a link.

[image] bago: I’m using Acme.sh, too, but I still have acmetool on legacy systems, so I’d like to understand how long I can “live” with acmetool and if/when I will be forced to switch to acme.sh the legacy deployments. in its current state acmetool will be completely broken when ACME v1 is de…

Action required: Let's Encrypt client problem - acmetool

Help

cpu May 23, 2019, 4:28pm 8

in its current state acmetool will be completely broken when ACME v1 is deprecated.

I suspect users of acmetool were mistakenly included in this email batch. @ezekiel can you confirm this?

Topic		Replies	Views
Let's Encrypt client user-agent problem Client dev	1	2939	May 22, 2019
Update your client software to continue using Let's Encrypt Help	2	2317	April 17, 2020
ACMEv1 deprecation e-mails Site Feedback	8	3824	January 31, 2020
Update to API V2 with acmetool Help	12	2808	August 3, 2020
Updating to ACMEv2 Compatible Client Help	3	525	February 14, 2021

Action required: Let's Encrypt client problem - acmetool

Related topics