Understand what runs where
Install and operate the gateway on your own computer, server, or supported network device. It handles any provider-specific sign-in or stream conversion. Tellyra does not install, discover, configure, or remotely control it.
- The gateway and Apple device should be on the same trusted local network.
- Tellyra remains a player for user-provided sources.
- Use only services and media you are authorized to access.
Prepare standard output for Tellyra
Configure the gateway to publish a standard M3U playlist whose entries point to HTTP or HLS streams. If available, it may also publish XMLTV guide data and catch-up metadata that the playlist describes.
- Keep the playlist and stream addresses private.
- Prefer stable local addresses so the source survives device restarts.
- Do not depend on a gateway's private management API; Tellyra needs only media-facing URLs.
Verify first, then add the playlist
Check the gateway's own status page and play one HLS output from the Apple device on the same network. Once that works, add the gateway's M3U address in Tellyra as a remote playlist and run the source check.
- Confirm the gateway is running before opening Tellyra.
- Test one stream before importing a large list.
- Add XMLTV separately if the gateway supplies it.
- Keep addresses and credentials out of screenshots and support messages.
Keep management private and troubleshoot in order
Do not expose an unauthenticated gateway or its management page directly to the public internet. Restrict management access with your router or firewall. When playback fails, verify the gateway output first, then use Tellyra's source and playback diagnostics.
- Gateway unavailable: check its process, network, and stream conversion.
- Playlist unavailable: confirm its local address from the Apple device.
- Only one item fails: test that output at the gateway before changing Tellyra.
- Tellyra Support cannot repair or administer a self-hosted gateway.