Docker Windows

[treyzer]

I installed a jellyfin container on docker via this tutorial: https://www.youtube.com/watch?v=CMFR-TYLWv8&t=331s (also planning on using the caddy/cloudflare part of it as well)
Docker and the ports jellyfin is running on are both passed through my windows firewall. ports are open for the pc as well but that will be used later for caddy.
Docker reports jellyfin as running fine and gives ports its running on.     but it is unable to connect to localhost:8096(or 8920)    
other devices on the network cannot reach the IP:8096 address either.
also - docker reports it as running fine (also compose file gives no errors):    
docker-compose.yml:    

any ideas or guidance? I have been working with the author of the tutorial and we are both running out of ideas. note: it works fine for him and loads just fine but for me it is unable to connect. so I assume there is a firewall restriction in someway but cannot find one. if none then I will be transitioning to a baremetal on windows instead of docker

[TheDreadPirate]

Which IP are you using? I see two LAN IPs in that startup log. Also, the ports section is not used when in host networking mode.

Also, what is the host OS?

[treyzer]

my apologies - had submitted this last night before bed (who knows, maybe it would start working. it didnt)

My PC static IP is 192.168.1.71. Its entirely possible that we were overlooking things due to sleep so if you notice an issue then it absolutely could be something as simple as an IP conflict.
If I remove those ports mentioned in the compose, from it - the container is made and starts but doesnt run on any ports (literally the section under the container that would show the ports is blank). If I leave them in then it runs on the ports but says " jellyfin Published ports are discarded when using host network mode" so they seem to be discarded and thus shouldn't make a difference.

What I am assuming is happening is that there is an IP conflict (like you mentioned) and its starting on that, then discarding the ports related to my actual IP

---

localhost:8096 doesn't load either (even clicking on them in docker doesn't load it) so yeah looks like the wrong IP could def be being configured

[treyzer]

my entire LAN subnet for reference is 192.168.1.1-.254 (.254 is router, .71 is set to this PC both in Windows and router

[TheDreadPirate]

I just noticed, this is in WSL. And the subnet you specified aren't the IPs in the Jellyfin log.

192.168.65.3
192.168.65.6

[treyzer]

where can I specify those? not currently at my desk (work) and just glancing through the compose - they don’t seem to be referenced plainly

[TheDreadPirate]

I'm just not sure why there are as many addresses as there are. In a bridge setup there are typically two or three. The bridge network IP, the IPv4 loop back and, if IPv6 is enabled, an IPv6 loop back.

You have the IPv4 loop back, a bridge network IP, and what looks like two LAN IPs.

Do you have a VPN running on this server?

[treyzer]

I do not. This is a fresh windows 11 install with only docker (with caddy), firefox, discord, and sublime text installed. I’ve also made the appropriate inbound firewall rules for the ports these run on.

[TheDreadPirate]

Let's backup a bit. Is there any particular reason you are running Jellyfin in WSL instead of directly on Windows?

[treyzer]

Just wanted to try it out - if I’m unable to figure out the issue then I’ll be doing bare windows instead. Which is what i’m currently leaning towards