2024-06-18, 07:40 AM
(This post was last modified: 2024-06-18, 07:54 AM by Cognicom. Edited 1 time in total.)
(2024-06-18, 06:31 AM)macnab Wrote: Jellyfin.exe has both an inbound and outbound rule for my private network, all protocols, all ports.
Using http://localhost:8096 is exactly the same. Says Select Server. Huge blue square called DESKTOP-70OJU52. Can't connect.
However, Create new server allowed me to enter the CORRECT IP address. To log in I selected Forgot Password. Response: Please try again within your home network to initiate the password reset process. This is because Jellyfin insists that my IP range is 192.168.0.0/16 when it is 192.168.0.100/16. And of course it just ignores the info in network.xml. Although it does do a syntax check.
192.168.0.0/16 and 192.168.0.100/16 are the same network. In times of old (and among those who deal with networking on a daily basis), the subnet is written as 192.168/16 - to save keystrokes and to make it impossible to misunderstand what it's referring to.
What's the subnet mask in your Windows configuration? I've encountered countless systems where a computer's set to /16 (255.255.0.0) and the router's set to /24 (255.255.255.0) or vice-versa. This situation will always yield mysterious issues.
Also... Try temporarily disabling the Windows firewall entirely - I've a suspicion that using the rule you've created, Windows isn't allowing traffic through to the running (web) process, only to the main Jellyfin executable. If everything runs as it should with the firewall disabled, re-enable the firewall, delete the Jellyfin.exe rules, and create port-based (not application-based) in/out rules for your local network (192.168/16).
Amentis aperi, politicus mortus politicus bonus est!