Jellyfin stopped allowing local connections suddenly

[radnom]

It'd all been working perfectly fine for a couple weeks, and then suddenly without touching any network settings, Jellyfin settings, Router settings, etc. Jellyfin just stopped allowing connections from my other computers!


Problem: I cannot connect to my Jellyfin server from other computers/devices on the same network.
I do not want remote access. I only want to access my media files from within my house and network.

• Jellyfin version 10.10.3
  
• Hosted on a Windows 10 computer
  
• Connected with a 'private' Ethernet connection
  
• My Windows 10 Firewall has exceptions for Jellyfin.exe and port 8096.
  
• My local IP for my server computer is set to always use the same IP on my router.
  
• I can ping my server computer from my laptop with ping 192.168.xxx.xxx but if I ping using 192.168.xxx.xxx:8096 it fails (not sure if that's meant to work, though).
  
• I don't have a VPN.
  
• Log: https://pastebin.com/azcYDY77
  
• network.xml: https://pastebin.com/RpmgAUZr
  

If I tick 'Allow remote connections to this server' then it works fine again.

However, I don't want remote connections! I want it to be completely local like it was before.

The fact that it works with 'allow remote connections' ticked makes me think it's not Firewall related, but I'm an amateur at networking stuff so I don't really have a clue if that's related.

I'm not sure what changed that now Jellyfin thinks my other devices on the network are considered 'remote' now.

[TheDreadPirate]

Do you have multiple VLANs? Are your other devices on a different subnet? 192.168.2.X? Do you have AP isolation enabled for wireless clients?

I don't see any access attempts in the log you provided. Do you know if your clients are using an IPv6 address when attempting to connect to your server? Since you only have 192.168.1.0/24 as accepted LAN connections.

[wenzelja]

I have found that if I enable IPv6 then I lose all access to my server locally. Un-ticking the "Enable IPv6 functionality" (and a server restart) should work.

That's been one of those questions I've been meaning to ask about this option. Why does enabling IPv6 functionality result in disabling IPv4 access to my server on 192.168.1.XXX:8096, or does it just mean that I can only access it using the local IPv6 address (and do I still use 8096 as the port for IPv6, e.g. XXXX:XXXX:XXXX:XXXX:XXXX:XXXX%XX:8096)? Even though both IPv4 and IPv6 are enabled, based on my experience thus far it would seem that IPv4 is disabled when IPv6 is enabled, even though the Network settings aren't reflecting that reality, and are instead showing both enabled.

[schnappi]

Did your computer go into sleep mode?