Well.... that did the trick!
We have 2 other servers updated the same way, will replace server files with those
Something didn't work out properly updating with the script for sure
Thank you
Antonio
I've had many LetsEncrypt auto-renewal failures, and I'm finally realizing that the problem is related to various storage locations used by letsencrypt-win-simple and now wacs.exe.
My C:SolidCPServerbinLetsEncrypt includes both letsencrypt.exe (version 1.9.7) and wacs.exe (version 2.0.8), and I've previously used letsencrypt.exe (version 1.9.1) which stored its information in user-specific locations, and so I've ended up with a mess of information in all of the following registry and file locations.
1.9.4 and earlier:
HKEY_CURRENT_USERSoftwareletsencrypt-win-simple
%APPDATA%letsencrypt-win-simple
1.9.5:
HKEY_LOCAL_MACHINESoftwareletsencrypt-win-simple
%PROGRAMDATA%letsencrypt-win-simple
1.9.9:
%PROGRAMDATA%letsencrypt-win-simplehttpsacme-v01.api.letsencrypt.org
2.0.0:
%programdata%win-acmeacme-v02.api.letsencrypt.org
SolidCP 1.4.4 appears to be using the newer wacs.exe, so my next step might be to make sure all certificates are in the new system (by running wacs --import and/or using SolidCP to reinstall some certificates). Then maybe I can delete the data from the older locations, as well as the older scheduled task(s), keeping the newer one called "win-acme renew".
But I'm not sure if wacs.exe is really working correctly. It does seem to work, but when I run it manually I see many errors as shown below.
Hello,
You are correct we are using WACS from now on but we included the older LE-Win-Simple client as there was no documented way to upgrade.
You can use the upgrade switch or run the WACS client and select upgrade from the more options menu.
Regards,
Trevor
Are certificates now auto updated using WACS? Or will I have to manually do something with certificates to force WACS (and ACMEv2) usage?
Hello,
At the current moment they are not automatically imported to WACS as at the time we implemented this to SolidCP the import options was not finalized.
I have added this to the tracker ( https://github.com/FuseCP/SolidCP/issues/21 ).
Regards,
Trevor
