SOLVED: Can't see other clients in the "cast to" devices list

[auxym]

I'm not sure what changed recenetly, this used to work 1-2 weeks ago. I have not upgraded my JF server, but the clients (Jellyfin Media Player) might have been, I'm not sure (rolling release distros, I update everything frequently).

• Two instances of Jellyfin Media Player on Linux (one on EndeavourOS, the other is OpenSUSE Tumbleweed)
  
• One is running 1.12.0, the other still on 1.11.1
  
• Both connected to the same JF server (v10.10.6) running in Docker on Truenas, on the same LAN.
  
• I used to be able to click the "Cast To" button in either client, see the other one and being able to cast to it, or remote control
  
• Now, when I click "Cast to" in either client, the list has only two entries: this device, and Google Cast. For what it's worth, casting to my gen2 Chromecast works great.
  
• I have also tried other clients: the web one and Jellyfin Android on a phone, and none of them can see other clients or are seen by it.
  
• The clients do appear in the admin dashboard Devices page
  

Searching led me to this thread: https://forum.jellyfin.org/t-cast-button...light=cast but it concludes that the DLNA plugin is it culprit. I do not have the DLNA plugin installed on the server.

I can try searching logs, but I'm not sure what to look for. Also server logs or JMP logs?

[TheDreadPirate]

DLNA is not related to that function.

Can you describe your network setup? Are you using a reverse proxy for all the clients?

You can also try clearing the JMP cache on both clients.

~/.cache/Jellyfin Media Player
~/.local/share/jellyfinmediaplayer

[auxym]

Nothing special for the clients network-wise. Two machines on a home router wifi. No proxy setup.

The server is running in a docker container and is behind a reverse proxy (nginx), which is running on the same physical machine in another container. The host is on the same LAN as the clients (wire to the router).

I tried removing the folders you mentioned on both clients and restarting JMP, no luck, same result.

[TheDreadPirate]

What network mode is the jellyfin container running in? Host or bridge?

[auxym]

Sorry, I'm not super familiar with docker networking, but I assume bridge mode. It's not using host networking. The port mapping is as follows:

Code:

udp://0.0.0.0:7359:7359
udp://:::7359:7359
tcp://0.0.0.0:30013:8096
tcp://:::30013:8096

nginx proxies the jellyfin.home domain (LAN use only, no public domain) to port 30013 which is the jellyfin web server port.I don't have any proxy setup for port 7359 though, should I?

[TheDreadPirate]

Code:

tcp://0.0.0.0:30013:8096
tcp://:::30013:8096

You cannot do this kind of port redirection when using DLNA/casting. Jellyfin is advertising that it is on port 8096. It is not aware of the redirection. So clients are trying to connect to port 8096 when it should be connecting to 30013. You either need to remove the redirection, if possible, or configure Jellyfin to be directly on port 30013.

[auxym]

Good catch! But unfortunately no luck I updated the port configuration (which was the default provided by Truenas) as follows:

Code:

udp://0.0.0.0:7359:7359
udp://:::7359:7359
tcp://0.0.0.0:8096:8096
tcp://:::8096:8096

And updated the nginx proxy configuration as well. Same result still, I cannot see other clients in "Cast to"

[TheDreadPirate]

And how about when you switch to host networking? Also, is port 7359 open on the host firewall?

[auxym]

Changed it to host networking, deleted all .local/share and .cache JMP folders and restarted both clients: no luck, same issue.

No firewall running on the host (truenas) machine. To my knowledge truenas does not include firewall functionality at all. Running nmap (-sT) from my laptop (one of the clients) also shows port 8096 as open on the host.

Thanks for the help so far troubleshooting this btw

[TheDreadPirate]

Do you have anything in the Published URI field in Dashboard > Networking?