Https acces, local time out

#1

Hello,
I have a problem with https access. I installed Jellyfin as a docker on a Synology NAS.
I have no problem accessing http://192.168.0.42:8096 at my jellyfin server, but impossible via https://192.168.0.42:8920 (time-out connection)

An idea ?
Thank you

#2

How did you set up the SSL? Did you use a Reverse Proxy or add a certificate to Jellyfin?

We don’t include a certificate by default, so this needs some “first time setup”.

#3

Thank you for your reply.
I chose the reverse proxy option, I created an ngnix container to solve the problem.

#4

Hello,

Is it normal that in the activity of the server, it is impossible for me to know the real IP address of the person who connects? Instead, I have the IP address of my proxy appearing!

Ngnix Proxy :

server {
listen 8080;
server_name _;

location / {
    # Proxy main Jellyfin traffic
    proxy_pass http://192.168.0.42: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://192.168.0.42: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;
}

}

Proxy DSM :