![]() |
Remote Control Devices from Jellyfin - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access) +---- Thread: Remote Control Devices from Jellyfin (/t-remote-control-devices-from-jellyfin) |
Remote Control Devices from Jellyfin - 8bitHero - 2025-04-01 I am running Jellyfin server on a Linux server from Docker. I have it set to host networking... Code: services: The server lists on 192.168.1.2 on my "Trusted" network. I am using Jellyfin on a NVIDIA Shield TV Pro device. It is connected to my "Untrusted/IOT" network at 192.168.3.124 I have the following firewall rules in place... "Allow Return Traffic" is ticked. When I play something from my NVIDIA Shield TV Pro (192.168.3.124) to Jellyfin (192.168.1.2) it works great, except in the Dashboard I do not have the option to control the NVIDIA device. Such as stopping/pausing/sending messages. I was wondering what ports I am missing to make that happen. Thank you! RE: Remote Control Devices from Jellyfin - TheDreadPirate - 2025-04-01 Web sockets are required for device control to function. I don't think your rule would affect just web sockets. However, if you are using a reverse proxy you may need to enable websockets depending on which one you are using. RE: Remote Control Devices from Jellyfin - 8bitHero - 2025-04-01 I am using Caddy but nothing crazy... jellyfin.domain.com { reverse_proxy localhost:8096 } RE: Remote Control Devices from Jellyfin - TheDreadPirate - 2025-04-01 Is the Shield connecting through your domain name? And is caddy also a container? Or installed directly on the host? AFAIK, Caddy automatically supports web sockets for reverse_proxy configs. And if you can connect at all, web sockets should also be going through. So the answers to my initial questions shouldn't really matter..... |