Longboardcruiserspt.free.nf in visible to me only with VPN connection

Website URL

https://longboardcruiserspt.free.nf/

Error Message

Server Not Found. Hmm. We’re having trouble finding that site.

We can’t connect to the server at longboardcruiserspt.free.nf

Other Information

I can access the Control Panel from within InfinityFree with no problem, just not the site itself. However if I use a VPN connection I can see the site. I’ve also tested https://downforeveryoneorjustme.com/longboardcruiserspt.free.nf?proto=https and it’s working fine, so I believe something is blocking just my WAN IP.

With VPN connection I can see/login on everything. Without VPN (just my regular internet connection) I can log into InfinityFree, but the site says “Server Not Found”.

NOTE: I have in total 3 accounts (sites), and the other 2 accounts I access them fine, it’s just this longboardcruiserspt.free.nf IP 185.27.134.57 that it seems to be blocking my WAN IP…

Can you please help me fix this issue?

Thanks in advance, and best regards

IF does not block any IPs/ISP.

It is something on your end that is blocking your access. It may be a program o your computer, router-level DNS configuration or firewall rules, or a block at the ISP level.

4 Likes

I’m using Linux.

Here’s the traceroute output from https://centralops.net/co/Traceroute?addr=longboardcruiserspt.free.nf&ip-version=auto

Do you see anything wrong?

Unfortunately you can’t use traceroutes to test the connection to free hosting as the servers block those requests (As well as ping requests)

2 Likes

That doesn’t really help because that online tool does a traceroute from the server powering centralops.net, not your own network.

Which distro? If it’s an Ubuntu or Debian-based distribution, you should be able to install the traceroute utility from APT and then use it with this command in the terminal:
traceroute longboardcruiserspt.free.nf

True, but it can still be helpful in this situation, as the connection being blocked at the network level or by the ISP would still terminate before even getting to the web server.

3 Likes

Endeavour OS.

Without VPN connection:

 $ traceroute longboardcruiserspt.free.nf
longboardcruiserspt.free.nf: Name or service not known
Cannot handle "host" cmdline arg `longboardcruiserspt.free.nf' on position 1 (argc 1)

With VPN connection:

$ traceroute longboardcruiserspt.free.nf
traceroute to longboardcruiserspt.free.nf (185.27.134.57), 30 hops max, 60 byte packets
 1  _gateway (10.96.0.1)  45.141 ms  49.562 ms  50.433 ms
 2  185.107.56.254 (185.107.56.254)  71.154 ms  72.060 ms  72.081 ms
 3  adm-b3-link.ip.twelve99.net (80.239.221.129)  53.207 ms  54.172 ms  54.190 ms
 4  * * *
 5  * * *
 6  * level3.fra06.atlas.cogentco.com (130.117.15.194)  48.253 ms ae9.cr6-fra2.ip4.gtt.net (141.136.110.41)  58.380 ms
 7  ae9.cr6-fra2.ip4.gtt.net (141.136.110.41)  58.522 ms et-7-0-19.cr6-fra2.ip4.gtt.net (195.72.93.246)  63.488 ms et-7-0-11.cr6-fra2.ip4.gtt.net (77.67.66.86)  66.648 ms
 8  ip4.gtt.net (213.251.24.102)  65.130 ms et-0-0-16-3.cr10-lon2.ip4.gtt.net (213.251.24.101)  65.062 ms  65.013 ms
 9  * et-0-0-16-3.cr10-lon2.ip4.gtt.net (213.251.24.101)  63.930 ms  64.860 ms
10  * * *
11  * * *
12  * 185.27.134.57 (185.27.134.57)  72.391 ms  67.880 ms

That would usually indicate a DNS issue. You may want to try flushing your DNS cache. If that doesn’t work, you should try switching to a different DNS provider, such as Cloudflare’s public DNS resolver. If that doesn’t work, your ISP is likely blocking the domain name or IP address for some reason, in which case using a VPN will likely be the most productive way around that.
You can also try doing a traceroute on your site’s IP address directly (185.27.134.57) which should look something like this:


If it doesn’t, then your ISP is blocking the entire IP address, rather than just the domain.

4 Likes

I can now confirm that it is indeed a DNS provider issue, more precisely a quad9.net “block”… here are the results of my tests:

With my Internet Provider’s DNS: site accessible
With Google’s DNS (8.8.8.8,8.8.4.4): site accessible
With CloudFlare’s DNS (1.1.1.1,1.0.0.1): site accessible
With Quad9’s DNS (9.9.9.9,149.112.112.112): site inaccessible

Can anyone please try to temporary switch to Quad9’s DNS and confirm the site is being blocked for you too?

It seems that free.nf is blocked at Quad9 or one of the filters they use. One of Quad9’s features is that they implement filters to protect you from bad sites. The downside of any such filters is that they can inadvertently block good sites.

I have submitted a request with the underlying filter to get this adjusted.

4 Likes

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