# Timeout during connect

**URL:** <https://community.letsencrypt.org/t/timeout-during-connect/234462>\
**Category:** Help\
**Created:** [March 1, 2025, 2:12pm UTC](https://community.letsencrypt.org/t/timeout-during-connect/234462 "2025-03-01T14:12:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafal](https://avatars.discourse-cdn.com/v4/letter/r/ac91a4/32.png) [@Rafal](https://community.letsencrypt.org/u/Rafal)\
**Post date:** [March 1, 2025, 2:12pm UTC](https://community.letsencrypt.org/t/timeout-during-connect/234462/1 "2025-03-01T14:12:24Z")

</div>

My domain is: gosocialmedia.pl

I ran this command: certbot certainly -d gosocialmedia.pl

It produced this output:  
During secondary validation: 91.236.87.76: Fetching [http://gosocialmedia.pl/.well-known/acme-challenge/](http://gosocialmedia.pl/.well-known/acme-challenge/)\<...\> Timeout during connect (likely firewall problem)

My web server is (include version): Apache 2.4.53

The operating system my web server runs on is (include version): Rocky Linux 9.2 (Blue Onyx)

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): 2.6.0

I've already checked:

1. ports 80,443 are open and accessible from internet
2. Wireshark shows that apache receives GET request for a challenge file from lets encrypt server and replies successfully with its content
3. I can access other test files from directory .well-known/acme-challenge using browser

What is the issue????

Regards,  
Rafał

---

<div class="post-metadata">

**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:** [March 1, 2025, 2:19pm UTC](https://community.letsencrypt.org/t/timeout-during-connect/234462/2 "2025-03-01T14:19:51Z")

</div>

Hi @Rafal,

Welcome to our community! 🙂

> [@Rafal](#):
>
> ports 80,443 are open and accessible from internet

From around the world [Permanent link to this check report](https://check-host.net/check-report/239dad6fkd64) shows HTTP not able to connect.

---

<div class="post-metadata">

**Author:** ![Rafal](https://avatars.discourse-cdn.com/v4/letter/r/ac91a4/32.png) [@Rafal](https://community.letsencrypt.org/u/Rafal)\
**Post date:** [March 1, 2025, 2:37pm UTC](https://community.letsencrypt.org/t/timeout-during-connect/234462/3 "2025-03-01T14:37:06Z")

</div>

Hi Bruce!

thanks for warm welcome! 🙂

This is strange, I've used browser connected to external mobile phone network and it works...it may be cached? I will double check it...

Best regards,  
Rafał

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [March 1, 2025, 4:51pm UTC](https://community.letsencrypt.org/t/timeout-during-connect/234462/4 "2025-03-01T16:51:03Z")

</div>

Or there is geoblocking going on.

---

<div class="post-metadata">

**Author:** ![Rafal](https://avatars.discourse-cdn.com/v4/letter/r/ac91a4/32.png) [@Rafal](https://community.letsencrypt.org/u/Rafal)\
**Post date:** [March 1, 2025, 7:25pm UTC](https://community.letsencrypt.org/t/timeout-during-connect/234462/5 "2025-03-01T19:25:08Z")

</div>

Thank you all for your help! It turned out it was my firewall configuration issue, now it works perfectly! Issue closed!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [March 31, 2025, 7:25pm UTC](https://community.letsencrypt.org/t/timeout-during-connect/234462/6 "2025-03-31T19:25:49Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
