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. crt.sh | 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:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
I have experience with using certificates in a Linux environment but not in Windows. I ran into an issue helping my wife at her store where the PCI security scan failed because by default the certificate for RDP is self signed. Looking around on Stack Exchange I see that a Let's Encrypt cert should work. So my question is whether it is possible to obtain a Let's Encrypt cert with the network setup at my wife's business. I have turned off the RDP port until I can sort this out.
At the business we are running a Windows 10 Pro PC behind a cable modem using an assigned DHCP address belonging to Comcast. The DNS address is fixed but not precisely a static. The modem is set to forward RDP session requests to the PC. The PC uses a 10 network address setup by the cable modem. We don't run IIS or Windows Server on the PC. I am using the win-acme.exe client and the validation step fails presumably because my wife's business does not own the DNS address. Under these circumstances is it possible to use a Let's Encrypt certificate with RDP? If not do you have any recommendations?
Thanks greatly in advance for any help and apologies if I missed a relevant support article.