· Roon is slow, freezing or won’t start
· Roon is stuck updating or installing
· Roon nucleus updating but get looking for your Roon server message
· Unknown
Hey @matthew_randall,
Thanks for the screenshot and welcome to the forum! Are you still able to access the Nucleus Web UI? Is there any change in behavior if you reboot the Nucleus, press the power button once, wait for it to turn off, then press the power button once again? We’d also like to know what your network setup looks like, including the model and manufacturer of your router, switches, and any other networking gear. Let us know the above and we can continue from there, thanks!
Hi @matthew_randall,
Thanks for the additional information!
If you haven’t yet, I’d temporarily bypass the switch and see if you can temporarily connect your Nucleus directly to your primary router.
Reboot everything, and we’ll attempt to enable diagnostic mode for your Nucleus once this is completed.
Thank you! 
I suppose you are trying to connect from an iPad, yes?
Suedkiez,thanks for that,
interestingly, those suggestions seem to have moved things on!
However, I’m now seeing this screen…
Why would I need to Move my licence? I’ve only got one nucleus ¬hing has changed except the last Roon update a couple of days ago, which has screwed things up.
I’m hesitant to switch licence just in case it complicates things further.
Any further input much appreciated
Sometimes Roon gets confused, in particular if connection to the regular server failed. Then it thinks that the server it finds now is a new server. (The identification of a server is apparently not an exact science and depends on a range of factors).
Since your license can only activate one server at any one time, it asks you to transfer the license to the „new“ server, even though the „new“ server is physically the same one.
Just connect to this „new“ server and everything should be fine.
Side note: In the last update, Roon Labs tried to make this flow more reassuring and less scary, so now to says, „Don’t worry, your music and settings are safe“, but perhaps it’s not yet reassuring enough, so I mention this here as feedback 
Suedkiez,
Think I owe you a beer!
Those setting changes on the iPad & iPhone controllers have done the trick!
The update licence also worked v smoothly although I’ve lost my eq settings in muse. Luckily I had made a note of them old school, so it was easy just to re enter them into muse etc.
I bought the Nucleus as I thought it would be far more " plug n play" than faffing about with OS updates etc on my old MacMini, & it would just work in the background with little or no intervention from me.
It seems that’s a bit optimistic.
Still can’t see how a software update from Roon has cased this aggro.
in future I will see if I can “not allow” Roon updates to prevent this hassle recurring.
Anyway, the suns shining, the music is back on, so today is a good day.
Feedback for the Roon tech Team, as it was asked for upthread…
Getting hold of a Roon tech member, as opposed to a fellow Roon user is way to difficult. It seems as if they don’t want to be contacted & hope someone else answers the question for them. That’s not what I call good customer service.
And the licence swapping thing… ok it may be a more friendly process now, but maybe a notification that any EQ or headphone settings etc in Muse will get lost & the user should make a note them prior to doing the procedure may be useful?
Cool, I’ll drink one on you
That’s weird and shouldn’t happen. Something for @Benjamin, @noris.
You can turn off update on the server, but it would keep nagging you, which is annoying. You also wouldn’t get any necessary security fixes or necessary updates for changes elsewhere (such as digital certificates, changes to adapt to Roon cloud server changes, or adaptions to API changes by Roon’s partners such as MusicBrainz, Tivo, Tidal, Qobuz, etc)
However, you can’t prevent updates on the iPad (except if you disable ALL updates in the App Store), so incompatibilities would occur over time if the server doesn’t update but the iPad app did.
So all in all this would be a bad idea. In any case, on balance things get better with updates, even if there is an occasional minor issue.
I don’t know which change exactly it was on the iPad that helped, but if you had to change the wifi privacy setting from Random to Fixed or Off, this is generally recommended on private networks because otherwise the device identifies with a rotating, random MAC address. The Random setting helps against device tracking on untrusted networks, but the same restriction of tracking can cause discovery issues with home servers and the like.
If the critical change was the turning-off-and-back-on of Roon’s local network access rights on the iPad, this has more to do with Apple’s draconian security.
Although, personally I never have any such issues, so if this happens again, it might still be worthwhile to investigate if everything’s healthy on your network.
Well, your subsequent replies to support’s posts happened on a Saturday, and support doesn’t work on weekends, so I helped out to get you going.
Hi @matthew_randall,
So glad to hear you’re back up and running, and a huge thanks to @Suedkiez for stepping in over the weekend!
Your feedback is genuinely appreciated and well taken. You’re right that our response was slower than it should have been, and I apologize for that. As Suedkiez mentioned, your replies came in on a Saturday when our team isn’t available, but that’s not an excuse for the overall experience feeling harder than it should.
Regarding the MUSE DSP settings being lost during the license transfer — that’s a valid point and good feedback for our team. Your settings should normally be preserved as part of your Roon database, so if they were lost it’s worth understanding why. Could you confirm: did you restore from a backup during the process, or did the license transfer happen without a restore? That would help us understand if this is something we should look into.
Enjoy the sunshine and the music!
Thanks for the reply Vadim.
The license transfer was a straightforward process and completed without a backup.
Luckily I had made a note of the two Muse settings I use, one for my speakers & one for my headphones so resetting them wasn’t too much of an issue.
Maybe for others, it could be worth suggesting taking a screenshot of settings for safe keeping just in case a similar situation happens again?
Hi @matthew_randall,
That makes sense — taking a screenshot beforehand is a great tip and worth passing on!
Enjoy the music 
