+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: No servers have been found (/t-solved-no-servers-have-been-found)
No servers have been found - fliberdygibits - 2024-06-18
Just rebuilt my server after more than a year and I'm having a hard time with one thing. When I visit page I get the screen "No servers have been found using the automatic server discovery." with a button to add server. I've seen a lot of comments to clear browsing cache/cookies but I've not only done that but I've tried other browsers (opera and brave) and I've tried a private browsing tab all with the same results.
This is running in a proxmox VM behind NPM and it does the same thing via the URL on the public internet OR via the IP address here locally.
RE: No servers have been found - theguymadmax - 2024-06-18
What server version are you running?
Try disabling IPV6 in the network.xml config file:
<EnableIPv4>true</EnableIPv4>
<EnableIPv6>false</EnableIPv6>
RE: No servers have been found - fliberdygibits - 2024-06-18
Apologies, I'm doing this while making curry and was a bit sparse with information. Running 10.9.6 in an ubuntu 22.04 vm.
RE: No servers have been found - fliberdygibits - 2024-06-18
Also ipv6 was never enabled.... but per some other posts I enabled it then disabled it again to no effect.
RE: No servers have been found - fliberdygibits - 2024-06-18
Figured it out. In proxmox VM > Hardware > Network Device > Firewall=off. Turning off the firewall IN the VM and in the proxmox VM settings to the left isn't enough.
RE: No servers have been found - TheDreadPirate - 2024-06-18
Is that really a "solution" though? Ports 8096/TCP, 1900/UDP, and 7359/UDP need to be open. Turning off the entire firewall is much less than ideal.
RE: No servers have been found - fliberdygibits - 2024-06-18
I have other firewalls in place that allow for those ports. I did not realize that Proxmox snuck this firewall in. Now that I've confirmed it was the cause of my issue I plan to loop back around and evaluate whether I'd like to make use of it. I didn't mean to imply I just blindly shut it off and walked away. For now the whole thing (JF, NPM, Proxmox) is all shut back down until I get time this evening to tinker with it.