Thanks Trevor, that's interesting, especially since my second scheduled task has not been successful in getting everything to renew automatically.

I have tried adding --usedefaulttaskuser when running the LetsEncrypt command, but it still stored the data in Administrator user folder. On the other hand, I think the following might be working to run the command as system and store the data under All Users:

psexec -i -s "C:SolidCPServer asp.net v4.5binletsencryptletsencrypt.exe"

I don't always have success using SolidCP to install the certificate. It fails if the site has Web Site Pointers that are actually resolving elsewhere, and sometimes it fails for other reasons. In these cases, it is unfortunate that SolidCP often reports "LetsEncrypt Certificate successfully installed on website" even though it failed. Anyway, sometimes I find it necessary to go into command line to successfully install the certificate.

Hello,

I am glad you was able to resolve the issue. SolidCP does not handle the install of the certificate and runs the command checking for errors during the process.

When you make the certificate manually do you have to make any changes to get it to work?

Kind Regards,

Trevor Robinson

I think the most recent one worked in command line without any changes. That one had apparently timed out in SolidCP (and displayed the Error.htm message after a LONG delay).

Meanwhile, for another site that had bogus Web Site Pointers, I'm pretty sure SolidCP showed "successfully installed" but no certificate was actually installed until I ran LetsEncrypt manually and specified only the active hostnames.