Xteve VPN

xTeVe VPN is a Docker image that runs xTeVe, an IPTV (Internet Protocol television) and EPG (electronic program guide) proxy server for Plex, Emby and similar…

  • Media Applications
  • Media Servers
  • Network Services
  • Tools & Utilities
xTeVe VPN is a Docker image that runs xTeVe, an IPTV (Internet Protocol television) and EPG (electronic program guide) proxy server for Plex, Emby and similar TV apps, behind an OpenVPN tunnel. In bridge mode it exposes the xTeVe web interface on port 34400 and uses your .ovpn credentials so proxy traffic travels through your VPN. It suits homelab users whose tuner or channel sources are geo-restricted or must be reached from outside the home network.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

14/100 Low

Maintained
0last commit 2186 days ago
Popular
198 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 47 days ago

GitHub stars
8
Open issues
2
Last commit
2020-11-26
Activity
stale

Checked 20 days ago - source: GitHub (alturismo/xteve_vpn)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Default port and config folder xTeVe listens on port 34400 (the numbered address your TV app uses to find it) and saves settings in ~/.xteve/ (a hidden folder in your home directory) by default. If that port is busy, start it with -port and put settings in a known folder with -config so your setup stays reachable and easy to find. source
  • Back up the settings folder The settings folder holds your channel lineup and guide choices, so keep a backup or note where it lives. If it is lost, your TV app will lose your customized channels and guide data. source
  • Add login details if needed If authentication is enabled, guide requests may need your username and password. Without them, your TV app may fail to load the guide or channel information. source
  • Place the OVPN file and set network variables The container runs in Docker bridge mode. Put your .ovpn file in the container's /config folder, edit the OVPN credentials and the LOCAL_NET variable to match your netmask, and if IPv6 is active on your network add ...disable_ipv6=1 as an extra parameter. source
  • Access web interface Access the xTeVe web interface at IP:34400/web after the container starts. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I reach the xTeVe web interface in the Docker setup?

Use port 34400 and open the /web/ path on the host IP.

What extra parameter should I set if IPv6 is active on the network?

Add disable_ipv6=1 to the extra parameters.

Where do I put the OpenVPN file and credentials for xteve_vpn?

Put your ovpn file in /config and edit the credentials in /config, then set LOCAL_NET to match your netmask.

Will xTeVe always unblock an IPTV source just because it runs behind a VPN?

Not necessarily; xTeVe can pass the IPTV service URL to the client, so the client may still contact the service directly and remain blocked.

How can I verify the path xTeVe uses to find an M3U playlist in unRAID?

Check the folder mapping in the unRAID Docker tab; the left side is the container path and the right side of the colon is the host path.

Answers sourced from github.com, www.reddit.com, www.redditmedia.com

Community

Collected 53 days ago - public community threads