Please fill out the fields below so we can help you better.
My domain is: I prefer not to share this, because it is not meant for public but for internal usage.
I ran this command: letsencrypt.exe --manualhost myurl.com --webroot “C:\Bitnami…\apache2\htdocs”
It produced this output: Everything worked fine. Certificates were generated in a user folder. I copied them manually to my apache2 path.
My web server is (include version): Apache2
The operating system my web server runs on is (include version): Windows Server 2012 R2
My hosting provider, if applicable, is: Contabo
I can login to a root shell on my machine (yes or no, or I don’t know): Yes, but honestly I can’t do much on Windows.
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
I used the letsencrypt-win-simple client to obtain a certificate on Windows for an Apache2. The tool asked me to generate a scheduled task for renewal. I chose “No”, because I wanted to see that it works first. I copied all files to the apache and now the first certificate works fine. My questions is: How can I test that a renewal will work in the future? As far as I can see, the tool does not allow me to create a scheduled task without creating a new csr, right? How can I know that the certificate will work in the future? I assume I need to write a batch file that is called from the tool and copies all result files to the apache folder, but I would love to test this in advance to make sure we will have a valid certificate. Is it possible the make the renewal a week before the certificate runs out to have time to react in case of failure? Is there any best practice for cases like this?