mirror of
https://github.com/ridercz/AutoACME.git
synced 2026-04-25 15:15:53 +03:00
[GH-ISSUE #46] Upgrade instructions: ACMEv1 to ACMEv2? #36
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AutoACME#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chagrawil on GitHub (Jan 31, 2020).
Original GitHub issue: https://github.com/ridercz/AutoACME/issues/46
Is there a recommended upgrade path? More specifically, going from an ACMEv1 version to 1.6.2.0 for ACMEv2, are changes needed to the json files to enable or force v2?
@avonwyss commented on GitHub (Jan 31, 2020):
No, it should just work transparently. On the first request the new version of AutoACME will migrate the account to v2.
@carloslealxyzt commented on GitHub (Mar 4, 2020):
Hi, What I have to do to make the upgrade from ACMEv1 to ACMEv2? Just change the "ServerUri" in the "autoacme.json" file is enough? Is there any upgrade instructions?
@avonwyss commented on GitHub (Mar 4, 2020):
@carloslealxyzt It does that automatically if you're using the well-known LE servers, see
github.com/ridercz/AutoACME@0b4864e4d4/Altairis.AutoAcme.Core/AutoAcmeContext.cs (L20-L25)@carloslealxyzt commented on GitHub (Mar 4, 2020):
Hi @avonwyss, thanks for your response, I'm using AutoACME 1.5.4, and I think that I'm still using ACMEv1, because when I renew a domain, I get the e-mail to update.
@avonwyss commented on GitHub (Mar 4, 2020):
@carloslealxyzt V1.6.0 is the first to use ACMEv2 AFAIR.
@carloslealxyzt commented on GitHub (Mar 5, 2020):
Hi @avonwyss thanks for your response, is there any upgrade instructions? How should I do?
@avonwyss commented on GitHub (Mar 5, 2020):
@carloslealxyzt Make a backup of your files just in case, then replace the old version with the new version. You can then test it from the command line.
@RyanDansie commented on GitHub (May 12, 2020):
Here's how i did it: