SOLVED: Can't connect to local server

[everydaydealer]

Hello everyone.. google search led me here. i have pretty complex setup in my opinion but still i wanted your help.

1. OPNSENSE firewall and WAN - have adguard and unbound
2. jellyfin server is ON LAN 192.168. series
3. WIFI router is a dump AP so my wifi clients also in 192.169.x series

jellyfin server is accesible in my iphone app, mac browser and ofcourse local server browser.

but not working in Roku and firetv. Server is discovered in those apps automatically but while connecting getting connection error / timeout.

any help to resolve ?

[TheDreadPirate]

Hello everyone.. google search led me here. i have pretty complex setup in my opinion but still i wanted your help.

1. OPNSENSE firewall and WAN - have adguard and unbound
2. jellyfin server is ON LAN 192.168. series
3. WIFI router is a dump AP so my wifi clients also in 192.169.x series

jellyfin server is accesible in my iphone app, mac browser and ofcourse local server browser.

but not working in Roku and firetv. Server is discovered in those apps automatically but while connecting getting connection error / timeout.

any help to resolve ?

Please start a separate thread.  Share your server logs in the new thread.

[Pegasus185]

Yes, I checked Windows Defender Firewall after your very first response. I messed around there and at first there wasn't improvement, but either it took a reboot or a restart of Jellyfin to get results. Yes there are the 4 rules and both Private rules UDP and TCP are enabled and things are working. I'm not sure why that didn't work out of the box but whatever.

I have the complex network setup because a) I had extra routers cast off by local school and b) I set up an internal network for guests on wifi and an internal/internal network for me and mine. Lots of fun.

I just had this problem after an upgrade to Jellyfin 10.9.7. I could not connect to the server from two separate clients on the local network (Swiftfin iOS) and Tizen client (Samsung TV). I could only connect from the local machine, and even then, interestingly only from "localhost:8096" or one of the local IP addresses (I have 2 NICs), even though the server was supposedly listening on 0.0.0.0

The thing that resolved the inability to connect was to explicitly change the Windows Defender Firewall Inbound rules to be explicitly separate "Private" type. Previously the type was set to all of "Domain", "Private" and "Public" at the same time.

No, I don't understand why that would be a problem, but that seemed to be the fix for me.