[GH-ISSUE #305] help with Jellyfin Config #268

Closed
opened 2026-02-26 06:31:51 +03:00 by kerem · 4 comments
Owner

Originally created by @palitu on GitHub (Feb 23, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/305

I have jellyfin running in a container (via dockstarter), and it is reverse proxy'd by the letsencrypt container. I am trying to migrate to NPM, but cannot figure out the settings.

Does anyone have a working jellyfin Rproxy that they can help me with?

I have tried the adding a folder, as per the standard instructions, but then the GUI shows, but wont play movies.

This is the config for the letsencrypt nginx rev proxy:

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name jellyfin.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.X valid=30s;
        set $upstream_jellyfin jellyfin;
        proxy_pass http://$upstream_jellyfin:8096;

        proxy_set_header Range $http_range;
        proxy_set_header If-Range $http_if_range;
    }

    location ~ (/jellyfin)?/embywebsocket {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.X valid=30s;
        set $upstream_jellyfin jellyfin;
        proxy_pass http://$upstream_jellyfin:8096;

        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
   }
}

how would i recreate this in NPM?

ta

Originally created by @palitu on GitHub (Feb 23, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/305 I have jellyfin running in a container (via dockstarter), and it is reverse proxy'd by the letsencrypt container. I am trying to migrate to NPM, but cannot figure out the settings. Does anyone have a working jellyfin Rproxy that they can help me with? I have tried the adding a folder, as per the standard instructions, but then the GUI shows, but wont play movies. This is the config for the letsencrypt nginx rev proxy: ``` server { listen 443 ssl; listen [::]:443 ssl; server_name jellyfin.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.X valid=30s; set $upstream_jellyfin jellyfin; proxy_pass http://$upstream_jellyfin:8096; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; } location ~ (/jellyfin)?/embywebsocket { include /config/nginx/proxy.conf; resolver 127.0.0.X valid=30s; set $upstream_jellyfin jellyfin; proxy_pass http://$upstream_jellyfin:8096; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; } } ``` how would i recreate this in NPM? ta
kerem closed this issue 2026-02-26 06:31:52 +03:00
Author
Owner

@jc21 commented on GitHub (Feb 23, 2020):

It should be as simple as this:

jellyfin

where 192.168.0.10 is your upstream ip or hostname.

If you find that some things work in the browser and some don't, you have to inspect the Javascript/Developer tools console of your browser to get more info about why.

<!-- gh-comment-id:590127290 --> @jc21 commented on GitHub (Feb 23, 2020): It should be as simple as this: ![jellyfin](https://user-images.githubusercontent.com/1518257/75121928-9163f200-56e4-11ea-8e4e-b1f530ba3ee2.png) where `192.168.0.10` is your upstream ip or hostname. If you find that some things work in the browser and some don't, you have to inspect the Javascript/Developer tools console of your browser to get more info about why.
Author
Owner

@palitu commented on GitHub (Feb 23, 2020):

Thanks, i will try it as is an give it a go.

<!-- gh-comment-id:590127966 --> @palitu commented on GitHub (Feb 23, 2020): Thanks, i will try it as is an give it a go.
Author
Owner

@palitu commented on GitHub (Mar 2, 2020):

thanks - turns out i also needed a location

image

<!-- gh-comment-id:593170465 --> @palitu commented on GitHub (Mar 2, 2020): thanks - turns out i also needed a location ![image](https://user-images.githubusercontent.com/6634784/75637049-c4673200-5c5e-11ea-9e0f-b93a0cff4cd1.png)
Author
Owner

@bunducafe commented on GitHub (Jul 13, 2020):

It should be as simple as this:

jellyfin

where 192.168.0.10 is your upstream ip or hostname.

If you find that some things work in the browser and some don't, you have to inspect the Javascript/Developer tools console of your browser to get more info about why.

That's what I tried. Without SSL it is working, but with force SSL it quits with "internal error". Any hints?

<!-- gh-comment-id:657401264 --> @bunducafe commented on GitHub (Jul 13, 2020): > It should be as simple as this: > > ![jellyfin](https://user-images.githubusercontent.com/1518257/75121928-9163f200-56e4-11ea-8e4e-b1f530ba3ee2.png) > > where `192.168.0.10` is your upstream ip or hostname. > > If you find that some things work in the browser and some don't, you have to inspect the Javascript/Developer tools console of your browser to get more info about why. That's what I tried. Without SSL it is working, but with force SSL it quits with "internal error". Any hints?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#268
No description provided.