SOLVED: Jellyfin does not trancscode 4K HEVC in web player

[bioblatt]

still the same issue

[TheDreadPirate]

I'm sorry if you've answered this. There are like 3 threads with similar issues.

What browser are you using and what version?

[bioblatt]

No problem I'm really thankful for your great support.

I'm using Firefox 128.0 (64-Bit) on Windows 10 but it's also not working on my Android phone (Android 13) Jellyfin version 2.6.2 with the default Web player. The integrated player works fine.

[TheDreadPirate]

Are you using a reverse proxy?

[bioblatt]

Yes, I use Nginx as a reverse proxy.

Here's my config:

Code:

server {
      server_name my_domain;

      access_log /var/log/nginx/jellyfin.access;
      error_log /var/log/nginx/jellyfin.error;

      set $jellyfin 127.0.0.1;

      location / {
          proxy_pass http://127.0.0.1:8096;
          proxy_set_header Host $host;
          proxy_set_header X-Real-IP $remote_addr;

          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
          proxy_set_header X-Forwarded-Proto $scheme;
          proxy_set_header X-Forwarded-Protocol $scheme;
          proxy_set_header X-Forwarded-Host $http_host;

          # Disable buffering when the nginx proxy gets very resource heavy upon streaming
          proxy_buffering off;
      }

      location /socket {
          # Proxy Jellyfin Websockets traffic
          proxy_pass http://$127.0.0.1:8096;
          proxy_http_version 1.1;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection "upgrade";
          proxy_set_header Host $host;
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
          proxy_set_header X-Forwarded-Proto $scheme;
          proxy_set_header X-Forwarded-Protocol $scheme;
          proxy_set_header X-Forwarded-Host $http_host;
      }

        # Security / XSS Mitigation Headers
        #add_header X-Frame-Options "SAMEORIGIN";
        add_header Cross-Origin-Resource-Policy "cross-origin" always;
        add_header X-XSS-Protection "1; mode=block";
        add_header X-Content-Type-Options "nosniff";

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/my_domain/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/my_domain/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = my_domain) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


      listen 80;
      server_name my_domain;
    return 404; # managed by Certbot


}

[TheDreadPirate]

For testing, can you set X-XSS-Protection from "1; mode=block" to "0". Our documentation says to not enable it, period.

Code:

# Security / XSS Mitigation Headers
    # NOTE: X-Frame-Options may cause issues with the webOS app
    add_header X-XSS-Protection "0"; # Do NOT enable. This is obsolete/dangerous
    add_header X-Content-Type-Options "nosniff";

Reload nginx and try again.

[bioblatt]

Done. Made no difference.

[bioblatt]

Anything else I can try?

[TheDreadPirate]

You've got me stumped. Are you using any extensions in the browser?

[bioblatt]

Yes but like I said, this also happens on the android app.