# Certbot Timeout **URL:** \ **Category:** Help\ **Created:** [February 23, 2023, 7:43pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314 "2023-02-23T19:43:46Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Jon\_AK](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@Jon\_AK](https://community.letsencrypt.org/u/Jon_AK)\ **Post date:** [February 23, 2023, 7:43pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/1 "2023-02-23T19:43:46Z")
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](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: [jcasvcs.com](http://jcasvcs.com) and subdomain [odoo.jcasvcs.com](http://odoo.jcasvcs.com) I ran this command: certonly --standalone --register-unsafely-without-email -d [jcasvcs.com](http://jcasvcs.com) -d [odoo.jcasvcs.com](http://odoo.jcasvcs.com) It produced this output: Detail: 162.211.27.195: Fetching [http://jcasvcs.com/.well-known/acme-challenge/PwIx4G-80TMzwC\_bwZtAe1IrDF-2qs00xHAEeikVoRs:](http://jcasvcs.com/.well-known/acme-challenge/PwIx4G-80TMzwC_bwZtAe1IrDF-2qs00xHAEeikVoRs:) Timeout during connect (likely firewall problem) My web server is (include version): IIS v10 The operating system my web server runs on is (include version): WIndows Server 2019 v1809 Build 17763.4010 My hosting provider, if applicable, is: Ionos 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): IIS The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): 1.24.0 ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [February 23, 2023, 7:46pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/2 "2023-02-23T19:46:37Z")
Hi @Jon_AK, and welcome to the LE community forum 🙂 I see: > [@Jon\_AK](#): > > `--standalone` and > [@Jon\_AK](#): > > IIS v10 Is your HTTP site available from the Internet? Also: > [@Jon\_AK](#): > > Timeout during connect (likely firewall problem) Is there a firewall blocking OR not forwarding correctly? ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [February 23, 2023, 7:53pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/3 "2023-02-23T19:53:57Z")
> [@Jon\_AK](#): > > 162.211.27.195 Is that the current IP? ---
**Author:** ![Jon\_AK](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@Jon\_AK](https://community.letsencrypt.org/u/Jon_AK)\ **Post date:** [February 23, 2023, 8:12pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/4 "2023-02-23T20:12:36Z")
That is the current IP. I also made sure that both inboud & outbound port 80 are open on the server. Port 80 is forwarded in the router to the IP address of the server. I followed the instructions to make sure that IIS was shutdown prior to running certbot so not sure exactly what may be in the way yet. I was also unaware of the limitation imposed upon cert registration failures & as a result of verifying my settings after each failure, my last attempt let me know that I had exceeded the this limit. Not sure if I can even continue now??? Jon Albright JCA Services LLC Soldotna, Alaska ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [February 23, 2023, 8:20pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/5 "2023-02-23T20:20:28Z")
I see no ports accessible ```plaintext $ nmap -Pn jcasvcs.com Starting Nmap 7.80 ( https://nmap.org ) at 2023-02-23 12:13 PST Nmap scan report for jcasvcs.com (162.211.27.195) Host is up. rDNS record for 162.211.27.195: 162-211-27-195.sol.spitwspots.net All 1000 scanned ports on jcasvcs.com (162.211.27.195) are filtered Nmap done: 1 IP address (1 host up) scanned in 201.38 seconds ``` ```plaintext $ nmap -Pn odoo.jcasvcs.com Starting Nmap 7.80 ( https://nmap.org ) at 2023-02-23 20:13 UTC Nmap scan report for odoo.jcasvcs.com (162.211.27.195) Host is up. rDNS record for 162.211.27.195: 162-211-27-195.sol.spitwspots.net All 1000 scanned ports on odoo.jcasvcs.com (162.211.27.195) are filtered Nmap done: 1 IP address (1 host up) scanned in 201.83 seconds ``` ---
**Author:** ![Jon\_AK](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@Jon\_AK](https://community.letsencrypt.org/u/Jon_AK)\ **Post date:** [February 23, 2023, 8:27pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/6 "2023-02-23T20:27:32Z")
hmmm, I don't understand that. before I began anything today, i logged onto the website that is attached to this server but I just checked it and you're correct, it shows closed. ---
**Author:** ![Jon\_AK](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@Jon\_AK](https://community.letsencrypt.org/u/Jon_AK)\ **Post date:** [February 23, 2023, 8:30pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/7 "2023-02-23T20:30:58Z")
sorry about that, the website is not ready to open until i get the ssl cert so i closed it after trying to get the cert via certbot. it shows as open now ---
**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\ **Post date:** [February 23, 2023, 8:31pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/8 "2023-02-23T20:31:15Z")
Once you sort out that you might want to consider a different ACME client. Certbot does not easily integrate with IIS. You wouldn't use certbot standalone with a running server of any kind. And, certbot does not create certs in form Windows/IIS likes it so you need to convert and do stuff manually. Consider using Certify the Web (a gui) or another Windows focused ACME client > **[ACME Client Implementations - Let's Encrypt](https://letsencrypt.org/docs/client-options/#clients-windows-/-iis)** > > Last updated: Jun 29, 2022 | See all Documentation Let’s Encrypt uses the ACME protocol to verify that you control a given domain name and to issue you a certificate. To get a Let’s Encrypt certificate, you’ll need to choose a piece... ---
**Author:** ![jvanasco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jvanasco/32/55900_2.png) [@jvanasco](https://community.letsencrypt.org/u/jvanasco)\ **Post date:** [February 23, 2023, 9:27pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/9 "2023-02-23T21:27:06Z")
> [@MikeMcQ](#): > > Consider using Certify the Web (a gui) or another Windows focused ACME client > > [ACME Client Implementations - Let's Encrypt](https://letsencrypt.org/docs/client-options/#clients-windows-/-iis) Certify the Web is your best option. The author is a frequent contributor here, so you are more likely to get expert support if you run into issues. WinAcme, PoshAcme and Certes tend to be popular here and have some amount of support as well - but Certify is the best option in terms of robustness, ease of use and support. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [March 25, 2023, 9:27pm UTC](https://community.letsencrypt.org/t/certbot-timeout/193314/10 "2023-03-25T21:27:28Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.