Unable to access NUC and Nucleus+ servers due to timeout (ref#7E9E7T)

What’s happening?

· I'm having trouble connecting to Roon

What type of connection issue?

· Something else

Describe the issue

Set up new ROCK server on a NUC. Opened in the app as expected, found and played tracks in our local digital collection housed in an external drive connected to the NUC. Realized I needed to back up database from previous server on Nucleus+ to transfer playlists etc. Hooked the N+ back up and got site can't be reached because it times out. Hooked the NUC back up with same result - can't be reached, times out. Tried using Roon app on different computers, tried server address in browser, tried rebooting the router. Same result in all cases, can't be reached, times out. Help!

Describe your network setup

Orbi mesh network

Hi @Kevin_Murnane,

I’ll need a little more descriptive detail of what’s occurring here. This sounds like you’re referring to the URL redirect in the web browser that opens when you log into Roon via single-sign-on. Is this correct?

If that’s the case, try clearing the cookies in your default browser on all devices and disabling any adblockers, PiHoles, or other content blockers that you’ve added to this network or specific devices.

If you’re referring to the Web Administration Interface for the ROCK or the Nucleus+, try using the hostname in your web browser instead of the local IP address. For example, you can type http://rock.local.

As a separate troubleshooting step: Within the Orbi mesh network, enable IGMP snooping if available and make sure “Disable IGMP Proxying” is toggled off. This isn’t necessarily related to the issue, but it will help ensure device discovery moving forward.

Additionally, ensure you follow these steps precisely when migrating RoonServer to ROCK:

There’s an active third RoonServer instance associated with your account on another machine not mentioned in your initial report. Have you installed RoonServer somewhere else in the meantime?

Thank you for addressing my problem so quickly and please forgive me for taking so long to reply. Life outside music happened and had to be dealt with.

The problem was the URL redirect as you surmised. We cleared cookies and have no content blockers. Didn’t solve the problem. IGMP snooping is not an option in the Orbi mesh network; “Disable IGMP Proxying” was already toggled off when the problem appeared.

I tried a few other things and the problem resolved but because after hours of frustration I got away from testing after every change so I don’t know exactly what solved the problem. I think it may have had to do with the third RoonServer instance that I was unaware of until you mentioned it.

The upshot is Roon running on ROCK in a NUC shows marked improvement (fast and snappy with zero delays and higher gain than what we were used to) over the Nucleus+. Only issue that remains is the NUC and the external HDD holding our music that’s connected to it are not visible on our network and I’m working on finding a solution for that now. Again, thank you for your fast response with suggestions for getting our problem solved.

Hi @Kevin_Murnane,

Were you able to figure out what to do here? If not give us a bit more detail on what devices are unable to see the HDD and how you’ve set up your share settings.

Not been successful thus far. Neither the NUC nor its external drive are visible on the network.

Running a private network in Windows 11 with , and all toggled on. The box for is checked.

In Windows Services , , , and are all set to automatic.

Desktop, NUC and router have all been cold booted. Orbi running 5G band.

Do you mean that it is not visible in the Network section of Windows File Explorer? If so, see this post:

\ROCK\Data\ in “Add a network location” didn’t work; \ROCK\Data\ in “Map network drive” did. Being able to get help no matter where you are from people with the necessary expertise who are willing to share their time and knowledge no matter where they are is an extraordinary thing which should never be under-appreciated. Thank you very much.

There should be an error message giving more detail in it. Can you share that with us?

I don’t remember the error message (seen a lot of them today). I just tried to reproduce it but “Add a network location” worked this time. I’m guessing because either (a) there was a typo when I tried it earlier or (b) the location was successfully mapped earlier via “Map network drive”. Sorry I can’t be of more help

Do you still need help or did you resolve the issue?

Problems are solved. Y’all been a tremendous help. Thank you.

We’re glad you were able to resolve your network drive issue!

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.