← Directory

Xteve

Xteve is a self-hosted IPTV streaming and recording service that provides a TVHeadend-compatible interface so TV clients can watch live channels, use…

  • Media Applications
  • Network Services
  • Tools & Utilities
Xteve is a self-hosted IPTV streaming and recording service that provides a TVHeadend-compatible interface so TV clients can watch live channels, use time-shift, and record programs.

Platform availability

Available on 1 of 9 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)

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.

18/100 Low

Maintained
0last commit 1357 days ago
Popular
3238 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 14 days ago

GitHub stars
38
Open issues
3
Last commit
2023-01-25
Latest release
latest
Activity
stale

Checked 6 days ago - source: GitHub (alturismo/xteve)

Resources & Compatibility

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

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

First-install notes

  • Use the default port and config folder If you run xTeVe normally, it listens on port 34400 and stores settings in ~/.xteve/. Keep that port open for your TV clients and use -port or -config only if you need a different value, because a blocked port or moved config folder can make the service unreachable or lose your setup. source
  • Back up your config folder The config folder holds your channels, tuners, and preferences, so back it up before making big changes. It can be brought back with -restore, which saves you from having to rebuild everything if something goes wrong. source
  • Add login details if auth is on If you enable authentication, guide and stream requests need the username and password in the request. Without those details, your TV app or media server may not be able to get channels or start a stream. source

Fetched 6 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I access and configure xteve in a Docker setup?

Run the container with host networking and mounts for /root/.xteve, /config, /tmp/xteve, and optionally /TVH. After the container starts, open the host IP on port 34400 under the /web/ path, and delete the config data if you want to start from scratch.

Can xteve load compressed .xml.gz EPG files?

A user reports that xteve refuses to load an EPG as .xml.gz and instead wants a plain .xml file.

What happens with xteve temp files when multiple devices stream at once?

One GitHub issue reports that xteve writes temp files until it reaches 25, then deletes old files and writes again, which can cause buffering with two or more devices while one device works fine.

Does xteve need to start with Windows for Plex to recognize it?

A user reports that on Windows, if xteve is not started with the computer, manually starting it may require restarting the Plex server before Plex recognizes it.

How can channel icon links work when xteve is behind a reverse proxy?

The Docker setup includes a rewrite function for reverse-proxy use of the XML data so icon links can work.

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

Community

Collected 9 days ago - public community threads