Plans Support

VISTU SERVER · HOW IT WORKS

How the VPN in Vistu Server works

Vistu Server can send the playlists you choose through your VPN. Your TVs don’t need a VPN app, and nothing else in your home uses the VPN: not your library, not your NAS, not the other devices on your network.

The short version

Where the traffic goes

Without a VPN, a TV asks Vistu Server for a channel, and the server (or the TV itself) connects to your TV service over your home internet. Your TV service sees your home’s internet address.

A playlist without a VPN TVs and phones connect to Vistu Server, which connects through your router and home internet to your TV service. TVs & phones the Vistu apps Vistu Server on your NAS or computer Your router home internet Your TV service sees your home address Your home network
1. A playlist without a VPN: your TV service sees your home’s internet address.

With a VPN location chosen for a playlist, Vistu Server keeps an encrypted tunnel open to your VPN service’s server. Everything for that playlist goes into the tunnel, comes out at the VPN server, and only then reaches your TV service, which sees the VPN’s address instead of yours. The tunnel still crosses your router, but your router (and your internet provider) only see encrypted traffic to the VPN.

A playlist with the VPN on The playlist's traffic goes from Vistu Server through an encrypted tunnel to the VPN server and then to the TV service. Your library, the web pages, sports and access from outside go out over your own connection. TVs & phones no VPN app Vistu Server VPN playlist encrypted tunnel crosses your router, sealed VPN server your VPN service TV service sees the VPN’s address Everything else library & NAS · web pages · sports · access from outside Your own connection as usual, never the VPN
2. The VPN on a playlist: only that playlist’s traffic goes through the tunnel (a split tunnel).

A playlist on the VPN always plays through Vistu Server. Normally a TV may connect to your TV service directly; for a VPN playlist the server never gives TVs the service’s addresses, only its own. Channel logos and posters come through the server too. That’s what lets a TV without any VPN app watch through the VPN.

What uses the VPN

Through the VPN (for playlists you put on one)Never through the VPN
Loading the playlist: channels, movies, seriesYour movies and series library, and your NAS
Live channels, movies and episodes as they playThe web pages you manage the server from
Logos, posters and other picturesSports times and scores
The guide, when it comes from your TV service’s own address (other guide websites too, if you tick that in the playlist)The optional update check
Name lookups (DNS) for all of the aboveWatching from outside your home
The connection check for that playlistOther playlists, and every other device in your home

Names are looked up inside the tunnel. Before connecting to your TV service, a computer has to turn its name into an address. For a VPN playlist, Vistu Server asks your VPN service’s own name server, through the tunnel. Your home router and internet provider don’t see which names it looks up.

Several VPNs and locations

Most VPN services have servers in many countries, and give you a file for each one. In Vistu Server, each file you add is a location, for example PrivadoVPN · London. Add as many as you’ll use, from one service or several, then choose a location for each playlist. A UK service can come out in London while a US one comes out in New York, and a playlist that doesn’t need a VPN uses your own connection.

Playlists on different VPN locations Inside Vistu Server, a UK playlist goes through a tunnel to PrivadoVPN in London, a US playlist through a tunnel to Mullvad in New York, and a local playlist over your own connection. A Toronto location that no playlist uses isn't connected. Vistu Server UK playlist VPN: PrivadoVPN · London US playlist VPN: Mullvad · New York Local playlist No VPN tunnel (OpenVPN) tunnel (WireGuard) PrivadoVPN · London the UK service sees a London address Mullvad · New York the US service sees a New York address Your own connection as usual PrivadoVPN · Toronto: off (no playlist uses it)
3. Each playlist goes through its own location, or none. Locations no playlist uses stay off.

When the VPN drops

VPN connections drop now and then: the VPN server restarts, your internet blips, a login expires. A lot of setups quietly carry on over your own connection when that happens. Vistu Server doesn’t. Connections for a VPN playlist can only leave through the tunnel. With the tunnel down, they fail.

