[Issue]: Remote Control / Display Mirror not working

Please describe your bug

Ever since the update to 10.9 (currently 10.9.6) the remote control feature no longer works. Feels like its a repeat of #496 all over again. It used to work in 10.8.

My use case is, I like to play media on jellyfin-media-player on desktop, and control it via my mobile phone from the couch / bed.

Here's how the UI looks like on the mobile, while something is playing on the desktop. The pause/play button works, as does the volume slider and the mute button. Seek functionality does not work.

Reproduction Steps

Play something on jellyfin
Try remote control from android app
Be sad that it doesn't work :(

Jellyfin Version

10.9.0

if other:

No response

Environment

- OS: Debian 12
- Linux Kernel: 6.1.0
- Virtualization: none
- Clients: jellyfin-media-player 1.11.1 / jellyfin android 2.6.1
- Browser: nil
- FFmpeg Version: Server: 6.0.1 / Client: 7.0.1
- Playback Method: Direct play
- Hardware Acceleration: Server: none / Client: VAAPI
- GPU Model: RX7600
- Plugins: ??
- Reverse Proxy: nginx
- Base URL: none
- Storage: Local

Jellyfin logs

Found this to be quite interesting: 192.168.0.103 is my mobile phone from which I try to remote control

[2024-06-23 15:48:19.505 +02:00] [INF] WS "192.168.0.103" request
[2024-06-23 15:48:28.276 +02:00] [WRN] Failed to process WebSocket message
MediaBrowser.Controller.Authentication.AuthenticationException: Only admin users can subscribe to session information.
   at Jellyfin.Api.WebSocketListeners.SessionInfoWebSocketListener.Start(WebSocketMessageInfo message)
   at MediaBrowser.Controller.Net.BasePeriodicWebSocketListener`2.ProcessMessageAsync(WebSocketMessageInfo message)
   at Emby.Server.Implementations.HttpServer.WebSocketManager.ProcessWebSocketMessageReceived(WebSocketMessageInfo result)
   at Emby.Server.Implementations.HttpServer.WebSocketConnection.ProcessInternal(PipeReader reader)

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

Code of Conduct

[X] I agree to follow this project's Code of Conduct

jellyfin / jellyfin