Netflix no longer works when bonding via FusionHub

Has anyone else had any issues accessing Netflix when you’re bonding multiple WANs via FusionHub? It no longer works for any of my customers and I’ve had 3 different ones complain about it over the past 2 weeks. It basically gives an error saying Netflix cannot be accessed over a VPN connection or proxy, and to connect directly without using VPN to use Netflix services. This is for Netflix Canada. It basically gives the error message you’d get when using VPN and trying to access Netflix US. It’s basically this here: How to Fix Netflix Proxy Error With a VPN in 2024

It sounds as though Netflix has detected that the traffic is being routed over a VPN. If you only use one WAN do the customers get the same message?

3 Likes

No they don’t, it’s only when we are bonding 2 of them via FusionHub it gives that error.

Online streaming services are blocking access from massive blocks of IPs owned by cloud hosting companies to block out of region/country access.

To get round this you can do bonding from a remote peer to a FusionHub, then set send all traffic via LAN and forward to a firewall appliance hosted alongside the Fusionhub which has an OpenVPN connection to a VPN service that specializes VPN for Netflix (eg NordVPN, PrivateVPN, ExpressVPN).

2 Likes

Just to make sure I do not misunderstand: If you connect to the fusionhub with a single WAN (no bonding) and route your pepVPN traffic across that WAN, then netflix does not object when you stream Netflix across the Fusionhub/VPN?

No it still does. Apparently Netflix has banned the IP ranges of all popular cloud providers, so they don’t care if it’s bonding they just see it’s an Amazon or DigitalOcean, Azure, etc IP and ban it.

Yeah, that’s pretty much the shape of things. The problem is not the FusionHub or bonding per se, but rather the IP address of the FusionHub platform that is being used. The core issue is that (many of) the commercially available virtual hosting and VPN platforms are employed by users to relocate their internet location to a different country, avoiding copyright restrictions.

If you were to host the FusionHub (or a Peplink device with bonding capabilities) on a platform with a (say) residential or regular corporate IP address then things would likely be just fine.

It depend on which VPN you are using. When I want to access Netflix via VPN than I have also tested a few VPN services but didn’t. Than I start using ExpressVPN now for over a year and able to access Netflix easily, importantly I am getting much better speed that any other vpn service and no issues related to connectivity till now. Very Smooth VPN service indeed along with providing good features. Though I was just reading here: ExpressVPN Review 2024: Is It Worth The Price? | VPNveteran.com Highlighted cons are somewhat relevant. I know Expressvpn is expensive and also offer lesser login count on multiple devices. But such cons are bearable for me. I am more interested in getting good speed and accessing quality streaming sites without facing any connectivity issue.

So since these ip’s are blocked is there a way when using Fusionhub to keep Netflix traffic from being bonded and pick a connection to use by setting up a rule? If this is the case how would it be set up?

1 Like

Hi @charlesm

I just use the following outbound policy at home and this seems to work just fine.

1 Like

Or, if you have a dedicated streaming device, and you want it to use a local load balancing policy rather than going through SF, you can turn on Expert Mode in your Outbound Policy screen, define a new policy that has the IP of your streaming device as Source. Then drag this policy above the PepVPN line. It will not use Speedfusion I find this useful since now I can have one policy for all my streaming services since they are run from a dedicated device and send traffic through the WAN with the Fastest Response Time; since you may only be streaming from one source at a time, this WAN will not be saturated during your streaming session - works for me.

It would be great if you could define Source as a traffic type (much like you can do with SaaS) so that it would work for any device that runs a streaming app, like Windows or in a browser like Chrome. I don’t know if Peplink will consider this but I’ve asked for it in Feature Requests. It’s all about options, right?

Creating and Outbound Policy with Destination = ‘netflix.com’ DID NOT work for me as someone mentioned earlier.

1 Like

I had a similar problem when I was using a free VPN. However, after I changed it, everything worked fine. Maybe this is a problem in your region, and it will disappear soon. Moreover, I tried to find Bordertown Season 4 and information about it. That’s why I changed the VPN to Finland, but I couldn’t find any info about it, and I turned it off. I observed you change the IP address and log in from the same device. The app might have some bugs or can not function for some minutes or even hours.