HTTPS not enabled on reverse-proxied Jellyfin

[francislavoie]

@dzvpn

reverse_proxy 127.0.0.1:8096 127.0.0.1:8920

btw this seems wrong; you shouldn’t have two upstreams like this. Change it to simply:

reverse_proxy 127.0.0.1:8096

@dzvpn

However, the base URL of the server is not /, it’s /jellyfin.

Why not just make sure Jellyfin is configured to use / as its base URL? Why do you need to use a subpath?

Anyway, please read this article which explains many of the caveats:

The "subfolder problem", OR, "why can't I reverse proxy my app into a subfolder?"

Have you ever tried to reverse proxy an app into its own little subfolder of your domain name? Makes things neat, doesn’t it? Using example.com/foo/ for one app, example.com/bar/ for another. If you’re coming here from one of the selfhosted communities, you might be thinking along the lines of example.com/sonarr/, example.com/radarr/ etc. Chances are, you’ve tried some configuration along these lines: example.com { redir /sonarr /sonarr/ handle_path /sonarr/* { reverse_proxy localhost…