Another user jumping over from ErsatzTV here and I'm setting up Tunarr (1.2.1) on an Unraid docker with Plex. I've followed all the tutorials and read all the manuals but still can't get my station to play (getting the circle on the gray screen through the Watch Channel option and also tried through Plex Live TV). I've imported my libraries, created schedules and I'm seeing the programming on my schedule (both through Tunarr and Plex Live TV) and almost positive it's a transcoding issue but after all the tweaking I've tried at this point I'm scratching my head on what might be the issue.
#Channels not playing
gusty loom
gray echo
Streaming issues are best debugged with the following:
- details about your setup, hardware, and transcode config
- Full tunarr debug level logs
- Attempt to reproduce the issue in a simpler player like VLC (before moving to more complex players with known issues, like Plex)
gusty loom
Thanks, What is the perferred way to post logs?
gray echo
generally they're small enough to post directly here
gusty loom
Here you go:
Host OS: Unraid 7.1.2
Tunarr version: 1.2.1
Install type: Docker on Unraid
Plex version: 4.159.0
Client used to test: Plex web / Firestick / Tunarr Web
CPU: 12th Gen Intel® Core™ i7-12700F @ 2079 MHz
GPU: Nvidia 12th Gen Intel® Core™ i7-12700F @ 2079 MHz
RAM: 32 GiB DDR5
Tunarr container settings:
- Network type: bridge
- Port mapping: 8000:8000
- tmpfs/transcode mount: /transcode:size=8g / /transcode, 8G]
- Appdata/config path: /mnt/user/appdata/tunarr
Tunarr transcoding settings:
- FFmpeg transcode path: /transcode
- Stream mode: MPEG-TS
- Hardware acceleration: [NVIDIA (CUDA)]
- Audio mode: AAC
Problem:
- Channel starts but does not play / spins / errors in Plex
- Happens on all channels
- Happens in Tunarr direct stream, Plex & VLC
Log attached
I also tried in VLC with no luck.
gray echo
i think these logs are truncated.
also you're saying you set the channel stream mode to mpegts? why not use HLS?
gusty loom
Ah, here's the updated version (sorry, new to this)
Host OS: Unraid 7.1.2
Tunarr version: 1.2.1
Install type: Docker on Unraid
Plex version: 4.159.0
Client used to test: Plex web / Firestick / Tunarr Web
CPU: 12th Gen Intel® Core™ i7-12700F @ 2079 MHz
GPU: Nvidia 12th Gen Intel® Core™ i7-12700F @ 2079 MHz
RAM: 32 GiB DDR5
Tunarr container settings:
Network type: bridge
Port mapping: 8000:8000
tmpfs/transcode mount: /transcode:size=8g / /transcode, 8G]
Appdata/config path: /mnt/user/appdata/tunarr
Tunarr transcoding settings:
FFmpeg transcode path: /transcode
Stream mode: HLS
Hardware acceleration: [NVIDIA (CUDA)]
Audio mode: AAC
Problem:
Channel starts but does not play / spins / errors in Plex
Happens on all channels
Happens in Tunarr direct stream, Plex & VLC
LOG ATTACHED
slim ferry
Just to jump in a bit..I also am not able to playback any channels, haven't in awhile i believe. At least not on any Plex platform, which is kinda the point, lol. If i hit "Watch Channel" within Tunarr webui it works perfectly fine.
gusty loom
Just to jump in a bit..I also am not able to playback any channels, haven't in a...
Mine will show up in the Plex program guide, and I see the schedule in Tunarr, but won't play on Plex or the web UI, so I'm thinking it has to be an encoder settings issue.
gray echo
sorry, this one fell by the wayside, let me take a look
"message": "connect EHOSTUNREACH 10.0.0.237:32400: connect EHOSTUNREACH 10.0.0.237:32400",
problem here is that your container cannot communicate with Plex
unsure how your Plex is setup
Plex generally uses host networking, if running in a container. you can run it in bridge. if you are running Plex in bridge, then the networks for the Plex and Tunarr containers need to be made aware of each other
gusty loom
Thanks. Right now my setup is:
Host OS: Unraid 7.1.2
Tunarr: Docker container (bridge network, port 8000)
Plex: Also running on Unraid (I believe using host networking)
Tunarr is able to see my Plex libraries and metadata, but in the logs I’m noticing things like:
plexFilePath: null
plexRatingKey: null
and playback fails in:
Tunarr direct stream
VLC
Plex clients
So it looks like it can partially connect to Plex, but not fully resolve or stream the media.
Based on your suggestion, I suspect this may be a networking mismatch between bridge and host.
I think I might try:
switching Tunarr to host networking
reconnecting Plex in Tunarr using http://127.0.0.1:32400 (or server IP)
Does that sound like the right direction, or should I instead be putting both containers on the same custom bridge network?
pliant flame
Not to derail the thread but your GPU says Nvidia Intel Core I7. That doesn’t make any sense to me since an intel CPU would use integrated graphics. Also, the F variant of Intel CPUs don’t have an integrated graphics.
gray echo
Just to jump in a bit..I also am not able to playback any channels, haven't in a...
happy to take a look at your logs separately but this looks like a networking issue on the OP's setup
i wouldn't worry about the plexFilePath/plexRatingKey fields, these are deprecated and unused. the issue is what i mentioned above -- for whatever reason your Tunarr container cannot reach the configured Plex host at 10.0.0.237:32400 (via https://10-0-0-237.86b669c488e5495da606f80f6e20f2af.plex.direct:32400)
gusty loom
Ah, okay. What would be the best way to remedy this?
pliant flame
What network do you have your tunarr container on in Unraid?
gusty loom
What network do you have your tunarr container on in Unraid?
My Tunarr container is running on bridge networking in Unraid (8000:8000).
My Plex container is running on host networking, so I’m wondering if that mismatch is preventing proper communication between the two.
gray echo
In general, outbound comm from bridge containers (tunarr hitting a LAN IP should work). Inbound (other host hitting the network internal to the docker container) ofc won’t work (have to use the port mapping)
I’m unsure why your tunarr instance is unable to hit your plex server though, but the error is pretty clear in that regard - it’s a networking issue of some sort
gusty loom
Is that something outside of Plex and Tunarr (something in Unraid or Docker?)
pliant flame
Bridge and host should be able to talk just fine in Unraid
gusty loom
Bridge and host should be able to talk just fine in Unraid
HMMM, any ideas of what I could do to fix this? I'm dying to try this software out 🙂
pliant flame
It just kind of worked out of the box. I guess what you could do is open the console on plex and try and ping tunarrs address to see if they can even see each other
gusty loom
It just kind of worked out of the box. I guess what you could do is open the con...
I can reach Tunarr on port 8000 from the Unraid host, and Tunarr returns an HTTP 404 for /api/health rather than a connection error. So the container is up and reachable. That makes me think the problem is no longer basic host-to-container connectivity, but something more specific in Tunarr ↔ Plex communication or stream generation.
pliant flame
I can reach Tunarr on port 8000 from the Unraid host, and Tunarr returns an HTTP...
The only real issues I’ve ever run into with Tunarr is 10 bit HEVC incompatibility with QSV. If the two containers can talk to each other I don’t think anything else by default would stop their connections
gusty loom
Is there any way I can uninstall and install the Tunarr docker to make it work?
gusty loom
Tried uninstalling and re-installing with no luck. What else can I try?
gusty loom
I could really use some help. I've tried everything I can think of and still can't get it to work.
gray echo
ok, taking a step back here.
Tunarr is connected to your Plex with the host https://10-0-0-237.86b669c488e5495da606f80f6e20f2af.plex.direct:32400, per the logs
this is resolving to the IP address 10.0.0.237. first question is this the correct IP address for Plex
second, something I would try, it entering the Tunarr docker container while it is running and trying to see what it can / cannot hit via some simple commands. you can enter a running container with a command like docker exec -it tunarr /bin/bash. from there i would try some basic commands to see what the container can communicate with