[GH-ISSUE #46] Upgrade instructions: ACMEv1 to ACMEv2? #36

Closed
opened 2026-02-26 21:31:23 +03:00 by kerem · 8 comments
Owner

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?

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?
kerem closed this issue 2026-02-26 21:31:23 +03:00
Author
Owner

@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.

<!-- gh-comment-id:580770339 --> @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.
Author
Owner

@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?

<!-- gh-comment-id:594626476 --> @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?
Author
Owner

@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)

<!-- gh-comment-id:594667050 --> @avonwyss commented on GitHub (Mar 4, 2020): @carloslealxyzt It does that automatically if you're using the well-known LE servers, see https://github.com/ridercz/AutoACME/blob/0b4864e4d486e2455c6f4405a3816a6f62c58ce9/Altairis.AutoAcme.Core/AutoAcmeContext.cs#L20-L25
Author
Owner

@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.

<!-- gh-comment-id:594677678 --> @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.
Author
Owner

@avonwyss commented on GitHub (Mar 4, 2020):

@carloslealxyzt V1.6.0 is the first to use ACMEv2 AFAIR.

<!-- gh-comment-id:594789003 --> @avonwyss commented on GitHub (Mar 4, 2020): @carloslealxyzt V1.6.0 is the first to use ACMEv2 AFAIR.
Author
Owner

@carloslealxyzt commented on GitHub (Mar 5, 2020):

Hi @avonwyss thanks for your response, is there any upgrade instructions? How should I do?

<!-- gh-comment-id:595117371 --> @carloslealxyzt commented on GitHub (Mar 5, 2020): Hi @avonwyss thanks for your response, is there any upgrade instructions? How should I do?
Author
Owner

@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.

<!-- gh-comment-id:595174913 --> @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.
Author
Owner

@RyanDansie commented on GitHub (May 12, 2020):

Here's how i did it:

  1. Download the file AutoACME-1.6.2.zip from https://github.com/ridercz/AutoACME/releases/tag/v1.6.2
  2. Extract the zip file on the server. On my system the existing installation was on a path like C:...\AutoAcme-1.5.1 so the new version was unzipped to C:...\AutoAcme-1.6.2
  3. Copied the autoacme.json and autoacme.json.old files from the old installation folder to the new one
  4. Updated my task scheduler job to the file path for the new version exe (could also rename the folders so the new version was on the same path as the old one)
<!-- gh-comment-id:627151938 --> @RyanDansie commented on GitHub (May 12, 2020): Here's how i did it: 1. Download the file AutoACME-1.6.2.zip from https://github.com/ridercz/AutoACME/releases/tag/v1.6.2 2. Extract the zip file on the server. On my system the existing installation was on a path like C:\...\AutoAcme-1.5.1 so the new version was unzipped to C:\...\AutoAcme-1.6.2 3. Copied the autoacme.json and autoacme.json.old files from the old installation folder to the new one 4. Updated my task scheduler job to the file path for the new version exe (could also rename the folders so the new version was on the same path as the old one)
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AutoACME#36
No description provided.