Unable to access website on Virgin Broadband

[Giurlani]

I have turned off the 'Web Safe' settings in my Virgin Media Online Security settings, both Virus Safe and Child Safe are turned off and while turning these off certain websites did come unblocked, I'm still finding an issue with this website which I desperately need to access because of my job. The website is https://panel.oink.industries/

I have tried loading the website on my mobile hotspot for my PC and it works then, but as soon as I switch over to my Virgin Broadband the website fails to load at all. I tried different browsers and the issue maintains.

I get a simple error saying:

This site can’t be reached

panel.oink.industries took too long to respond.

Try:

Checking the connection

Checking the proxy and the firewall

Running Windows Network Diagnostics

ERR_CONNECTION_TIMED_OUT

If you could please help me out, I would really appreciate it. It's really important that I'm able to access the site and I didn't foresee having this type of issue when I signed up for the broadband, which I really needed.

[paul0363]

Quickest and easiest (as it's working in modem mode) may be to buy your own WiFi router. 

There are plenty of options depending on what you need but if it's just WiFi and 1GB wired ports then something from here will be fine (needs to be a cable router and not ADSL/VDSL):

https://amazon.co.uk/s?k=cable+router&crid=37KUGJ3XVNLC3&sprefix=cable+route%2Caps%2C162&ref=nb_sb_n...

If you need something quicker try your local Currys:

https://www.currys.co.uk/search?q=router

As for your tech support saying it's nothing they can fix - the last *responded* hop was at

ae-8.a02.londen12.uk.bb.gin.ntt.net

which belongs to https://www.gin.ntt.net/   i.e. beyond VM.

The remaining hops weren't responded to either because the router concerned is set not to respond to ping requests or because the request is being dropped.  They're right in as far as we can't tell where the problem is (likely beyond hop 30 as my tracert below to the same site returns the same result as yours but the site is reachable). The problem is very likely as posted earlier - that the public IP you're obtaining in router mode is blacklisted somewhere (you can try here: https://whatismyipaddress.com/blacklist-check to see if it's blacklisted on a common list).

Here's my tracert (giving the same result as yours) and also a screenshot showing the site is reachable (I use modem mode with an Asus RT-AX88U router):

Tracing route to panel.oink.industries [198.251.80.180]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms Merlin [192.168.72.1]
2 13 ms 12 ms 10 ms 10.53.38.245
3 21 ms 16 ms 16 ms sgyl-core-2b-xe-222-0.network.virginmedia.net [82.2.246.233]
4 * * * Request timed out.
5 * * * Request timed out.
6 26 ms 29 ms 27 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
7 26 ms 26 ms 24 ms ae-8.a02.londen12.uk.bb.gin.ntt.net [129.250.66.101]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I also set my hub to router mode as a test and I can still reach the site and get the following tracert:

1 1 ms 1 ms 1 ms 192.168.0.1
2 14 ms 14 ms 8 ms 10.53.38.245
3 20 ms 16 ms 18 ms sgyl-core-2b-xe-222-0.network.virginmedia.net [82.2.246.233]
4 * * * Request timed out.
5 * * * Request timed out.
6 22 ms 25 ms 29 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
7 26 ms 26 ms 21 ms ae-8.a02.londen12.uk.bb.gin.ntt.net [129.250.66.101]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[用心棒]

Roger_Gooner earlier trace route (here) also showed a similar path.

Can you repeat the earlier curl command but in verbose mode, i.e:

curl -v -I https://cpanel.oink.industries/

Redact any personal information from result and post here. 

[Giurlani]

---

@用心棒 wrote:

Roger_Gooner earlier trace route (here) also showed a similar path.

Can you repeat the earlier curl command but in verbose mode, i.e:

curl -v -I https://cpanel.oink.industries/

Redact any personal information from result and post here. 

---

I really can't afford to buy a wireless modem as I have just signed up with Virgin for the broadband and didn't expect any other charges thinking it would just work out of the box with what they provided.

Here are the ersults to the curl test in verbose mode:

curl -v -I https://panel.oink.industries/
*   Trying 198.251.80.180:443...
* connect to 198.251.80.180 port 443 failed: Timed out
* Failed to connect to panel.oink.industries port 443 after 21057 ms: Timed out
* Closing connection 0
curl: (28) Failed to connect to panel.oink.industries port 443 after 21057 ms: Timed out

[用心棒]

Had hoped curl might show more information but alas no.

Consider going back to site operator and explain to them that:

• other users have similar trace route paths and successful reach the site
• network traffic does exit ISP's network as shown by hop to ae-8.a02.londen12.uk.bb.gin.ntt.net [129.250.66.101]
• your ISP router has a modem mode and a non-modem mode with each having a unique public IP Address
  in non-modem mode, you cannot connection to site
  in modem mode, you can connect to site

Given this information it is fair to conclude your IP Address (when in non-modem mode) is being blocked from connecting to site.

[paul0363]

If you don't want to buy another router you could see if anyone you know has an old ISP provided router that was used on a fibre connection (either FTTP or FTTC).  These usually have a WAN port (sometimes one of the ethernet ports is dual WAN/LAN depending on the connection) for connection to an Openreach modem and can normally be reconfigured quite easily to work on VM if they've not been completely locked down by the ISP. e.g. the TalkTalk SuperRouter can be reconfigured - needs ethernet cable plugged in WAN port and configured to use DHCP to obtain a public IP.  

[legacy1]

Assuming your being blocked at 198.251.80.180 and is not VM routeing from that end point to your IP nothing you can do but ask the admin to unblock you or change your IP with another router.