· Hello, running Nucleus One server version 2.62, build 1641. I am experiencing odd behavior. I recently switched from COX internet, to gfiber, but I have ruled out that being the issue, although it started since that change. Nucleus one is connected via ethernet, and I can see it in the gfiber web application. This is what is happening. Currently, I am only connecting via a IOS ipad, that is a few years old. This is the only device that is connecting properly as before. My phone will not connect correctly or at all, 9 out of 10 times or more. If I do get it to connect to the roon server, once it goes dormant it will not work. I tried it on my wifes ipad, phone, plus a new Lenovo tab one that I got just as a roon controller, and all of those behave the same way. Here is where it gets strange. I did an operating system reinstall twice by accessing nucleus.one on my ipad's web browser. Once the roon server is back up after the re-install, I can connect my phone (Samsung s25 ultra) and the Lenovo Tab One right away. If I close the roon app in those devices and I bring it right up, they work ok. But, after like 5 minutes, they do not connect anymore. The tab one connects on occasion, but like after 5 - 10 minutes of sitting there on the waiting to connect screen. Later, that connection goes away and I get the waiting to connect screen. Please help, it seems something on the nucleus one is not working correctly as before. Why would only 1 device connect normally, and not others? Why would they connect after the OS re-install, but then now work normally? Any help appreciated, thank you.
Tell us about your home network
· Network is GFiber, with this modem, GFiber Wi-Fi 7 Router, and 2 GFiber Wi-Fi 7 Mesh Extender (GEBE320C). No VPN, no switches. GFiber tried port forwarding, but that did not do anything.
Thanks for reaching out. If the issue happens again, please let us know the exact local time and date so we can look over error logs associated with your account. If you press the Select a different Roon Server button, does the server show up there at all? Are you using multiple networking interfaces on the Roon Server, such as both WiFi and Ethernet? If so, is the behavior the same with just one interface? Also, is this affecting only Android devices, or do other Windows or Mac Remotes connect as expected?
Hello, so this happens all of the time now, except with my older Ipad. I just tried to bring up the roon app on my android phone, Samsung s25 ultra, and I get the waiting for your roon server message. It is currently 2:47 pm on 4/2/26 Phoenix time, which is currently same as PST. The only way I can get this device to connect, is if I do a OS re-install. If i I do that, it will connect right away, but after 5 - 10 minutes, the same thing happens, it wont connect again. I cannot connect with my wife’s iphone 17 pro, or her ipad which is newer. The samsung tab one is android, but it’s last years model, so a bit older. The Samsung tab one does not connect right away, it takes 5 - 10 minutes of it waiting for your roon server, then it connects. This issue does not seem to be related to android or ios, it’s either something changed with my roon nucleus setting during the ISP change, or something in the new network is behaving oddly. The strange thing to me is when I do the OS re-install on my nucleus one, the devices connect right away, but only for a period of time. . So it’s very unreliable right now as only my ipad connects as it should. The only device connected to the ethernet is the roon nucleus one, everything else is on wifi on the same network. If I select a different roon server button on my Samsung phone, it finds an older roon windows instance that is not in use anymore, it does not see the nucleus one at all. Thanks
At 3:21 pm, refreshed my ipad and did a connection to roon server so you can see the only one that is working right now, that is the older ipad. It did connect, takes like 5 - 8 seconds.
From a fresh Roon Server diagnostic report, we can see the issue appears to be related to how your new GFiber Wi-Fi 7 Router and Mesh Extenders are handling network discovery (multicast) traffic between your wireless devices and the wired Nucleus One.
The fact that an OS reinstall provides a temporary fix suggests that a fresh “handshake” is made during the setup process, but the connection is lost once the network’s security or routing table settles into its standard state.
Recent Android and iOS updates often enable “Private DNS” or “Private Relay,” which can mask your device’s identity on the local network, preventing it from seeing the Roon Server.
Android (Samsung S25 Ultra): Go to Settings > Connections > More connection settings > Private DNS and set it to Off.
iOS: Go to Settings > Wi-Fi > [Your Network Info] and ensure Private Wi-Fi Address is toggled off for your home network.
Samsung devices also often put background apps to sleep to save power, which kills the connection to Roon as soon as the app is not in the foreground.
Go to Settings > Apps > Roon > Battery and select Unrestricted (or "Allow background activity").
Since the Nucleus is wired to the main router and your remotes are on Wi-Fi (possibly connected to different mesh extenders), the router may be blocking the discovery protocol between the wired and wireless "segments" of your network.
Test: Move your Samsung phone or Lenovo tablet right next to the primary GFiber router (not the extenders). Turn the device's Wi-Fi off and back on to ensure it connects to the main router. If it connects immediately and stays connected, the issue is with how the Mesh Extenders handle traffic.
Settings: Access your GFiber router settings (via the web app) and look for settings like "IGMP Snooping" or "Multicast Enhancement." If they are off, try turning them on; if they are on, try turning them off.
I’d also check your local subnet. Switching ISPs sometimes results in a "Double NAT" if the new GFiber equipment is acting as a router while another device is also trying to manage the network.
Verify that your Nucleus and your mobile devices all have IP addresses starting with the same first three sets of numbers (e.g., 192.168.1.xxx).
Thank you Benjamin. I tried the settings you suggested and did not help me connect. I did disconnect both extenders, and when I did that and connected to the router, my Samsung phone behaved like the Samsung Tab one does, it took like 6 - 7 minutes to connect, but it did connect. Once I turned the extenders on, no connection, so it is definitely on the side of gfiber. I appreciate the troubleshooting on your side, it helps with figuring out where to look, and it looks like everything is working as it should on the roon side.
Thanks for the update on this, and it’s good to hear you were able to narrow it down to the gfiber extenders. Let us know if we can assist further once you’ve completed your investigation.
Just checking in on this after the network changes you made. Were you able to catch any recent dropout or connectivity timestamps in Roon so we can line them up with the logs? If you have those or any new details from the setup, send them over and we will take another look. If we don’t hear back from you this thread will auto-close shortly, thanks.
Thank you guys, so the Gfiber routers do not allow much in the way of advanced settings. Tried to go to their wifi 6 routers, but encountered the same thing. I bought a tp-link router and an extender, no issues at all. Still on Gfiber, just can use their routers. Thanks for the support.
