Hey guys, just wondering if there was ever a solution to the secure connections issue with the Virgin Media router, I am unable to connect securely with this ISP (well ever), I have always used the unsecure option. I’ve been looking into this and I’ve hit a brick wall. I figure this is a DNS issue and from browsing other threads came across this reply (which was acuatlly to a problem with getting remote access, which is working fine for me)
I think you’ll have to make do without Secure Connections.
The Virgin Hub has am over zealous ‘DNS rebinding protection’ which also prevents your Plex server from getting a fully qualified domain name on the .plex.direct domain.
If you cannot reach your server right now (I assume you are running it on Windows, right?), then do this:
quit Plex server with its task tray icon
import the attached registry file. It disables Secure Connections
restart Plex server
Be advised that this change also disables ‘Relayed’ connections.
I found another reply from the VM forums about their routers
You are correct there is no internal DNS on the hub 3, if you are setting a static IP on a device like Windows you can select what DNS servers to use, i.e. Google 8.8.8.8, 8.8.4.4 there are others out there. The hub itself uses DNS masquerading to always route to Virgins DNS servers, so any traffic going to hub on Port 53 get routed to Virgins DNS.
So it seems they use DNSmasq
I read the troubleshooting section about secure connections and it seems I can’t
add rebind-domain-ok=/plex.direct/ because the router settings page doesn’t have this option. Would simply switching to a public DNS like google work? Or is there absolutely no way of getting a secure connection with VM hub 3?
If you are experiencing a DNS rebinding protection related issue, yes, using a public DNS server could help (or you could set up a Pi-Hole DNS server on your network and point to that).
For clients which allow it, you can manually configure their DNS settings to point to one of the public providers.
Some client devices (Roku’s being a great example) don’t allow you to manually configure the DNS servers they use; they rely on those that the router’s DHCP server tell them to use. Check your router’s DHCP server settings and see if it allows you to configure the DNS servers advertised to clients. Most do allow this. If so, configure it to give out Google’s (8.8.8.8) or CloudFlare’s (1.1.1.1) DNS servers as a test (these are ones I know don’t use DNS rebinding protection).
For this to work, you’ll likely need to cause your clients to renew their DHCP leases to pull new DHCP server information. They’ll renew them automatically over time as well, depending on the length of the lease.
Thanks philipsw for your reply, I’ll try one of the public DNS servers and see how it goes, my hub is actually a modem/router and virgin doesn’t allow any DNS change on this hub so I’d have to buy a router first and use the VM hub as a modem only.
Hey guys, so after changing the DNS servers to that of google (in the computer the hosting plex), things are working, remote access and secure connections running. Awesome!
Thanks for sharing this! I’ve been burdened with this issue since using Virgin.
Time to go test.
Historically I’ve found smaller files are fine, but higher res and larger files have always conked out. I get the not enough bandwidth error, even though that’s 100% no an issue over wired connection.
I’ll give that a try