When the VPN drops With the tunnel broken, the VPN playlist stops. Vistu Server does not send it over your own connection instead. It reconnects by itself when the VPN is back. TV channel won’t start Vistu Server VPN playlist tunnel down VPN server unreachable TV service not contacted Your own connection never used instead no fallback for a VPN playlist
4. The VPN drops: the playlist stops instead of using your own connection, and comes back when the VPN does.

While it’s down, channels on those playlists won’t start, and the VPN page says what’s happening (for example “trying to reach the VPN server”). Vistu Server keeps reconnecting on its own; you don’t need to do anything once the VPN is reachable again. Playlists that don’t use the VPN, and your library, carry on as normal the whole time.

WireGuard or OpenVPN

VPN services hand out settings files for “manual setup” or “router setup”. Vistu Server takes the two common kinds: WireGuard files (.conf) and OpenVPN files (.ovpn). Both give you the same split tunnel and the same fail-closed behaviour. The difference is how they run inside the container.

Inside the container: WireGuard and OpenVPN With WireGuard, Vistu Server's helper runs the whole VPN in its own memory with no network device and no extra rights. With OpenVPN, the openvpn program makes a network device called vistu0, which needs the NET_ADMIN right, and the helper ties the playlist's connections to that device. In both cases the container's own routes don't change. WIREGUARD · no extra settings Vistu Server ordinary user VPN helper a private proxy WireGuard in the helper’s memory: no device, no routes sealed, to the VPN server OPENVPN · NET_ADMIN + /dev/net/tun Vistu Server ordinary user VPN helper tied to vistu1 vistu1 device made by openvpn, takes no routes openvpn the only program with NET_ADMIN sealed, to the VPN server Either way the container’s own routes don’t change: everything else leaves the usual way.
5. Inside the container. WireGuard runs entirely in the helper; OpenVPN uses its own network device, which needs two container settings.
WireGuardOpenVPN
File.conf.ovpn, with everything in one file
Container settingsNoneNET_ADMIN and /dev/net/tun
How it runsEntirely inside Vistu Server’s VPN helper, in memoryThe standard openvpn program, with its own network device
Sign-inKeys in the fileOften a username and password as well, kept encrypted on the server
ServicesMullvad, Proton VPN, IVPN, AirVPN, Surfshark, Windscribe and othersPrivadoVPN, NordVPN, ExpressVPN and others

Use WireGuard when your service offers it. It needs nothing extra from Docker, it’s quick to connect, and it’s light on a NAS. OpenVPN is there for the services that only give OpenVPN files.

WireGuard: no extra rights

WireGuard’s whole job is turning network packets into encrypted ones. Vistu Server’s VPN helper does that in its own memory, with its own small network stack, and offers the result as a private proxy that only the server uses. No network device is created and the container needs no extra permissions, which is why WireGuard works with a plain docker run.

OpenVPN: its own network device

OpenVPN works differently and needs a real network device: one per location, called vistu1, vistu2 and so on. Making one inside a container takes two settings: the NET_ADMIN right and the /dev/net/tun device. Vistu Server keeps their reach as small as it can:

Setting up OpenVPN

Add the two settings to the Vistu Server container, then recreate it. With Docker Compose, under the vistu-server service:

    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun

Then docker compose up -d. With docker run, add --cap-add NET_ADMIN --device /dev/net/tun. On a NAS with a container app, look for “capabilities” (add NET_ADMIN) and “devices” (add /dev/net/tun).

  1. Open Manage › TV service › VPN and choose your VPN service. For OpenVPN services the page first checks the container and says Ready for OpenVPN, or exactly what’s missing.
  2. Follow the steps to download an .ovpn file for each location you want from your VPN service’s website.
  3. Choose the files (several at once is fine), name each location, enter the username and password, and press Add and test. Some services (NordVPN, ExpressVPN) have a separate username and password for manual setup: use those, not your account login.
  4. In each playlist that should use a VPN, choose its location.

If it doesn’t start:

Checking it works

What we see

Nothing. The VPN runs on your server, between you and your VPN service. Your VPN file, username and password are stored encrypted on your server and never sent to us, and Vistu Server doesn’t call any Vistu service to check the VPN.

← Vistu Server · Questions? Contact support