Closed miguelarios closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
This is not a container or jellyfin issue. You can ask for help from NPM devs, or you can ask in our discord for community help.
Jellyfin works with our reverse proxy solution SWAG, with the built in proxy conf. Here's a helper document on 502 errors: https://docs.linuxserver.io/general/swag#502
Jellyfin works with our reverse proxy solution SWAG, with the built in proxy conf. Here's a helper document on 502 errors: https://docs.linuxserver.io/general/swag#502
The link did it. Thanks. Just erased the proxy host and redid it. It must have been a caching thing.
Is there an existing issue for this?
Current Behavior
I am getting a 502 error when in my rev proxy (NginxProxyManager) i only have container name and 8096 as port and I'm using a custom bridge network called "proxy-net"
Expected Behavior
be able to access jellyfin webUI through rev proxy without exposing a container port to host since I have a custom bridge network.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation