# Suddenly Timeout during connect (likely firewall problem) for www subdomain **URL:** \ **Category:** Help\ **Created:** [April 21, 2022, 6:49am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267 "2022-04-21T06:49:33Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mserra](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mserra](https://community.letsencrypt.org/u/mserra)\ **Post date:** [April 21, 2022, 6:49am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/1 "2022-04-21T06:49:33Z")
Hi, I have a really strange problem. This issue Suddenly appeared last 24 or 48 hours (before all was runing well for the last 18 months!) My domain is: [laresidencia.net](http://laresidencia.net) I ran this command: plesk bin extension --exec letsencrypt cli.php -d [laresidencia.net](http://laresidencia.net) -d [www.laresidencia.net](http://www.laresidencia.net) -m me@domain.tld It produced this output: ```nohighlight # plesk bin extension --exec letsencrypt cli.php -d laresidencia.net -m me@domain.tld # plesk bin extension --exec letsencrypt cli.php -d laresidencia.net -d www.laresidencia.net -m me@domain.tld [2022-04-21 08:45:38.541] 3877622:6260fd928408e ERR [extension/letsencrypt] The execution of cli.php has failed with the following message: [2022-04-21 08:45:38.528] 3877624:6260fd82a7081 ERR [extension/letsencrypt] Domain validation failed for www.laresidencia.net: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/100274279387. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: Fetching http://www.laresidencia.net/.well-known/acme-challenge/mENo2ZDDnaXDr0qRD3rk7ZYB2xQEGNsiCDPo4Tyj9AQ: Timeout during connect (likely firewall problem) [2022-04-21 08:45:38.531] 3877624:6260fd82a7081 ERR [extension/letsencrypt] Domain validation failed: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/100274279387. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: Fetching http://www.laresidencia.net/.well-known/acme-challenge/mENo2ZDDnaXDr0qRD3rk7ZYB2xQEGNsiCDPo4Tyj9AQ: Timeout during connect (likely firewall problem) Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/100274279387. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: Fetching http://www.laresidencia.net/.well-known/acme-challenge/mENo2ZDDnaXDr0qRD3rk7ZYB2xQEGNsiCDPo4Tyj9AQ: Timeout during connect (likely firewall problem) The execution of cli.php has failed with the following message: [2022-04-21 08:45:38.528] 3877624:6260fd82a7081 ERR [extension/letsencrypt] Domain validation failed for www.laresidencia.net: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/100274279387. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: Fetching http://www.laresidencia.net/.well-known/acme-challenge/mENo2ZDDnaXDr0qRD3rk7ZYB2xQEGNsiCDPo4Tyj9AQ: Timeout during connect (likely firewall problem) [2022-04-21 08:45:38.531] 3877624:6260fd82a7081 ERR [extension/letsencrypt] Domain validation failed: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/100274279387. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: Fetching http://www.laresidencia.net/.well-known/acme-challenge/mENo2ZDDnaXDr0qRD3rk7ZYB2xQEGNsiCDPo4Tyj9AQ: Timeout during connect (likely firewall problem) Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/100274279387. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: Fetching http://www.laresidencia.net/.well-known/acme-challenge/mENo2ZDDnaXDr0qRD3rk7ZYB2xQEGNsiCDPo4Tyj9AQ: Timeout during connect (likely firewall problem) exit status 1 ``` As you can see, the first command without de www subdomain, worked! but when I add the www failt. My web server is: Apache 2.4.41 The operating system my web server runs on is (include version): ubuntu 20.04 My hosting provider, if applicable, is: IONOS I can login to a root shell on my machine: yes I'm using a control panel to manage my site: Plesk obsidian The version of my client is: I'm using the latest plesk SSL IT! extension Nmap port 80 and 443 tests (tested from another machine, not the hosting server)... ```nohighlight # nmap -P 80 laresidencia.net Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-21 08:27 CEST Nmap done: 2 IP addresses (0 hosts up) scanned in 2.17 seconds root@oismarclinux:/home/m_serra# nmap -p 80 laresidencia.net Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-21 08:27 CEST Nmap scan report for laresidencia.net (212.227.149.7) Host is up (0.020s latency). rDNS record for 212.227.149.7: webolot.com PORT STATE SERVICE 80/tcp open http Nmap done: 1 IP address (1 host up) scanned in 0.28 seconds # nmap -p 80 www.laresidencia.net Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-21 08:27 CEST Nmap scan report for www.laresidencia.net (212.227.149.7) Host is up (0.020s latency). rDNS record for 212.227.149.7: webolot.com PORT STATE SERVICE 80/tcp open http Nmap done: 1 IP address (1 host up) scanned in 0.30 seconds # nmap -p 443 www.laresidencia.net Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-21 08:27 CEST Nmap scan report for www.laresidencia.net (212.227.149.7) Host is up (0.020s latency). rDNS record for 212.227.149.7: webolot.com PORT STATE SERVICE 443/tcp open https Nmap done: 1 IP address (1 host up) scanned in 0.26 seconds # nmap -p 443 laresidencia.net Starting Nmap 7.80 ( https://nmap.org ) at 2022-04-21 08:27 CEST Nmap scan report for laresidencia.net (212.227.149.7) Host is up (0.020s latency). rDNS record for 212.227.149.7: webolot.com PORT STATE SERVICE 443/tcp open https ``` DNS test (tested from another machine, not the hosting server) ... ```nohighlight # dig +short NS laresidencia.net ns1045.ui-dns.de. ns1045.ui-dns.com. ns1045.ui-dns.biz. ns1045.ui-dns.org. # dig +short www.laresidencia.net 212.227.149.7 # dig +short laresidencia.net 212.227.149.7 ``` The same happens with some other domains, for example: ecarta.cat and delitgastronomic.cat, ... This server has a UFW (disabled now) and a Firewall at hosting provider level (IONOS) with the ports 80 and 443 open and unfiltered. I tried to change the www DNS record from A to CNAME, with the same results. I tried to change the www DNS record from www to \*, with the same results. I'm really lost! ---
**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:** [April 22, 2022, 2:00am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/2 "2022-04-22T02:00:52Z")
Looks like there is some type of GeoLocation blocking going on: See: [Let's Debug (letsdebug.net)](https://letsdebug.net/laresidencia.net/1005138) ---
**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:** [April 22, 2022, 2:33am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/3 "2022-04-22T02:33:46Z")
@rg305 I see your Let's Debug test failing but it is working now. I see they issued a cert with both names in it. But, oddly, much earlier today. By my calcs about 2H after their initial post. Hmmm [https://tools.letsdebug.net/cert-search?m=domain&q=laresidencia.net&d=168](https://tools.letsdebug.net/cert-search?m=domain&q=laresidencia.net&d=168) ---
**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:** [April 22, 2022, 2:37am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/4 "2022-04-22T02:37:17Z")
Maybe it only blocks some of the IPs some of the times - LOL ---
**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\ **Post date:** [April 22, 2022, 4:32am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/5 "2022-04-22T04:32:00Z")
I am getting good results now: Cert is good till Wed, 20 Jul 2022 05:57:14 GMT Thought Id mention it. ---
**Author:** ![mserra](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mserra](https://community.letsencrypt.org/u/mserra)\ **Post date:** [April 22, 2022, 6:52am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/6 "2022-04-22T06:52:11Z")
Thank's for all your replies. > I see they issued a cert with both names in it. But, oddly, much earlier today. By my calcs about 2H after their initial post. Hmmm and > I am getting good results now: > Cert is good till Wed, 20 Jul 2022 05:57:14 GMT > Thought Id mention it. That's true. After a few tries (without change anything) the certificate for www has renewed correctly. Why?! I don't know. Today, a new domain has the same problem: [aniolmangas.com](http://aniolmangas.com) As you can see, the domain succefully renewed but no www. [crt.sh | aniolmangas.com](https://crt.sh/?q=aniolmangas.com) For your information, I had another server with the same setup and 2 days ago we have the same problem with [manxaindustrial.com](http://manxaindustrial.com). But like [laresidencia.net](http://laresidencia.net), after a few retries we succefully renewed for www. What can I do? Thank's! ---
**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:** [April 22, 2022, 2:37pm UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/7 "2022-04-22T14:37:54Z")
Your explanation is very helpful but is unusual. I do not know Plesk very well. Does it auto-configure your Apache server too or do you configure that by hand? Have you tried using the Plesk interactive panel to get the certs? Does it fail the same way as your command line method? > **[How to install a Let's Encrypt SSL certificate for a domain in Plesk?](https://support.plesk.com/hc/en-us/articles/213946825-How-to-install-a-Let-s-Encrypt-SSL-certificate-for-a-domain-in-Plesk-)** > > Applicable to: > > Plesk for Linux > Plesk for Windows > > > Question > How to install a Let's Encrypt SSL certificate for a domain in Plesk? > Answer > > Note: Before securing a domain with a Let's Encrypt certif... ---
**Author:** ![mserra](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mserra](https://community.letsencrypt.org/u/mserra)\ **Post date:** [April 22, 2022, 6:03pm UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/8 "2022-04-22T18:03:55Z")
Thank's for your answer Mike, Before try with the command line, I was already tried with the plesk panel (as usual) with the same result... ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/a/a/aaa0fe9a9b84ddc1a2a416d3226446f3edd1f8d0.png) The base domain cert is renewed ok but no the www subdomain Before post here, I searched a lot in plesk forums and KB, some people said the (similar) problem goes unchecking the **Redirect from http to https** option, but no in my case. ---
**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:** [April 22, 2022, 6:23pm UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/9 "2022-04-22T18:23:27Z")
> [@MikeMcQ](#): > > Does Plesk auto-configure your Apache server too or do you configure that by hand? We can look at your Apache conf but if Plesk manages that it would not help to adjust it manually. As a test, did you try getting a cert for just the www domain. I am curious if it has to do with multiple domains in same cert (which is normally fine) or related to the www itself. In your IONOS setup is there any optional firewall / security settings that relate to "ddos" protection or "smart security"? Let's Encrypt will make several identical request from different places around the world so is sometimes confused for an attack and blocked by such a firewall. ---
**Author:** ![mserra](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mserra](https://community.letsencrypt.org/u/mserra)\ **Post date:** [April 25, 2022, 6:41am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/10 "2022-04-25T06:41:34Z")
Hi Mike, and thank's for answer. If I try to get a cert for just the www domain, I have the same result... ```nohighlight # plesk bin extension --exec letsencrypt cli.php -d www.candanes.com -m mserrafontfreda@gmail.com [2022-04-25 08:35:33.152] 315615:626641352515f ERR [extension/letsencrypt] The execution of cli.php has failed with the following message: [2022-04-25 08:35:33.139] 315617:6266412706cbc ERR [extension/letsencrypt] Domain validation failed for www.candanes.com: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/101866345467. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: 212.227.149.7: Fetching http://www.candanes.com/.well-known/acme-challenge/ew3A2sFXVQUNS2q9_btXOYI0JFAOXeC-708can5dZpw: Timeout during connect (likely firewall problem) [2022-04-25 08:35:33.141] 315617:6266412706cbc ERR [extension/letsencrypt] Domain validation failed: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/101866345467. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: 212.227.149.7: Fetching http://www.candanes.com/.well-known/acme-challenge/ew3A2sFXVQUNS2q9_btXOYI0JFAOXeC-708can5dZpw: Timeout during connect (likely firewall problem) Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/101866345467. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: 212.227.149.7: Fetching http://www.candanes.com/.well-known/acme-challenge/ew3A2sFXVQUNS2q9_btXOYI0JFAOXeC-708can5dZpw: Timeout during connect (likely firewall problem) The execution of cli.php has failed with the following message: [2022-04-25 08:35:33.139] 315617:6266412706cbc ERR [extension/letsencrypt] Domain validation failed for www.candanes.com: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/101866345467. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: 212.227.149.7: Fetching http://www.candanes.com/.well-known/acme-challenge/ew3A2sFXVQUNS2q9_btXOYI0JFAOXeC-708can5dZpw: Timeout during connect (likely firewall problem) [2022-04-25 08:35:33.141] 315617:6266412706cbc ERR [extension/letsencrypt] Domain validation failed: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/101866345467. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: 212.227.149.7: Fetching http://www.candanes.com/.well-known/acme-challenge/ew3A2sFXVQUNS2q9_btXOYI0JFAOXeC-708can5dZpw: Timeout during connect (likely firewall problem) Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/101866345467. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail: 212.227.149.7: Fetching http://www.candanes.com/.well-known/acme-challenge/ew3A2sFXVQUNS2q9_btXOYI0JFAOXeC-708can5dZpw: Timeout during connect (likely firewall problem) exit status 1 ``` No, I think there is not an additional protection. If you need something from my server (apache config, logs, etc) tell me please. For your information, this weekend, four new domains have problems renewing the www subdomain ... [www.pirenaic.fr](http://www.pirenaic.fr/) [www.pirenaic.com](http://www.pirenaic.com/) [www.candanes.com](http://www.candanes.com/) [www.tiars.cat](http://www.tiars.cat/) ---
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [April 25, 2022, 7:35am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/11 "2022-04-25T07:35:29Z")
I cannot reproduce any of that from Italy. There probably is a firewall you have yet to discover. If it's not yours it's probably your ISP's. ---
**Author:** ![Wolfix](https://avatars.discourse-cdn.com/v4/letter/w/8edcca/32.png) [@Wolfix](https://community.letsencrypt.org/u/Wolfix)\ **Post date:** [April 25, 2022, 9:25am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/12 "2022-04-25T09:25:30Z")
Hello, We are having the same type of issue since the last thursday and our ISP is the same: Arsys (IONOS)(Spain). The error is: "Timeout during connect (likely firewall problem) for www subdomain" We can renew the raw domain but no the "www.". Ports 80 and 443 are accesible from inside/outside server and we don't have ipv6 records. When the error ocurs, we can access to the "Fetching" error url of our domains quickly and without any problem from inside and outside server. We tried access to those urls with the typical pages that try access to a url from different countries and we didn't see problems either. The domain access via [https://letsdebug.net/](https://letsdebug.net/) were ok in all cases. We have 8 servers with Windows Server 2016 + Plesk 18.0.43 + Lets Encrypt 3.0.0-785 and we are having the same issue in all servers since the same day. We contacted with the ISP and they are investigating it because it could be some type of ip block or some problem related at ISP level. ---
**Author:** ![mserra](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mserra](https://community.letsencrypt.org/u/mserra)\ **Post date:** [April 25, 2022, 9:48am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/13 "2022-04-25T09:48:17Z")
Thank's for your answer Wolfix, (_mal de muchos, consuelo de tontos_ 😅) If you have news about the issue, can you update this post please? Can I do something to help? ---
**Author:** ![Wolfix](https://avatars.discourse-cdn.com/v4/letter/w/8edcca/32.png) [@Wolfix](https://community.letsencrypt.org/u/Wolfix)\ **Post date:** [April 25, 2022, 10:14am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/14 "2022-04-25T10:14:34Z")
Yes, I will post any news. 🙂 I don't know if you reported it to IONOS but them maybe could have more clues with our two issues over the table. Thank you! 😀 ---
**Author:** ![pepelucai](https://avatars.discourse-cdn.com/v4/letter/p/b38774/32.png) [@pepelucai](https://community.letsencrypt.org/u/pepelucai)\ **Post date:** [April 25, 2022, 5:54pm UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/15 "2022-04-25T17:54:42Z")
Hi! I'm having the same problem (exactly the same problem) with ARSYS. I reported a ticket and waiting for anwser. ---
**Author:** ![mserra](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mserra](https://community.letsencrypt.org/u/mserra)\ **Post date:** [April 25, 2022, 8:17pm UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/16 "2022-04-25T20:17:01Z")
Thanks pepelucai, A few years ago, Ionos bought Arsys: [La compañía alemana 1&1 compra la española Arsys por 140 millones | Tecnología | EL PAÍS](https://elpais.com/tecnologia/2013/08/19/actualidad/1376901994_696934.html) Ionos (1and1) and arsys are the same ---
**Author:** ![pepelucai](https://avatars.discourse-cdn.com/v4/letter/p/b38774/32.png) [@pepelucai](https://community.letsencrypt.org/u/pepelucai)\ **Post date:** [April 26, 2022, 3:49pm UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/17 "2022-04-26T15:49:13Z")
Yes. Same company. They answered that there are more clients with same problem and asked me for result of command tcptraceroute. No more answers for now. ---
**Author:** ![mserra](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mserra](https://community.letsencrypt.org/u/mserra)\ **Post date:** [April 27, 2022, 7:17am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/18 "2022-04-27T07:17:51Z")
I don't know if this information will be relevant for the gurus in this forum, but, I try ... After insisting with IONOS Spain, I have been asked for the result of executing the command mtr And there is something strange with some of the let's encrypt servers. I have two servers. And the mtr result is different in each server. Look... Server 1: ```nohighlight cat acme-staging.api.letsencrypt.org.txt Start: 2022-04-27T08:54:35+0200 HOST: distracted-albattani.82-223 Loss% Snt Last Avg Best Wrst StDev 1.|-- distracted-albattani.82-2 0.0% 10 0.0 0.0 0.0 0.1 0.0 cat acme-staging-v02.api.letsencrypt.org.txt Start: 2022-04-27T08:49:43+0200 HOST: distracted-albattani.82-223 Loss% Snt Last Avg Best Wrst StDev 1.|-- 10.255.255.2 0.0% 10 0.2 0.2 0.1 0.3 0.1 2.|-- 82.223.41.138 0.0% 10 0.5 0.6 0.4 0.8 0.1 3.|-- ae-6.bb-a.mad2.mad.es.net 0.0% 10 8.2 8.2 7.9 8.4 0.2 4.|-- cloudflare.alta.espanix.n 0.0% 10 8.8 15.5 8.5 39.6 11.3 5.|-- 172.70.58.2 0.0% 10 21.1 10.3 8.2 21.1 4.1 6.|-- 172.65.46.172 0.0% 10 8.3 8.2 8.1 8.3 0.1 cat acme-v01.api.letsencrypt.org.txt Start: 2022-04-27T08:48:58+0200 HOST: distracted-albattani.82-223 Loss% Snt Last Avg Best Wrst StDev 1.|-- distracted-albattani.82-2 0.0% 10 0.0 0.0 0.0 0.1 0.0 cat acme-v02.api.letsencrypt.org.txt Start: 2022-04-27T08:48:34+0200 HOST: distracted-albattani.82-223 Loss% Snt Last Avg Best Wrst StDev 1.|-- 10.255.255.2 0.0% 10 0.3 0.2 0.1 0.5 0.1 2.|-- 82.223.41.137 0.0% 10 0.5 0.6 0.5 0.7 0.1 3.|-- ae-6.bb-b.epx.mad.es.net. 0.0% 10 7.5 7.5 7.0 8.1 0.3 4.|-- ae-8.bb-a.mad2.mad.es.one 0.0% 10 7.1 7.3 7.1 7.6 0.2 5.|-- cloudflare.alta.espanix.n 0.0% 10 7.7 13.1 7.7 32.4 9.2 6.|-- 188.114.108.7 0.0% 10 7.5 7.7 7.5 7.8 0.1 7.|-- 172.65.32.248 0.0% 10 7.0 7.1 6.9 7.3 0.2 ``` Server 2 ```nohighlight $ cat acme-staging.api.letsencrypt.org.txt Start: 2022-04-27T08:45:25+0200 HOST: webolot.com Loss% Snt Last Avg Best Wrst StDev 1.|-- 10.255.255.2 0.0% 10 0.2 0.1 0.1 0.3 0.1 2.|-- 82.223.41.138 0.0% 10 0.4 0.5 0.4 0.7 0.1 3.|-- ae-6.bb-a.mad2.mad.es.net 0.0% 10 8.1 8.0 7.9 8.1 0.1 4.|-- mad-b3-link.ip.twelve99.n 70.0% 10 8.2 8.2 8.0 8.3 0.1 5.|-- mad-b2-link.ip.twelve99.n 0.0% 10 8.4 8.5 8.3 8.8 0.2 6.|-- prs-bb2-link.ip.twelve99. 0.0% 10 106.3 106.0 105.9 106.3 0.1 7.|-- rest-bb1-link.ip.twelve99 0.0% 10 105.8 106.6 105.8 111.8 1.9 8.|-- ash-b2-link.ip.twelve99.n 0.0% 10 105.9 106.0 105.8 106.3 0.1 9.|-- vadata-ic333119-ash-b2.ip 0.0% 10 106.5 110.2 105.6 127.9 6.9 10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 12.|-- 52.93.28.78 0.0% 10 120.9 121.1 118.4 135.3 5.2 13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 $ cat acme-staging-v02.api.letsencrypt.org.txt Start: 2022-04-27T08:46:01+0200 HOST: webolot.com Loss% Snt Last Avg Best Wrst StDev 1.|-- 10.255.255.2 0.0% 10 0.1 0.1 0.1 0.2 0.0 2.|-- 82.223.41.137 0.0% 10 0.6 0.6 0.4 1.3 0.3 3.|-- ae-6.bb-b.epx.mad.es.net. 0.0% 10 7.1 7.3 6.9 7.8 0.3 4.|-- ae-8.bb-a.mad2.mad.es.one 0.0% 10 7.0 7.1 7.0 7.2 0.1 5.|-- cloudflare.alta.espanix.n 0.0% 10 14.9 10.9 7.5 23.6 5.5 6.|-- 172.70.58.2 0.0% 10 7.8 7.8 7.1 9.7 0.7 7.|-- 172.65.46.172 0.0% 10 7.1 7.1 7.0 7.1 0.0 $ cat acme-v01.api.letsencrypt.org.txt Start: 2022-04-27T08:44:43+0200 HOST: webolot.com Loss% Snt Last Avg Best Wrst StDev 1.|-- 10.255.255.2 0.0% 10 0.1 0.1 0.1 0.1 0.0 2.|-- 82.223.41.138 0.0% 10 0.6 0.5 0.4 0.6 0.1 3.|-- ae-6.bb-a.mad2.mad.es.net 0.0% 10 8.0 8.0 7.8 8.1 0.1 4.|-- mad-b3-link.ip.twelve99.n 70.0% 10 8.5 8.4 8.2 8.5 0.2 5.|-- mad-b2-link.ip.twelve99.n 0.0% 10 8.7 8.7 8.4 9.7 0.4 6.|-- prs-bb2-link.ip.twelve99. 0.0% 10 105.8 106.0 105.8 106.2 0.1 7.|-- rest-bb1-link.ip.twelve99 0.0% 10 106.3 106.1 106.0 106.3 0.1 8.|-- ash-b2-link.ip.twelve99.n 0.0% 10 106.0 106.0 105.7 106.2 0.1 9.|-- vadata-ic333119-ash-b2.ip 0.0% 10 105.8 106.8 105.7 111.4 1.8 10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 12.|-- 52.93.28.78 0.0% 10 118.8 119.4 118.4 125.9 2.3 13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 $ cat acme-v02.api.letsencrypt.org.txt Start: 2022-04-27T08:45:03+0200 HOST: webolot.com Loss% Snt Last Avg Best Wrst StDev 1.|-- 10.255.255.2 0.0% 10 0.1 0.1 0.1 0.1 0.0 2.|-- 82.223.41.138 0.0% 10 0.5 0.5 0.4 0.7 0.1 3.|-- ae-6.bb-b.epx.mad.es.net. 0.0% 10 6.6 6.4 6.2 6.8 0.2 4.|-- ae-8.bb-a.mad2.mad.es.one 0.0% 10 7.0 7.1 6.9 7.3 0.1 5.|-- cloudflare.alta.espanix.n 0.0% 10 7.9 10.2 7.5 16.8 3.3 6.|-- 172.70.60.2 0.0% 10 7.4 7.9 7.1 9.6 0.7 7.|-- 172.65.32.248 0.0% 10 7.1 7.1 7.0 7.2 0.1 ``` ---
**Author:** ![FEJIDIF](https://avatars.discourse-cdn.com/v4/letter/f/8e8cbc/32.png) [@FEJIDIF](https://community.letsencrypt.org/u/FEJIDIF)\ **Post date:** [April 27, 2022, 7:17am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/19 "2022-04-27T07:17:59Z")
Same issue over here. Identical environment: IONOS, Plesk Obsidian, SSL It! extension, spanish client and partially renewed certificate (main domain renewed and www subdomain failed). It's not a final solution, but I finally found a partial one to get the renewal while this issue is completely solved. From Plesk panel: 1. Go to the subscription. 2. SSL/TLS Certificates. 3. Deactivate the "Redirect from http to https" option. 4. Reissue the certificate. 5. Activate the http to https redirect. ![Redirect](https://global.discourse-cdn.com/letsencrypt/original/3X/4/f/4f588f8f434d835270c123428b134026cc7cfd07.jpeg) ---
**Author:** ![mserra](https://avatars.discourse-cdn.com/v4/letter/m/ed8c4c/32.png) [@mserra](https://community.letsencrypt.org/u/mserra)\ **Post date:** [April 27, 2022, 7:19am UTC](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267/20 "2022-04-27T07:19:55Z")
Thank's for your message FEJIDIF, but don't work for me 😭 [Next page](https://community.letsencrypt.org/t/suddenly-timeout-during-connect-likely-firewall-problem-for-www-subdomain/176267.md?page=2)