+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: SOLVED: Editing network.xml doesn't work (/t-solved-editing-network-xml-doesn-t-work)
Editing network.xml doesn't work - macnab - 2024-06-15
Windows 11 latest
Jellyfin 10.8.13
My PC ip4 is 192.168.1.108
So subnet is 192.168.0.100/16 (Verified in router.)
Logs show Jellyfin trying to use 192.168.0.0/16
Read in a different post to edit network.xml
<LocalNetworkSubnets> and <LocalNetworkAddresses> are empty.
Stopped Jellyfin, edited them to be 192.168.0.100/16
Restarted Jellyfin.
Log still shows 192.168.0.0/16
It does have the server's IP correct.
So Jellyfin seems to be getting the info elsewhere.
EDIT: Completely uninstalled 10.8.13 and installed 10.9.6. Now there isn't a network.xml any more.
RE: Editing network.xml doesn't work - Efficient_Good_5784 - 2024-06-15
(2024-06-15, 07:16 AM)macnab Wrote: <LocalNetworkSubnets> and <LocalNetworkAddresses> are empty.192.168.0.0/16 matches to your desired ip range. The /16 subnet mask means the first 6 numbers will be the same (and treated as part of the same network) and the rest can change to give out IPs for that local network. So 192.168.0.### IP addresses fall in the range Jellyfin is using.
Stopped Jellyfin, edited them to be 192.168.0.100/16
Restarted Jellyfin.
Log still shows 192.168.0.0/16
What is the issue you're trying to solve here? Is it a single or multiple clients that can't connect to your server?
RE: Editing network.xml doesn't work - macnab - 2024-06-17
Trying to get my PC to connect so that I can define my folders, etc.
I get "We're unable to connect to the selected server right now. Please ensure it is running and try again."
Task Manager says Jellyfin.Server is running.
RE: Editing network.xml doesn't work - TheDreadPirate - 2024-06-17
Did you open the Windows firewall during install? If not you need to add a firewall rule. You could also use "http://localhost:8096" to do the setup since localhost doesn't go through the firewall. Regardless, if only localhost is accessible, you need to add a firewall rule for jellyfin.exe.
RE: Editing network.xml doesn't work - macnab - 2024-06-18
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.
RE: Editing network.xml doesn't work - Cognicom - 2024-06-18
(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).
RE: Editing network.xml doesn't work - macnab - 2024-06-18
Subnet masks match.
Disabling the firewall made progress. I deleted the old, incorrect server and selected the, now visible, correct server. When I say Open Jellyfin I just get a black screen.
Created port 8096 rules for both directions and for TCP and UDP.
Situation is the same as for firewall disabled.
Going to try reboot. And maybe reinstall.
RE: Editing network.xml doesn't work - macnab - 2024-06-18
OK. Restarting changed my rules to the app based rules, but at least it connects to the server. Reinstalled as well, but wizardstart still yields only a black screen.
RE: Editing network.xml doesn't work - macnab - 2024-06-18
Basically the series of events was:
Disable firewall
Select (now visible) correct server.
Enable firewall, create port-based firewall rules. These were removed during reinstallation. Somehow this made the installer insert the correct rules.
Install the desktop media player.
@Cognicom Thanks for the help.