# Urn:ietf:params:acme:error:connection (one more) **URL:** \ **Category:** Help\ **Created:** [June 18, 2020, 6:59am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144 "2020-06-18T06:59:38Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![alf2006x](https://avatars.discourse-cdn.com/v4/letter/a/e480ec/32.png) [@alf2006x](https://community.letsencrypt.org/u/alf2006x)\ **Post date:** [June 18, 2020, 6:59am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/1 "2020-06-18T06:59:38Z")
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. [https://crt.sh/?q=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: [api.bolerotour.ru](http://api.bolerotour.ru) I ran this command: wacs.exe Software version 2.1.8.838 (RELEASE, PLUGGABLE) Running with administrator credentials It produced this output: Target generated using plugin IIS: [api.bolerotour.ru](http://api.bolerotour.ru) Authorize identifier [api.bolerotour.ru](http://api.bolerotour.ru) Authorizing [api.bolerotour.ru](http://api.bolerotour.ru) using http-01 validation (SelfHosting) { “type”: “urn:ietf:params:acme:error:connection”, “detail”: “Fetching [http://api.bolerotour.ru/.well-known/acme-challenge/MOEeSs](http://api.bolerotour.ru/.well-known/acme-challenge/MOEeSs) UlbXSABNuShgnv-KTF6WD1v\_ozUaGi08d3rPQ: Timeout during connect (likely firewall p roblem)”, “status”: 400 } Authorization result: invalid My web server is (include version): 8.5 The operating system my web server runs on is (include version): Windows Server 2012R2 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 don’t know 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): wacs.exe 2.1.8.838 ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [June 18, 2020, 7:07am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/2 "2020-06-18T07:07:49Z")
Hi @alf2006x there > [@alf2006x](#): > > “type”: “urn:ietf:params:acme:error:connection”, > “detail”: “Fetching [http://api.bolerotour.ru/.well-known/acme-challenge/MOEeSs](http://api.bolerotour.ru/.well-known/acme-challenge/MOEeSs) > UlbXSABNuShgnv-KTF6WD1v\_ozUaGi08d3rPQ: Timeout during connect (likely firewall p > roblem)”, is your job. A working port 80 is required, not a timeout. ---
**Author:** ![alf2006x](https://avatars.discourse-cdn.com/v4/letter/a/e480ec/32.png) [@alf2006x](https://community.letsencrypt.org/u/alf2006x)\ **Post date:** [June 18, 2020, 7:27am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/3 "2020-06-18T07:27:29Z")
Unfortunately, our major-sysadmin politics is to prevent broadcasting opening 80 port. Is there any other way to make a new LE sertificate without opening this port? And of course to easely renew it in the future. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [June 18, 2020, 8:02am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/4 "2020-06-18T08:02:24Z")
That's > [@alf2006x](#): > > our major-sysadmin politics is to prevent broadcasting opening 80 port a wrong policy, change that. Read > **[Best Practice - Keep Port 80 Open - Let's Encrypt](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... Or switch to dns validation. ---
**Author:** ![alf2006x](https://avatars.discourse-cdn.com/v4/letter/a/e480ec/32.png) [@alf2006x](https://community.letsencrypt.org/u/alf2006x)\ **Post date:** [June 18, 2020, 8:34am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/5 "2020-06-18T08:34:36Z")
Thanks a lot. I will try ) And there is one more trouble. It looks like some times ago my renewing of LE was broken. This is about my other site: arfa.travel And this is other host with opened 80 port. It was always everything good but now I receive letter that sertificate will gone soon. What could have happened? My wacs.exe writes this: [INFO] A simple Windows ACMEv2 client (WACS) [INFO] Software version 2.0.9.386 (RELEASE) [INFO] IIS version 8.5 [INFO] Please report issues at [https://github.com/PKISharp/win-acme](https://github.com/PKISharp/win-acme) [INFO] Renewing certificate for [Manual] arfa.travel [INFO] Authorize identifier: arfa.travel [INFO] Authorizing arfa.travel using http-01 validation (SelfHosting) [EROR] Authorization timed out [EROR] Renewal for [Manual] arfa.travel failed, will retry on next run ---
**Author:** ![alf2006x](https://avatars.discourse-cdn.com/v4/letter/a/e480ec/32.png) [@alf2006x](https://community.letsencrypt.org/u/alf2006x)\ **Post date:** [July 3, 2020, 2:12pm UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/6 "2020-07-03T14:12:05Z")
Still dont work. I’m very disappoint. It looks everything OK with my site on 80 port. And win-acme doing everything without any error. But my [https://api.bolerotour.ru](https://api.bolerotour.ru) doesn’t want to work correct. It returns ERR\_CONNECTION\_TIMED\_OUT. Both 80 and 443 ports are opened. When my carma was broken? ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [July 3, 2020, 2:16pm UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/7 "2020-07-03T14:16:03Z")
> [@alf2006x](#): > > Fetching [http://api.bolerotour.ru/.well-known/acme-challenge/MOEeSsUlbXSABNuShgnv-KTF6WD1v\_ozUaGi08d3rPQ:](http://api.bolerotour.ru/.well-known/acme-challenge/MOEeSsUlbXSABNuShgnv-KTF6WD1v_ozUaGi08d3rPQ:) Timeout during connect (likely firewall p > roblem)”, Now I can open your file. 404, but that's a correct answer. Looks like you have a firewall with regional blockings, so Letsencrypt is blocked. ---
**Author:** ![alf2006x](https://avatars.discourse-cdn.com/v4/letter/a/e480ec/32.png) [@alf2006x](https://community.letsencrypt.org/u/alf2006x)\ **Post date:** [July 7, 2020, 8:46am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/8 "2020-07-07T08:46:25Z")
It looks like we’ve done it. Works great. Thanx a lot! ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [July 7, 2020, 8:56am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/9 "2020-07-07T08:56:24Z")
> [@alf2006x](#): > > It looks like we’ve done it. Yep, now my browser has a new Letsencrypt certificate 👍 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [August 6, 2020, 8:56am UTC](https://community.letsencrypt.org/t/urnparamserror-connection-one-more/126144/10 "2020-08-06T08:56:24Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.