How To Install XTeVe On Synology NAS: Complete Setup Guide
Installing xTeVe on a Synology NAS bridges the gap between M3U playlists and media servers like Plex or Emby by emulating an HDHomeRun tuner, allowing seamless DVR and Live TV integration. Successfully deploying this environment requires a compatible Synology DiskStation, Docker package support, and precise network port mapping to ensure stable stream concurrency.
Pre-Operation & Technical Prerequisites Checklist
Deploying xTeVe within a Network Attached Storage environment demands strict adherence to system requirements, directory paths, and network configurations. Because xTeVe acts as a middleware proxy that handles multiple simultaneous client requests, resource allocation directly impacts stream stability and transcoding efficiency.
- Essential Gear & Tools: A Synology NAS running DiskStation Manager (DSM) 6.2 or DSM 7.x with an Intel or AMD processor supporting Docker, an active Plex Pass subscription (required for Plex Live TV/DVR integration), a valid M3U playlist URL, and an XMLTV EPG (Electronic Program Guide) link.
- Prerequisite Knowledge & Standards: Familiarity with Docker containerization principles, basic understanding of IP networking, subnet masks, static IP assignments, and port forwarding fundamentals within a home network.
- Budget & Duration Benchmarks: Financial investment is zero for open-source xTeVe software (though Plex Pass requires a license), and the complete installation timeline ranges from 25 to 45 minutes depending on playlist size and XML parsing speed.
Step-by-Step xTeVe Deployment on Synology DiskStation
Step 1: Install and Configure the Docker Environment
Open the Synology Package Center, search for the Docker package (renamed to Container Manager in newer DSM versions), and click Install. Once installation finishes, launch Container Manager and navigate to the Registry tab. Search for the official xteve repository (typically alby/xteve or the updated codeamin/xteve image), select the latest tag, and click Download to pull the image to your local Synology storage pool.
Pro-Tip: Always pin your container image to a specific version tag rather than the latest identifier to prevent automated updates from breaking existing M3U stream mappings during routine maintenance.
Step 2: Establish Persistent Storage Volumes
Create a dedicated shared folder on your Synology storage pool named docker, and inside it, create a subfolder labeled xteve. Inside this xteve directory, create two additional subfolders named conf and temp. These persistent directories are critical because xTeVe stores configuration files, active buffer paths, and cached guide data locally; mapping them prevents data loss when the container restarts or updates.
Step 3: Configure Container Networking and Port Mappings
Launch the process to create a new container from the downloaded xteve image within Container Manager. Assign a clear container name such as xteve-server, and ensure the resource limitation settings allow adequate RAM based on your M3U channel count. Proceed to the Advanced Settings tab, check the box to use the same network as Docker host (Host network mode) to simplify UPnP discovery and SSDP device broadcasting across your local subnet. Alternatively, if using Bridge mode, explicitly map local port 34400 to container port 34400.
Warning: Avoid using dynamic or auto-assigned host ports for xTeVe, as Plex and Emby require a static, persistent port configuration (default 34400) to maintain stable communication with the virtual tuner.
Step 4: Finalize Environment Variables and Launch
Add any necessary environment variables during the container creation wizard, specifically PUID and PGID corresponding to your Synology user credentials to avoid file permission conflicts. Map your previously created local storage paths to the container mount points: map the conf folder to /config and the temp folder to /tmp/xteve. Review the summary page, verify that volume mounts and network settings are correct, and click Apply to launch the xTeVe container instance.
Installation Relution auf einem Synology NAS | Relution Community
Technical Parameters and Configuration Comparison
| Configuration Parameter | Bridge Network Mode | Host Network Mode | Recommended Standard |
|---|---|---|---|
| Port Mapping | Requires explicit mapping (34400:34400) | Uses host ports directly without translation | Host Network Mode for easier tuner discovery |
| SSDP Broadcasting | Often blocked across virtual subnets | Broadcasts natively to local network adapters | Host Network Mode to ensure Plex auto-detection |
| Resource Overhead | Minimal virtualization penalty | Zero virtualization network penalty | Host Network Mode for optimal stream throughput |
| IP Address Assignment | Shares NAS IP with translated ports | Directly utilizes Synology NAS IP address | Host Network Mode for streamlined router integration |
Common Site Failures and Field Fixes
- Root Cause: Plex fails to discover the virtual HDHomeRun tuner automatically due to subnet isolation or firewall restrictions.
- Actionable Fix: Switch the Docker container network configuration from Bridge mode to Host mode, or manually enter the Synology NAS IP address followed by port 34400 inside the Plex Live TV setup wizard.
- Root Cause: Streams fail to load or buffer infinitely due to strict file permission errors on the Synology storage volumes.
- Actionable Fix: Access File Station, right-click the docker/xteve folder, navigate to Properties, and ensure your system user or administrator account possesses full Read/Write permissions with inheritance enabled for all child objects.
- Root Cause: EPG guide data disappears or fails to refresh because the XMLTV link is blocked, rate-limited, or malformed.
- Actionable Fix: Access the xTeVe Web UI at your NAS IP address on port 34400, navigate to the XMLTV settings tab, increase the refresh interval, and validate the source URL in a standard web browser to confirm raw XML output.
Frequently Asked Questions
What is the primary purpose of running xTeVe on a Synology NAS?
xTeVe acts as a software-based M3U proxy and virtual tuner that translates standard IPTV playlists and XMLTV guide files into a format compatible with media servers like Plex and Emby. By emulating an HDHomeRun device, it allows users to integrate live television and DVR capabilities directly into their existing media ecosystem without specialized hardware.
Do I need a Plex Pass subscription to use xTeVe?
Yes, Plex requires an active Plex Pass subscription to unlock the Live TV and DVR feature set necessary for adding external network tuners. Without a Plex Pass, the option to configure a custom tuner device will not appear within the Plex server settings dashboard.
How many simultaneous streams can xTeVe handle on a Synology NAS?
Stream concurrency depends primarily on your Synology NAS hardware specifications (CPU and RAM) and your IPTV provider's simultaneous connection limits. While xTeVe itself has a very low footprint, each active stream consumes network bandwidth and CPU resources if transcoding is required by the end client.
Can xTeVe record live television broadcasts?
xTeVe does not handle the actual recording process itself; instead, it exposes the virtual tuner to media servers like Plex, Emby, or Jellyfin. The connected media server handles scheduling, buffer management, and writing the final recorded video files directly to your designated Synology storage pools.
Why does the xTeVe Web UI become inaccessible after a NAS reboot?
This typically occurs if the Docker container is not configured to restart automatically or if the static IP address of the Synology NAS has changed. Ensure that container restart policies are set to "Always" in Container Manager and assign a static reserved IP address via your local network router.
Optimize your home media streaming infrastructure today by deploying xTeVe on your Synology NAS for a unified Live TV and DVR experience.
