It looks like the screenshot didn’t come through correctly. Could you kindly upload it again? Additionally, please let us know what steps you’ve already taken so we can better understand the situation and assist you further.
I have reinstalled the server software, I did a reboot,
I have this problem most of the time. Also yesterday, after 3 hours roon was ready.
unfortunatley i cannot send you files. you should know how the screen shots are looking, aalways the same - waiting on a roon server, cannot connect… everything is correct with the nucleus, all information are shown via adress 192.168.02.
I am frustrated, your software is not cheap, I do not use it very often and most of the time I have problems to get the system running. I do not know where the problem is. The system is not unusual. The switch before the nucleus is a melco s100, before this is a standard switch because there is some hardware from my solarsystem that is also connected via ethernet and the switch from where all ethernet lines running through the house. Cables are cat5.
Kind regards
hubert
p.s. it would be much easier if it will be possible to send you mails, e.g. the last log-files or screen shots, whatecer you neeed - much easier with mail.
Thank you for the update, and I’m truly sorry to hear about the ongoing frustration. We understand how disappointing this must be, especially considering the investment you’ve made in Roon and how infrequently you’ve been able to use it reliably.
Based on your description—and the fact that your device does not appear in our diagnostic data—it appears something is likely blocking access to our servers, or interfering with network device discovery within your local network.
You mentioned the Melco S100 switch. Since this is an unmanaged switch, it typically shouldn’t interfere, but to better understand the root of the issue, could you please share your full network setup? This includes:
Your main router (make and model)
Any mesh systems, Wi-Fi extenders, or access points
Any managed switches or firewall appliances
How the Nucleus is connected in relation to these devices
If possible, how IP addresses are assigned (DHCP or static)
This information will help us narrow down any possible points of failure or interference.
Also, regarding your note about email support and file sharing—we completely understand. While the community forum doesn’t currently support email communication, you can upload log files or screenshots using the file upload option in the forum post editor. If you’re having trouble with that, let me know, and I’ll guide you through the steps.
Again, we appreciate your patience and want to get this resolved for you as soon as possible.
the main router is:
Technicolor CGA2121 (from the internet provider)
there are 4 FritzWlan Repeaters (1750E, 2400, 3000 and 310), connected via wifi, no ethernet connection
i have no managed switches in the system, on the way to the nucleus are to switches - both are from TP-Link.
The first switch is the main switch - from there is the cable to the main router and cables in the living room and basement. in the basement is the second switch which leads to the melco switch. IP adresses are assigned with dhcp, exept the wlan switches - they all have static ip adresses. Nucleus has always the same IP-Adress.
on the melco swich are also the BluRay player and the TVReceeiver. Sometimes i loose the connection to this also, uaually it helps if i plugout the melco switch and plug it in again. when i do not reach netflix or so, i also do not reach the nucleus. but just right now i can see the nucleus via broswer, saying everything is alright.
just right now in the explore are:
the 4 fritzlanrepeaters
the nas for the audio files (192.168.0.30)
Marantz CR 611 (192.168.0.21)
Naim Mu-So (192.168.0.62)
main router (192.168.0.1)
and a Broadcom Media Server - Version 2.1 (192.168.0.10) (to be honest i have no idea what this is).
On the screen where i can choose the roon server the nucleus is shown as “bereit” (Ready), pressing the connection button leads to the usual screen - waiting for the server.
I’m experiencing the same inability to connect after the most recent upgrade. I had been running on a nuc, but bought a nucleus one. When first installed it worked perfectly. Then it began to update and hasn’t worked since. I’ve reinstalled and rebooted an every imaginable effort to work around to no effect. Very frustrating. Awaiting delivery of a rose streamer to see if I can get roon working on other than an Apple device. Very frustrating. Very expensive workaround.
Your post indicates you might require assistance from Roon technical support.
To equip the Roon Technical Support team to assist you directly, please follow this link to provide the details of your case to Technical Support: Technical Support Request
Respond to the prompts there to ensure that you’ve performed basic troubleshooting and to ensure Technical Support has the full details necessary to expedite Technical Support’s investigation into the case.
Your responses will auto-generate a Community thread in the appropriate section.
yes, every update leads to this problems. i am always afraid starting updates. yesterday was update time again, but surprising - it worked after few hours. but today, nothing is working. nucleus is shown in the webbrowser, also shown in the list of possible roon servers, but there is no connection.
kind regards
hubert
You mean the FritzWlan Repeaters? Why would you set up static addresses in them? - best practice is to set them to obtain their IP address via DHCP from the main router…
Then set up DHCP reservations in your router so that they always get the same IP addresses not different ones. If you are using static addresses that are within the DHCP range of addresses there will be a possibility of IP address clashes as leases are renewed.
To ensure multicast traffic flows efficiently across your network, especially with multiple repeaters connected via Wi-Fi. If IGMP Snooping or Proxy is disabled or blocked, multicast traffic fail to reach devices, causing discovery issues.
well it looks like that the Technicolor CGA2121 can not “multicast”. i can’t find such a setting. all Fritz repeaters are multicast - able, but there is no setting. All fritz repeaters are connected via wlan bridge, no lan bridge.
i have contacted the internet provider.
at the moment roon is working.
sorry, i guess this is what i do, they have reservations to use the same ip adress, because i want to avoid thsi mentioned clashes.
i am not an expert, sorry. just a user.
I don’t even know if mine attempted to do an update. This is so maddening. Worse is that we seem to be on our own. I love music. I don’t know much about networking. Roon seemingly requires patience and skills i just don’t have. i feel like i need to return the new nucleus since i don’t have any sense that this is going to get repaired. i don’t need to take a loss while waiting. and you can’t reach anyone.
At The Moment roon is working. Internet provider says modem can do multicast, but i see nothing to activate or disable it. So maybe this is running automatically.
To summarize this thread, you’ll need to take the following steps to ensure Roon’s device discovery announcements can pass between the extenders/repeaters in your topology:
Fritz!Box repeaters should rely on mDNS by default and allow for multicast traffic to forward between nodes. However, you will need to ensure multicast settings aren’t restricted in the main router settings page. This would include options related to IGMP Snooping (turn them on) and Multicast Forwarding (turn them on, too).
Since you’ve set up static IP addresses for each node, IP conflict will be an ongoing vulnerability in this network after router firmware updates or any network resets. The DHCP servers responsible for Roon have to also retain the IP addresses of each node in this topology. Please see @Geoff_Coupe’s post above and consider relying on automatic DHCP and address assignment using the main router instead.
If you continue to experience network disruptions after taking the above steps, first try restarting RoonServer to prompt a network discovery cycle. This thread will soon auto-close, but if you require further troubleshooting, reach out in a new request here to continue the conversation. Thanks!