Remote Controls Not Showing After Update

[Jukelyn]

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:

[Efficient_Good_5784]

Have you tried accessing the dashboard from a private window to see if it's a cache issue?

[Jukelyn]

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)
   

[TheDreadPirate]

Do you have a reverse proxy?

[Jukelyn]

Do you have a reverse proxy?

Yes, I'm using Nginx.

[TheDreadPirate]

Can you share a censored version of your Nginx config?

[Jukelyn]

Can you share a censored version of your Nginx config?

Sure, here it is:

Code:

# ------------------------------------------------------------
# jellyfin.domain.tld, jf.domain.tld
# ------------------------------------------------------------



map $scheme $hsts_header {
    https  "max-age=63072000;includeSubDomains; preload";
}

server {
  set $forward_scheme http;
  set $server        "[REDACTED]";
  set $port          [REDACTED];

  listen 80;
#listen [::]:80;

listen 443 ssl http2;
#listen [::]:443;


  server_name jellyfin.domain.tld jf.domain.tld;


  # SSL
  include conf.d/include/[REDACTED]acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate [PATH_REDACTED];
  ssl_certificate_key [PATH_REDACTED];






  # Block Exploits
  include conf.d/include/block-exploits.conf;



  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security $hsts_header always;





    # Force SSL
    include conf.d/include/force-ssl.conf;




proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;


  access_log [PATH_REDACTED]_access.log proxy;
  error_log [PATH_REDACTED]_error.log warn;







  location / {





  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security $hsts_header always;





   
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
   

    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

[TheDreadPirate]

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

[Jukelyn]

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

This is the first one, conf.d/include/proxy.conf:

Code:

[root@docker-90e9b66e15d6:~]# cat /etc/nginx/conf.d/include/proxy.conf
add_header      X-Served-By $host;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Scheme $scheme;
proxy_set_header X-Forwarded-Proto  $scheme;
proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP          $remote_addr;
proxy_pass      $forward_scheme://$server:$port$request_uri;

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/
total 36
drwxr-xr-x 9 root root 4096 Aug 24 03:57 .
drwxr-xr-x 7 root root 4096 Jan 27 01:46 ..
drwxr-xr-x 2 root root 4096 Aug 24 03:57 dead_host
drwxr-xr-x 2 root root 4096 Sep 27 01:13 default_host
drwxr-xr-x 2 root root 4096 Sep 27 01:12 default_www
drwxr-xr-x 2 root root 4096 Jan 27 01:46 proxy_host
drwxr-xr-x 2 root root 4096 Sep  1 19:52 redirection_host
drwxr-xr-x 2 root root 4096 Dec 13 07:11 stream
drwxr-xr-x 2 root root 4096 Nov  4 18:05 temp

[TheDreadPirate]

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;
        proxy_set_header Connection "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".