# Some challenges have failed error **URL:** \ **Category:** Help\ **Created:** [March 27, 2025, 2:58pm UTC](https://community.letsencrypt.org/t/some-challenges-have-failed-error/235643 "2025-03-27T14:58:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![MilesGibson](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/milesgibson/32/86607_2.png) [@MilesGibson](https://community.letsencrypt.org/u/MilesGibson)\ **Post date:** [March 27, 2025, 2:58pm UTC](https://community.letsencrypt.org/t/some-challenges-have-failed-error/235643/1 "2025-03-27T14:58:45Z")
My domain is: [albertatriathlon.com](http://albertatriathlon.com) I ran this command: certbot certonly --webroot It produced this output: Saving debug log to C:\Certbot\log\letsencrypt.log Please enter the domain name(s) you would like on your certificate (comma and/or space separated) (Enter 'c' to cancel): [albertatriathlon.com](http://albertatriathlon.com) Requesting a certificate for [albertatriathlon.com](http://albertatriathlon.com) Input the webroot for [albertatriathlon.com](http://albertatriathlon.com): (Enter 'c' to cancel): \web2020\c$ Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems: Domain: [albertatriathlon.com](http://albertatriathlon.com) Type: connection Detail: 209.89.8.16: Fetching [http://albertatriathlon.com/.well-known/acme-challenge/J8Qtje8ScGCBoHgX-h4wEy3XLtH1Gy\_p7sZ1Nrs0xEE:](http://albertatriathlon.com/.well-known/acme-challenge/J8Qtje8ScGCBoHgX-h4wEy3XLtH1Gy_p7sZ1Nrs0xEE:) Timeout during connect (likely firewall problem) Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet. Some challenges have failed. Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details. C:\Users\Administrator\> * * * My web server is (include version): IIS 7.0 The operating system my web server runs on is (include version): Windows Server 2019 My hosting provider, if applicable, is: IIS 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.24.0 ---
**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:** [March 27, 2025, 3:15pm UTC](https://community.letsencrypt.org/t/some-challenges-have-failed-error/235643/2 "2025-03-27T15:15:13Z")
> [@MilesGibson](#): > > My web server is (include version): IIS 7.0 > [@MilesGibson](#): > > I ran this command: certbot certonly --webroot Looking at your certificate history it looks like this is the first time you are trying with Certbot. The EFF stopped supporting Windows with Certbot over a year ago. You should not use it for new setups. For IIS, Certify the Web is an excellent alternative. It is the first alternative mentioned in the EFF announcement: [https://certifytheweb.com/](https://certifytheweb.com/) [Certbot Discontinuing Windows Beta Support in 2024](https://community.letsencrypt.org/t/certbot-discontinuing-windows-beta-support-in-2024/208101) ---
**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\ **Post date:** [March 27, 2025, 3:19pm UTC](https://community.letsencrypt.org/t/some-challenges-have-failed-error/235643/3 "2025-03-27T15:19:32Z")
Yes, for IIS, you want to use [some other client](https://letsencrypt.org/docs/client-options/#clients-windows-/-iis), probably [Certify the Web](https://certifytheweb.com/) (if you're a GUI fan), [simple-acme](https://simple-acme.com/) (if you're a command line fan), or [Posh-Acme](https://github.com/rmbolger/Posh-ACME) (if you're a Powershell fan), though there are other choices too. As for the problem you're getting, it looks like your site is not responding on port 80: > **[Check website performance and response : Check host - online website monitoring](https://check-host.net/check-report/246876e9k33c)** > > Website checking for speed and availability with servers around the world: > website monitoring with useful tools, Check IP, Check website Make sure that your http site is working first, and then you should be able to get a certificate for https. > **[Best Practice - Keep Port 80 Open](https://letsencrypt.org/docs/allow-port-80/)** > > We occasionally get reports from people who have trouble using the HTTP-01 challenge type because they’ve firewalled off port 80 to their web server. Our recommendation is that all servers meant for general web use should offer both HTTP on port 80... ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [April 26, 2025, 3:20pm UTC](https://community.letsencrypt.org/t/some-challenges-have-failed-error/235643/4 "2025-04-26T15:20:20Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.