Err_connection_timed_out

Hosting Support
1

Website URL

https://wholefrtworkday.great-site.net

Error Message

This site can’t be reached

wholefrtworkday.great-site.net took too long to respond.

Try:

ERR_CONNECTION_TIMED_OUT

Other Information

Working on WIFI and my other ISPs
Converge - Working both WIFI and LAN
Starlink - Working both WIFI and LAN
PLDT - Not working both WIFI and LAN

2

That would indicate an issue on your end or with the ISP. What happens if you try to access the base domain great-site.net with that same provider?

5 Likes
3

Same error.

This site can’t be reached

great-site.net took too long to respond.

Try:

ERR_CONNECTION_TIMED_OUT

4

Okay, that means that most likely your ISP or DNS provider is blocking the entire domain on their end. It may also be because of an antivirus or security software blocking the connection. Can you please try running a trace route on the domain from that connection? It’s expected to terminate anyway because InfinityFree’s servers block ping requests, but in this instance it will show us where the connection is being broken.

6 Likes
5

I have a strong feeling this is probably a DNS issue. Are you checking the site with default ISP-supplied DNS configuration? PLDT’s DNS have issues accessing some sites (as reported in other forums). If you have admin privileges to your ISP ONU/HGU/router try modifying the DNS servers to 1.1.1.1 or 8.8.8.8 or any refutable public DNS. If no admin privileges you can change the DNS right from your device, try looking for Networking/Settings or equivalent. I can access your site without problem.

2 Likes
6

I still get the same error.

Tried using VPN and it works, it was working fine a week ago.
I wanted all the users/visitors of the page access it without needing to use VPN.
Any other work around?

7

I ran a traceroute to wholefrtworkday.great-site.net and it resolves to 185.27.134.123. The trace leaves PLDT’s network and reaches GTT in London, but then all requests time out. On PLDT, the site always returns ERR_CONNECTION_TIMED_OUT, but it works fine on other ISPs. This suggests a routing or filtering issue on PLDT’s side.

Could you please confirm if InfinityFree’s IP range 185.27.134.0/24 is currently reachable from PLDT?

8

No because I don’t have PLDT. Could you please show me a copy/paste or screen capture of the traceroute in question? It actually doesn’t sound unlike a working one, but I want to be sure.

There have been cases where certain IP addresses or IP ranges will be temporarily blocked on the side of InfinityFree’s provider because of cyberattack traffic, but only Admin would be able to check that for sure.

5 Likes
9

I had it checked, and it appears that your IP address was blocked on our network. That block has now been removed.

We automatically monitor our network for suspicious and potentially abusive traffic, and automatically block IP addresses that show unusual traffic. This is mainly done to block things like (D)DoS attacks.

But like anyone or anything that makes decisions, it can make mistakes and accidentally block legitimate IP addresses. This is usually caused by abnormal traffic, like running website scanners or severely malfunctioning website code.

8 Likes
10

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