Netflix Works on My Phone but Not the Smart TV: The TV Needed Its Own VPN Route

The film played perfectly on my phone.

The television showed an error.

We were in a rented apartment in Copenhagen, gathered around a smart TV that seemed ideal for the evening until anyone tried to watch something on it. My niece had been waiting to see Heartstopper Forever, the finale film Netflix released on July 17, 2026. She had already threatened to mute every group chat until we finished it.

On my phone, I opened Netflix through the VPN I normally used while travelling. The film appeared in search and played immediately.

I tapped the Cast icon.

The television switched to the Netflix logo, displayed a loading circle and then stopped at a message saying the device appeared to be using a VPN or proxy.

I blamed the television first.

I restarted it, reopened Netflix and signed out of the account. Entering the password again with an on-screen keyboard took long enough for everyone in the room to begin offering advice.

The error returned.

I checked the phone. The same film was still playing there without hesitation.

That was what made the failure confusing. Same account. Same apartment. Same Wi-Fi. Same title.

Yet the phone could watch it and the television could not.

I was no longer searching for a generally “good streaming VPN.” I needed to understand why the working connection disappeared the moment I tried to move the film to the larger screen.

Casting moved the request, not the protected connection

I had assumed the phone remained responsible for the stream.

It did not.

In a Google Cast session, the phone acts as the controller, while the receiving device requests and plays the media itself. Tapping Cast did not send the already playing video through my phone’s VPN. It instructed the television to open its own Netflix session over its own network connection.

The phone and the TV were therefore taking different routes.

My phone reached Netflix through the VPN installed on it. The television reached Netflix directly through the apartment Wi-Fi. When playback moved to the television, the protected route stayed behind on the phone.

That explained why the result changed immediately.

The same mistaken assumption appears in public discussions from people whose streams work on a VPN-connected phone but fail as soon as a Cast receiver takes over. The practical lesson is simple: the device playing the video needs its own usable connection.

Restarting Netflix would not solve that. The TV needed a VPN route of its own.

The familiar provider worked differently on the television

The smart television ran Google TV, so I installed the major VPN provider I already used on my phone.

That felt like the cleanest solution. The company had a long operating history, a large support organisation and plenty of server locations. Since the phone worked through the service, I expected the television to work through it too.

First, I had to sign in.

I entered my email address with the remote, corrected two mistakes and moved to the password field. The provider then sent a verification message to my phone.

By the time the television finally displayed the server list, the rest of the room had moved from impatience to snacks.

I selected the same country shown in the phone app.

The VPN connected.

Netflix opened normally. The profile page appeared, and search found the film.

Playback produced the proxy warning again.

Netflix uses that message when it believes a device or network is connecting through a VPN or proxy. The menus can still load because the decisive check often arrives when playback begins.

I returned to the VPN and selected another server.

This time, the title page loaded more slowly. When I pressed Play, the circle spun for several seconds and returned me to the profile screen.

A third server reached the first frame before another playback error appeared.

The provider’s large network gave me more options, but each option repeated the same awkward loop:

Leave Netflix. Open the VPN. Choose another city. Reopen Netflix. Find the film. Press Play. Wait.

The phone was still playing the film through its original connection. The television, despite using the same VPN brand, was emerging through a different shared exit address—one Netflix would not accept for playback.

I could not see Netflix’s internal filtering rules, so I could not know whether the rejection came from the exit address, its network ownership, its previous traffic or several signals together. The visible result was enough: working on one device did not make the provider’s other routes equally useful.

The television needed an accepted route of its own, not merely the same logo as the phone.

Mirroring moved the picture but ruined the setup

Screen mirroring looked like the obvious shortcut.

Unlike casting, mirroring would keep playback on the phone and reproduce the phone’s screen on the television. That would preserve the VPN route that already worked.

The picture appeared, but with thick borders and uneven motion. Playback controls remained visible whenever I touched the phone. A notification briefly covered the subtitles.

When the phone screen dimmed, the television dimmed with it.

The method technically moved the film to the larger screen. It did not create a proper television experience. It turned the phone into a fragile video cable.

It also made the phone unusable for everything else. Nobody could check a message, order food or look up the train schedule without interrupting the film.

That attempt clarified the standard.

I did not merely want the television to display the phone’s screen. I wanted Netflix to play normally on the television while the phone returned to being a phone.

The smaller app put the route on the correct device

I removed the first VPN connection and opened OnlyDogs VPN on the television.

Instead of typing another email address and password with the remote, I linked the TV using a verification code from my phone. That avoided another session with the on-screen keyboard and connected the second device without creating a separate conventional login.

Then I selected the situation-based streaming preset rather than choosing another country and city manually.

The service established the connection.

I reopened Netflix.

The profile loaded.

Heartstopper Forever appeared in the same place it had appeared on my phone.

I pressed Play.

The Netflix logo disappeared. The film began.

No proxy warning.

No return to the profile screen.

No phone balanced upright beside the television to keep a mirrored image alive.

I put the remote down and watched the first minute, still expecting another error to interrupt the opening scene.

It did not.

My niece asked why I was staring at the corner of the screen instead of watching the film.

I realised I had been monitoring the connection rather than the story.

That was the result the comparison needed to produce. Netflix was no longer working somewhere in the apartment. It was playing on the device everyone had gathered to watch.

The useful explanation was short

A VPN connection belongs to the device or network where it is configured. Installing one on a phone does not automatically place the smart television behind the same route.

Casting made that separation easy to miss because the phone continued showing the controls. It felt as though the phone were carrying the stream when it was really directing a receiver on the television.

The smaller app solved the problem where playback was actually happening. Its streaming preset selected a usable route for the television, while additional traffic obfuscation made the connection less obvious as a familiar shared VPN exit.

The established provider had offered more server locations, but the TV kept reaching Netflix through routes the service rejected. The smaller app chose one route and started the film.

That mattered more than whether both VPN apps displayed the same country.

Two devices can show the same flag while presenting Netflix with completely different connections.

The phone became useful again

A few minutes into the film, someone asked whether the takeaway restaurant was still open.

For the first time that evening, I could pick up my phone without disturbing the television.

The Netflix controls remained available, but the video no longer depended on the phone’s screen, battery or current app. I checked the menu, placed the order and returned to the group chat my niece had been avoiding.

That smaller benefit confirmed that the setup was finally correct.

The television was streaming.

The phone was controlling when necessary, not carrying the entire viewing session.

The verification-code setup also gave me a reason to remember the service after the film ended. Living-room devices are shared, frequently logged out and unpleasant places to type long credentials. Adding one through a short code fitted the device better than treating the TV like another laptop.

Fewer locations, but the right route for the screen

The service has fewer server locations than the largest providers. Its public history is shorter, and fewer independent reviews are available.

Someone who needs a precise exit city for regional testing or specialised business access may prefer the manual control of a larger network.

That was not the decision in the rented apartment.

The established provider worked on my phone but sent the television through routes Netflix rejected. Casting exposed the TV’s separate connection. Mirroring preserved the phone’s route but made the phone part of the screen.

The smaller app put the VPN where playback was actually happening, linked the television without another remote-control login and let the film begin normally.

When Netflix works on a phone but not a smart TV, the important question is not whether the phone’s VPN is connected. It is whether the television has its own working route before everyone loses interest and chooses something else.

Editorial context: OnlyDogs VPN commissioned the original article. The first-person narrative is a composite based on public reports and product testing.