You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not 100% sure which of those settings or both are needed to prohibit public http use, but none of them are mentioned in any reverse proxy example I was looking through. But anyhow, I suggest that 2 things are added to every reverse proxy page:
Make sure jellyfin is bound to localhost only (Settings->Networking->Bind to local network address: "127.0.0.1")
Set "Known proxies" to your domain. (Settings->Networking->Known proxies: "jellyfin.example.com")
You also need to restart jellyfin after that.
If those things are not set, jellyfin will continue to server content via the public IP and its HTTP port (default 8096) via HTTP. You can check this simply by setting it up like described in the docs with the two settings above left to their default value and then clicking on a log. It ill open in a browser window with http via the internal port. Of course this will only work if there is no firewall in between preventing this.
If you think this is a correct assumption I can prepare a pull request for some changes.
The text was updated successfully, but these errors were encountered:
I am not 100% sure which of those settings or both are needed to prohibit public http use, but none of them are mentioned in any reverse proxy example I was looking through. But anyhow, I suggest that 2 things are added to every reverse proxy page:
You also need to restart jellyfin after that.
If those things are not set, jellyfin will continue to server content via the public IP and its HTTP port (default 8096) via HTTP. You can check this simply by setting it up like described in the docs with the two settings above left to their default value and then clicking on a log. It ill open in a browser window with http via the internal port. Of course this will only work if there is no firewall in between preventing this.
If you think this is a correct assumption I can prepare a pull request for some changes.
The text was updated successfully, but these errors were encountered: