I see here my domain has ssl https://tools.letsdebug.net/
but my site wont open with ssl and during request for that, I got error
My domain is: .ir
I ran this command: certbot certonly --standalone -d .ir -d www..ir --debug-challenges -v
It produced this output: requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))
My web server is (include version): IIS
The operating system my web server runs on is (include version): windows server 2019
I can login to a root shell on my machine
The version of my client is : I don't know the version, I just download this file certbot-beta-installer-win_amd64_signed.exe and use it
I put the license here:
In Windows Server 2019, certificates are typically stored in the Windows Certificate Store. The path to the certificate store is usually:
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys
or
C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys
See the EFF announcement below and links for alternatives including Certify. Certbot was never well integrated with IIS and Certify will be much easier.
Which program? Certify has an excellent support forum of their own. And, their main developer regularly appears here.
I personally am not helping with Certbot installs on Windows anymore since EFF is not supporting it. Maybe someone else here will help if you have questions about that.
Even if you asked last year I still would have suggested Certify instead of Certbot if you have IIS. Certbot was always difficult to use with IIS
The easiest way to use the app is to set the hostname (fully qualified domain) in your IIS bindings so that domains included on certificates can be easily matched with the respective website bindings, otherwise by default your new certificate won't be automatically applied to any IIS websites.