To migrate to another machine, you may follow these steps.
The files in the directory that contains
wacs.exe can be copied to the new machine.
Alternatively you can download the latest release, but in that case make sure to
check the upgrade instructions for possible breaking changes to
take into account.
Move the configuration files to the new machine. They are stored in the
that can be customized in settings.json). Move these files
to new other machine.
If you’re using HTTP validation directly from the old machine (which is most common scenario), you will have to update your DNS records* before you can validate host names on the new machine
*) Don’t forget the AAAA/IPv6 records when doing so!
That means that in theory you won’t be able to get certificates before you go “live” on the new machine, which is a problem for services that require continuous availability. To work around this we can:
.renewal.jsonfiles to reveal the passwords for the
.pfxfiles in the
%ProgramData%\win-acme\acme-v02.api.letsencrypt.org\Certificates, though that can be customized in settings.json) and import those on the new machine. If your renewals are still encrypted, you can access these passwords from the main menu (
Show details). In theory this could be scripted, please contribute!
PrivateKeyExportablesetting to true in settings.json, force renew the certificates to make this setting take effect and export and import them manually using
certlm.msc, or use a Powershell script to do so (if you wrote one you’d like to share, please contribute!)
Test email notification