Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: helpmecpos.com
I ran this command:
It produced this output: renewed cert successful
My web server is (include version):
The operating system my web server runs on is (include version): windows 10
My hosting provider, if applicable, is: self
I can login to a root shell on my machine (yes or no, or I don't know): yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot): 1.8.0
I am running connectwise control on this box and have to bind the cert to this software. I have a ticket open with them. My question is about the renewal process. It created a 2nd working directory labeled -0001 appended to the original directory (where the csr and key is located) and certbot placed the cert, chain, fullchain, and privkey here in -0001 as symbolic links. Those links point to a Certbot archive directory where the actual PEM files are located. I think this symbolic link has made the connectwise control ssl configurator tool to not being able to find the certificate correctly.
I get this message:
Looking for file "C:\certbot\live\helpmecpos.com\ScreenConnectPrivateKey.key" ...
Detecting your certificate...
Could not find valid certificates in "C:\certbot\live\helpmecpos.com".
Couldn't find a matching certificate. Returning to menu.
Press any key to continue . . .
Any of you have experience with connectwise control or this symbolic linking?