Change one thing at a time or you will chase this for an evening. Open the channel that fails, note exactly how it fails, disconnect the VPN, and replay the same channel within a minute or two. Playing clean without the tunnel and failing with it points squarely at routing, and nothing about your bandwidth, your router or your player needs investigating. Failing both ways means the VPN is a bystander and you should diagnose it as an ordinary stream fault: scope the problem to one channel, one category or everything, then work from there. Keep the same channel throughout, since a different feed is a different test.

1. 1Same channel, same minute, one variable changed
2. 2Fails with the tunnel off too: the VPN is not your cause

The app lets you specify a resolver for the app to use while connected, and its own documentation notes that doing so can cause trouble with streaming services. The mechanism is simple: every stream request starts with a name lookup, and if the resolver you pinned is slow, geographically distant or filtering, the player waits and then gives up before video ever starts. Web pages survive this because browsers retry patiently and cache aggressively. A live player does not, since it is trying to fetch the next 6-second segment on a deadline. Clear the custom entry, or set it to 1.1.1.1 or 8.8.8.8, then retest.

1. 1Symptom: web browsing normal, streams time out before the first frame
2. 2Fix: clear the custom resolver or point it at a public one

Split tunneling excludes chosen apps from the VPN connection so they run on your ordinary route. Two mistakes produce identical symptoms. The list can be inverted, so the player is protected when you meant it to be excluded, or excluded when you meant it protected. The list can also be reset by a reinstall or a version update, which is why a setup that ran for months breaks on an app update day. Android TV builds support the feature, so the fix is available on the boxes most people stream on. Rebuild the list deliberately and verify by checking the visible IP address inside and outside the player.

1. 1Inverted list and reset list look identical from the couch
2. 2Verify with the exit IP rather than assuming the toggle held

A tunnel that reconnects or rotates servers changes your exit address mid-stream. From the delivery side, that looks like a new session opening from a new address while the old one has not timed out, and a plan with a fixed number of simultaneous connections will refuse the newcomer. The pattern to look for is playback that runs three to ten minutes, stops, and works again after you restart the player. Pin one server, switch off anything that reconnects automatically, and confirm how many connections your plan actually includes. IP4KTV plans carry 1 to 5 at once, with unlimited installs across devices.

1. 1Runs a few minutes, dies, recovers on restart: session collision
2. 2Pin one server and one protocol before changing anything else

Answer it honestly rather than by habit. A VPN changes the route your traffic takes, which sometimes routes around a congested or filtered path, and it hides the content of that traffic from your internet provider. It also adds a hop and a layer of encryption, so it can add latency and it can make timing worse on a marginal line. What it does not do is change anything about licensing, which attaches to individual services rather than to the delivery method. Decide based on what the tunnel-off test showed, and run two tunnels at once never, since double encapsulation fragments segments.

1. 1A VPN is a routing and privacy tool, not a licensing one
2. 2One tunnel only: router VPN plus device VPN breaks segments