Remote Controls Not Showing After Update - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: Remote Controls Not Showing After Update (/t-remote-controls-not-showing-after-update) Pages:
1
2
|
Remote Controls Not Showing After Update - Jukelyn - 2025-01-31 The version of Jellyfin you are running (e.g. 10.8.10) Tested 10.10.3 (works fine), 10.10.4 (works sometimes?), and 10.10.5 (controls no longer present) Your installation method and platform (e.g. Linux Docker, Debian repository, Windows installer, etc.) Docker on Linux A brief description of the issue as your thread subject, using the description for additional important context only if required I just updated from 10.10.3 to 10.10.5 and noticed that when I go to the Administration Dashboard, the remote control feature for active streams is no longer present. I was wondering if this is an issue just on my end of it this is due a bug (or feature removed) from version 10.10.5. When I downgraded from 10.10.5 to 10.10.4, the first time I tested to see if the controls were there, they were. But other times, they were not. A full explanation of what is happening, versus what you expect to happen What I expected were the media controls to be present there. What client(s) you are using and how the issue manifests - Client Roku App streams some media - Client iPhone App streams some media - Me, using the web app the admin dashboard does not show the remote controls anymore. Showing on 10.10.4: Not showing on 10.10.4: Not showing on 10.10.5: RE: Remote Controls Not Showing After Update - Efficient_Good_5784 - 2025-01-31 Have you tried accessing the dashboard from a private window to see if it's a cache issue? RE: Remote Controls Not Showing After Update - Jukelyn - 2025-02-01 (2025-01-31, 08:22 AM)Efficient_Good_5784 Wrote: Have you tried accessing the dashboard from a private window to see if it's a cache issue? Yes. Oddly enough, I downgraded back to 10.10.3 and I get the controls on just one of the numerous current streams. So it doesn't seem to be a version issue after all... I'm pretty lost at this point and am not sure what the issue may be. My configuration has been the same for the last few months besides the update I did to 10.10.5 two days ago. (Screenshot taken in an private window) RE: Remote Controls Not Showing After Update - TheDreadPirate - 2025-02-02 Do you have a reverse proxy? RE: Remote Controls Not Showing After Update - Jukelyn - 2025-02-03 (2025-02-02, 11:52 PM)TheDreadPirate Wrote: Do you have a reverse proxy? Yes, I'm using Nginx. RE: Remote Controls Not Showing After Update - TheDreadPirate - 2025-02-03 Can you share a censored version of your Nginx config? RE: Remote Controls Not Showing After Update - Jukelyn - 2025-02-05 (2025-02-03, 10:43 PM)TheDreadPirate Wrote: Can you share a censored version of your Nginx config? Sure, here it is: Code: # ------------------------------------------------------------ RE: Remote Controls Not Showing After Update - TheDreadPirate - 2025-02-05 Can you share censored versions of these two files, which would contain the info we need. conf.d/include/proxy.conf /data/nginx/custom/server_proxy[.]conf RE: Remote Controls Not Showing After Update - Jukelyn - 2025-02-06 (2025-02-05, 01:39 PM)TheDreadPirate Wrote: Can you share censored versions of these two files, which would contain the info we need. This is the first one, conf.d/include/proxy.conf: Code: [root@docker-90e9b66e15d6:~]# cat /etc/nginx/conf.d/include/proxy.conf and the second one, /data/nginx/custom/server_proxy[.]conf, doesn't seem to exist (?) this is what is in /data/nginx/: Code: [root@docker-90e9b66e15d6:~]# ls -la /data/nginx/ RE: Remote Controls Not Showing After Update - TheDreadPirate - 2025-02-06 Try adding a separate /socket location with identical parameters as proxy.conf plus these two proxy_set_headers. Code: proxy_set_header Upgrade $http_upgrade; I know you have those two in the server block, but I'm trying to find clarification if those headers need to be in the location or not. Also, "Connection" needs to be "upgrade". Yours is currently set to "$http_connection". |