SOLVED: Bind to 8096 error

[browbeat7900]

Hi all,

I am currently running jellyfin on an OMV server running in a docker instance in portainer and a cloudflare tunnel pointing to my server. I currently am having a problem where after starting up my tunnel and trying to access my server via the tunnel, suddenly the server couldn't be accessed and I keep receiving the error "curl: (7) Failed to connect to localhost port 8096 after 0 ms: Couldn't connect to server" I've tried running ss to see what is listening on port 8096 but I can't see anything when the container is down and when it is up it shows something is listening (i assume jellyfin trying to attach?). I found a similar problem someone was having on reddit and they solved it by running "chown -R me:me /run/media/me/datapartition/Docker/config" which I tried but didn't work because my run directory for whatever reason doesn't have a media directory.

Any help with this is incredibly appreciated. This is the third time having to rebuild the entire server because of some weird error like this, and I'd like to not have to run settup again.

[Efficient_Good_5784]

Using a Cloudflare tunnel for Jellyfin is against Cloudflare's terms of service.

https://jellyfin.org/docs/general/community-standards/

Do not suggest, encourage, or discuss configurations that may violate the Terms of Service (TOS) of any other platforms. Jellyfin can interface with multiple external services, both internally (e.g. Metadata providers) and by user configuration, each of which has its own requirements and TOS to protect itself. We do not want Jellyfin or its community to develop a reputation for facilitating circumvention or breaking of other services' TOSes or be seen as a problematic member of the wider community. The exact nature of these violations is subject to interpretation on a case-by-case basis based on the service in question and the discussion, and this rule is designed to bring attention to the issue. As a concrete example, the Cloudflare Terms Of Service forbid video streaming behind a normal Cloudflare tunnel; thus, suggesting a user run their instance in this way is a violation of this rule.

Therefore, if it's determined that your issue is stemming from Cloudflare's tunnel, we will not offer much support.

[browbeat7900]

Thank you, was not aware of the TOS issue. When not using tunnel though I still have the port binding issue is there any way to solve this so that I can access my jellyfin through only my local network (without using tunnel since this is against TOS)?

[TheDreadPirate]

Are you using host or bridge networking?

[browbeat7900]

I've been using bridge, but I decided to completely uninstall jellyfin from my machine and delete all volumes that portainer had created (there were several duplicate volumes). Reinstalling and going through initial settup again solved the issue. Thank you for the assistance and information all.