2023-08-11, 09:28 AM
I appear to be missing the information button from active devices within the dashboard when using Jellyfin via my NGINX reverse proxy.
I have stumbled across this post however there's no details as to what exactly was wrong with the configuration.
https://www.reddit.com/r/jellyfin/commen...dashboard/
I have attached my config below, it is not exactly the same as the one in the official instructions however if I use that, it will straight up not work and just black screen me any client. Not only that but the instructions tell you to uncomment the SSL lines from the sample config as well as running a certbot NGINX config which inserts its own SSL lines resulting in duplicates and a broken config.
Anyway, can anyone help me work out what's wrong here? Running 10.8.10 on Ubuntu x64. Nginx 1.18.0.
I have stumbled across this post however there's no details as to what exactly was wrong with the configuration.
https://www.reddit.com/r/jellyfin/commen...dashboard/
I have attached my config below, it is not exactly the same as the one in the official instructions however if I use that, it will straight up not work and just black screen me any client. Not only that but the instructions tell you to uncomment the SSL lines from the sample config as well as running a certbot NGINX config which inserts its own SSL lines resulting in duplicates and a broken config.
Anyway, can anyone help me work out what's wrong here? Running 10.8.10 on Ubuntu x64. Nginx 1.18.0.
Code:
server {
server_name MYDOMAIN.COM;
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 block for /web - This is purely for aesthetics so /web/#!/ works instead of having to go to /web/index.html/#!/
location ~ ^/web/$ {
# Proxy main Jellyfin traffic
proxy_pass http://$jellyfin:8096/web/index.html/;
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;
}
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 X-XSS-Protection "1; mode=block";
add_header X-Content-Type-Options "nosniff";
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/MYDOMAIN.COM/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/MYDOMAIN.COM/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 = MYDOMAIN.COM) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80;
server_name MYDOMAIN.COM;
return 404; # managed by Certbot
}