My issue here is this:
getting a certificate fails, and it fails as if the server was unreachable. I don’t understand why, seeing as somebody does check in on the server, and successfully gets the challenge content when I try renewing.
I’ve been running certify the web, but did decide to try a manual process with certbot, and even then, after verifying myself that the contents are available, it doesn’t work.
Here’s a screenshot, showing a wireshark capture with a successful http get during the verification process.
I’ve tested this from other countries via my VPN, and it seems that it is accessible just fine.
I’ve included the template below:
My domain is: simo.korho.org
I ran this command:certbot certonly --test-cert --config-dir /home/joakim/testi-kansio/config --work-dir /home/joakim/testi-kansio/work --logs-dir /home/joakim/testi-kansio/log -d simo.korho.org --agree-tos --manual
It produced this output: Failed authorization procedure. simo.korho.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://simo.korho.org/.well-known/acme-challenge/jznsrwSJyvM2GqjNiY-bCVFTViYZ4sFW197J7QvSqkM: Timeout during connect (likely firewall problem)
My web server is (include version): IIS 10.0
The operating system my web server runs on is (include version): Windows Server 2016
My hosting provider, if applicable, is: n/a
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): certbot 0.31.0