on 30-08-2018 22:35
Connecting to github.com on port 22 is impossible over a virgin media connection since its DNS record is hijacked to point to a proxy box that only accepts TCP on ports 80/443.
This is the same issue as reported here https://community.virginmedia.com/t5/Networking-and-WiFi/DNS-issue/td-p/3792034
Opening a new question since the old one is marked solved (the underlying issue isn't) and people at Virgin Media seem to need one to be open to even investigate things.
10-09-2018 14:22 - edited 10-09-2018 14:23
Hi cargill,
We don't block port 22 (SSH, port forwarding etc). If your connection is being routed via a proxy I wonder if it has anything to do with Websafe? Not saying it is, just querying it. Would you please disable Websafe (Virus Safe & Child Safe) and let me know if the issue persists?
Let me know how you get on 🙂
on 12-09-2018 19:05
Hi Jen,
yes, it is the Virgin Media proxy (62.252.172.241 <-> know-sspiprxy-vip.network.virginmedia.net.) that is being replaced for github.com and probably yes, it might be Websafe.
The problem is I am a tenant in this house and the landlord will certainly not consent to disabling something that's called "Virus Safe & Child Safe" on this internet connection.
I might also question the rationale of setting up a HTTP proxy for GitHub since it will immediately switch over to HTTPS and such a proxy should have no way of preventing any virus/other harmful traffic anyway?
on 12-09-2018 20:12
on 12-09-2018 23:26
on 13-09-2018 00:07
on 15-09-2018 12:47
on 15-09-2018 12:52
on 16-09-2018 22:21
Just had the same issue although switching both the Child Safe and Virus Safe didn't fix the issue, I had to add www.github.com to the allowed list to get it to work. This has changed in the last few weeks as it was working fine for me as well. something Virgin has done. I'm on a Hub 3
on 14-10-2018 15:14
I can confirm that git or ssh connections to github.com do not work with VM's WebSafe.
and
that by adding github.com to the whitelist makes it work again.
Why can't Virgin Media do it properly? Apparently it has been reported 3 months ago and they have not been able to sort it out.