github-actions[bot]
commented
3 years ago Closed jmbell128 closed 3 years ago
github-actions[bot]
commented
3 years ago 
mholt
commented
3 years ago This is happening to me too, but on WAN. 10.7.0 and 10.7.1.
jmbell128
commented
3 years ago My issue was with the whitelist. I didn't think when I set it up that I added a whitelist since I didn't have remote access enabled, but I did a quick check and it turns out I did. For anyone else that is having a similar issue, check the network.xml in the config directory and check to see if
`
` has anything. If it does, delete the ip address between the string tags.
This is a basic working network.xml file:
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<EnableUPnP>false</EnableUPnP>
<PublicPort>8096</PublicPort>
<UPnPCreateHttpPortMap>false</UPnPCreateHttpPortMap>
<UDPPortRange />
<EnableIPV6>false</EnableIPV6>
<EnableIPV4>true</EnableIPV4>
<EnableSSDPTracing>false</EnableSSDPTracing>
<SSDPTracingFilter />
<UDPSendCount>2</UDPSendCount>
<UDPSendDelay>100</UDPSendDelay>
<IgnoreVirtualInterfaces>false</IgnoreVirtualInterfaces>
<VirtualInterfaceNames>vEthernet*</VirtualInterfaceNames>
<GatewayMonitorPeriod>60</GatewayMonitorPeriod>
<TrustAllIP6Interfaces>false</TrustAllIP6Interfaces>
<HDHomerunPortRange />
<PublishedServerUriBySubnet />
<AutoDiscoveryTracing>false</AutoDiscoveryTracing>
<AutoDiscovery>true</AutoDiscovery>
<PublicHttpsPort>8920</PublicHttpsPort>
<HttpServerPortNumber>8096</HttpServerPortNumber>
<HttpsPortNumber>8920</HttpsPortNumber>
<EnableHttps>false</EnableHttps>
<CertificatePath />
<CertificatePassword />
<EnableRemoteAccess>false</EnableRemoteAccess>
<BaseUrl />
<LocalNetworkSubnets>
<string></string>
</LocalNetworkSubnets>
<LocalNetworkAddresses />
<RequireHttps>false</RequireHttps>
<RemoteIPFilter />
<IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist>
<KnownProxies />
</NetworkConfiguration>@mholt i don't know what's going on with the WAN stuff. It could be a similar issue or it could be a reverse proxy issue from what I read in the opened issues at the official jellyfin and jellyfin-web repos. I would check the config.json for jellyfin-web against https://github.com/jellyfin/jellyfin-web/blob/master/src/config.json That seems to have helped others here: https://github.com/jellyfin/jellyfin-web/issues/2493 I hope that helps. For now I'm closing this issue since it's an issue with jellyfin itself, not linuxserver's container image.
roelofz
commented
3 years ago I also had this issue, took me a lot of investigation as the networks were filled in correctly. Hope the new release will be available soon for Ubuntu (10.7.1).
liuweilhy
commented
2 years ago My issue was with the whitelist. I didn't think when I set it up that I added a whitelist since I didn't have remote access enabled, but I did a quick check and it turns out I did. For anyone else that is having a similar issue, check the network.xml in the config directory and check to see if
<LocalNetworkSubnets> <string></string> </LocalNetworkSubnets>has anything. If it does, delete the ip address between the string tags.This is a basic working network.xml file:
<NetworkConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <EnableUPnP>false</EnableUPnP> <PublicPort>8096</PublicPort> <UPnPCreateHttpPortMap>false</UPnPCreateHttpPortMap> <UDPPortRange /> <EnableIPV6>false</EnableIPV6> <EnableIPV4>true</EnableIPV4> <EnableSSDPTracing>false</EnableSSDPTracing> <SSDPTracingFilter /> <UDPSendCount>2</UDPSendCount> <UDPSendDelay>100</UDPSendDelay> <IgnoreVirtualInterfaces>false</IgnoreVirtualInterfaces> <VirtualInterfaceNames>vEthernet*</VirtualInterfaceNames> <GatewayMonitorPeriod>60</GatewayMonitorPeriod> <TrustAllIP6Interfaces>false</TrustAllIP6Interfaces> <HDHomerunPortRange /> <PublishedServerUriBySubnet /> <AutoDiscoveryTracing>false</AutoDiscoveryTracing> <AutoDiscovery>true</AutoDiscovery> <PublicHttpsPort>8920</PublicHttpsPort> <HttpServerPortNumber>8096</HttpServerPortNumber> <HttpsPortNumber>8920</HttpsPortNumber> <EnableHttps>false</EnableHttps> <CertificatePath /> <CertificatePassword /> <EnableRemoteAccess>false</EnableRemoteAccess> <BaseUrl /> <LocalNetworkSubnets> <string></string> </LocalNetworkSubnets> <LocalNetworkAddresses /> <RequireHttps>false</RequireHttps> <RemoteIPFilter /> <IsRemoteIPFilterBlacklist>false</IsRemoteIPFilterBlacklist> <KnownProxies /> </NetworkConfiguration>@mholt i don't know what's going on with the WAN stuff. It could be a similar issue or it could be a reverse proxy issue from what I read in the opened issues at the official jellyfin and jellyfin-web repos. I would check the config.json for jellyfin-web against https://github.com/jellyfin/jellyfin-web/blob/master/src/config.json That seems to have helped others here: jellyfin/jellyfin-web#2493 I hope that helps. For now I'm closing this issue since it's an issue with jellyfin itself, not linuxserver's container image.
I met the same problem. When I visit my Jellyfin container behind Nginx, I got a web with "Select Server". Then I check the file network.xml in config, and found that the key line is:
<LocalNetworkSubnets />
I changed it to:
<LocalNetworkSubnets> <string></string> </LocalNetworkSubnets>
Then I restart jellyfin. It works well now.
Thank you!
cmcraes
commented
2 years ago Had this same issue, this solved it! FWIW I was running jellyfin in a container alongside ubound for the first time when this error occured, and I suspect it is related
Shokyuxx
commented
1 year ago Hi, I have the same issue. I just started working with Jellyfin and Linux for that matter. I am running Jellyfin in a Proxmox LXC container on Ubuntu 22.04. How can I find the config folder and the specific network.xml you are referring to? Thank you for helping a noob :-)
stake25
commented
1 year ago I seem to be having this same problem. Although I change the <LocalNetworkSubnets /> to <LocalNetworkSubnets> <string></string> <LocalNetworkSubnets> and still have not seen a solution on this. I am using a docker container on ubuntu server
I apologize if this is a duplicate or if this needs to be reported to jellyfin. If that's the case let me know and I'll do that. I've read of similar things happening to containers that are web facing behind a reverse proxy. I don't do that. My container only serves my LAN. For reference These are the issues I've read through that seem similar/related:
https://github.com/jellyfin/jellyfin-web/issues/2508
https://github.com/jellyfin/jellyfin/issues/5575
https://github.com/jellyfin/jellyfin-web/issues/2493
and here is a pull request that may be related:
https://github.com/jellyfin/jellyfin/pull/5495
Expected Behavior:
Current Behavior:
Navigate to web interface Presented with the Select a Server page Input server-ip:port Click Connect Connection Error: We're unable to connect to the selected server right now. Please ensure it is running and try again.
Steps to Reproduce
Update to 10.7.1
Environment
OS: Ubuntu 18.04 (Planning an upgrade to 20.04 this coming weekend, or sooner if that's the cause) CPU architecture: x86_64 How docker service was installed: apt install Command used to create docker container (run/create/compose/screenshot)
docker-compose.yaml:
/usr/share/jellyfin/web/config.json:
Docker logs
docker inspect -f '{{ index .Config.Labels "build_version" }}' jellyfin
Linuxserver.io version:- 10.7.1-1-ls16 Build-date:- 2021-03-22T02:00:04+00:00docker logs -f jellyfin
Edited: formating