# Yet another "Timeout" while verifying via HTTP **URL:** \ **Category:** Help\ **Created:** [June 11, 2021, 6:37pm UTC](https://community.letsencrypt.org/t/yet-another-timeout-while-verifying-via-http/153624 "2021-06-11T18:37:23Z")\ **Posts on this page:** 1\ **Showing post:** 17
**Author:** ![Cohote](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cohote/32/50515_2.png) [@Cohote](https://community.letsencrypt.org/u/Cohote)\ **Post date:** [June 11, 2021, 8:40pm UTC](https://community.letsencrypt.org/t/yet-another-timeout-while-verifying-via-http/153624/17 "2021-06-11T20:40:58Z")
> [@petercooperjr](#): > > he only thing I noticed, though I don't know if it's actually going to send you on a wild goose chase, is that the IP resolves to `66.151.242.26` for me, and that IP seems to be from a block that has bad IRR information. > > [66.151.242.0/24 - bgp.he.net](https://bgp.he.net/net/66.151.242.0/24) > > The announcement of the `66.151.242.0/24` block is marked red with a message of "IRR Invalid - Origin Mismatch". I know only a minimal amount about BGP and how core Internet routing works, but I think that means that the IP block is being announced "wrong" or at least by an entity that hasn't properly proved that it owns the block. So my thinking is that routing to that IP from Let's Encrypt's servers might not be working right. Ooh, i will CERTAINLY look into that. **ESPECIALLY** after discovering this. After adjusting logging settings, my last attempt (via le64, not letsdebug), I see THIS: ```nohighlight 2021-06-11 20:31:08 srvr 66.151.242.26 GET /.well-known/acme-challenge/fuzQt3sxAaeoxiTF-MRmV25lZCQq6Vau74ScMJyGDb4 - 80 - 3.143.223.150 HTTP/1.1 Mozilla/5.0+(compatible;+Let's+Encrypt+validation+server;++https://www.letsencrypt.org) - 200 0 0 527 270 22 2021-06-11 20:31:08 srvr 66.151.242.26 GET /.well-known/acme-challenge/fuzQt3sxAaeoxiTF-MRmV25lZCQq6Vau74ScMJyGDb4 - 80 - 3.67.34.92 HTTP/1.1 Mozilla/5.0+(compatible;+Let's+Encrypt+validation+server;++https://www.letsencrypt.org) - 200 0 0 527 270 102 2021-06-11 20:31:18 srvr 66.151.242.26 GET /.well-known/acme-challenge/fuzQt3sxAaeoxiTF-MRmV25lZCQq6Vau74ScMJyGDb4 - 80 - 18.236.228.243 HTTP/1.1 Mozilla/5.0+(compatible;+Let's+Encrypt+validation+server;++https://www.letsencrypt.org) - 200 0 0 527 270 51 ``` Requests came in, and IIS returned a 200, the file was served properly. However, LE still reported: ```nohighlight 2021/06/11 16:31:19 Domain verification results for 'www.tsqmadness.com': error. Fetching http://www.tsqmadness.com/.well-known/acme-challenge/fuzQt3sxAaeoxiTF-MRmV25lZCQq6Vau74ScMJyGDb4: Timeout during connect (likely firewall problem) ``` So.. I'm at a loss at the moment. ☹ In the past, I was using GNS validation, which worked fine, but my DNS server _ **apparently** _ has no API to create/remove TXT entries, which is why I started messin' wth this. 🙂 --- _[View the full topic](https://community.letsencrypt.org/t/yet-another-timeout-while-verifying-via-http/153624)._