· Dear Support After I've added my ROON Nucleus Titan (internal storage 8 TB !!) an external fast SSD from SanDisk 8 TB everything was running / working very well + without problems too the last two weeks!!!! Since yesterday after your last update I can't reach my nucleus anymore: just seeing the ROON ICON moving + no answer too!!!! Thank you very much for your answer! Kind regards Hanspeter Dettwiler from Switzerland
Tell us about your home network
· Dear Support After I've added my ROON Nucleus Titan (internal storage 8 TB !!) an external fast SSD from SanDisk 8 TB everything was running / working very well + without problems too the last two weeks!!!! Since yesterday after your last update I can't reach my nucleus anymore: just seeing the ROON ICON moving + no answer too!!!! Thank you very much for your answer! Kind regards Hanspeter Dettwiler from Switzerland
The IP address 100.64.149.88 is not a standardized local, private IP address. The 100.64.*.* range is reserved for (external) CG-NAT addresses.
Something may have gone wrong on the network and the Titan was somehow assigned this address, most likely when it rebooted after the update was installed. Most likely not a Titan problem.
Are you using Tailscale for ARC? (Some VPNs and similar use 100.64.*.* for their internal purposes, so if Tailscale was somehow misconfigured, this might be a cause. But others do the same, e.g., Zscaler)
I know, the IP address of my ROON Nucleus Titan in the my Network is 192.168.1.114!!! I can see it everywhere but ROON is taking/generating a wrong one too as you could see in my attachment too!!!
Before the update everything worked perfectly nevertheless my huge music library + I’ve got all data very fast too!!!
I’m really not happy with the software currently!
I hope you can help me as soon as possible! It’s really a software problem with the wrong IP address!!!
Thank you very much!!!
Kind regards
Hanspeter Dettwiler from Switzerland
Yes, and there is shown my correct IP address too which is 192.168.1.114 and everywhere the status ‘"OK’" too!
Thanks for the screenshot. We checked your server logs directly: RoonServer is only bound to 192.168.1.114 on eth0, and Tailscale on the box shows no active connection. So that 100.64.149.88 address definitely isn’t coming from your Nucleus itself.
07/14 09:06:39 Info: Starting RoonServer v2.70 (build 1671) production on linuxx64
07/14 09:06:39 Info: Local time is 07/14/2026 09:06:39, UTC time is 07/14/2026 09:06:39
07/14 09:06:39 Trace: [roondns] loaded 5 last-known-good entries
07/14 09:06:39 Debug: Init DefaultBackingApi: HttpWebRequest
07/14 09:06:39 Debug: [easyhttp] default backing API HttpClient -> HttpWebRequest. This may cancel all in progress http requests
07/14 09:06:39 Trace: Checking if we are already running
07/14 09:06:39 Info: get lock file path: /tmp/.rnsems0-
07/14 09:06:39 Info: GetLockFile, fd: 111
07/14 09:06:39 Info: GetLockFile, res: 0
07/14 09:06:39 Trace: Nope, we are the only one running
07/14 09:06:39 Info: Is 64 bit? True
07/14 09:06:39 Info: Command Line Argument: -watchdogport=36885
07/14 09:06:39 Trace: [realtime] fetching time from NTP server
07/14 09:06:39 Trace: [ipaddresses] enumerating addresses
07/14 09:06:39 Trace: [ipaddresses] FOUND lo 127.0.0.1
07/14 09:06:39 Trace: [ipaddresses] FOUND eth0 192.168.1.114
07/14 09:06:39 Trace: [ipaddresses] SKIPPED tailscale0: no ipv4
07/14 09:06:39 Trace: [ipaddresses] SKIPPED docker0: not up
One likely explanation: many ISPs, including in Switzerland, use carrier-grade NAT and assign addresses in that exact 100.64.x.x range as your router’s WAN-facing address. Could you please check two things: does your router have DMZ enabled or any port forwarding pointed at the Nucleus, and is your internet connection on a public IP or does your provider mention CGNAT/shared IP? That would tell us whether the app is surfacing your router’s ISP-assigned address somewhere it shouldn’t.
Separately, since your server from the logs perspective is clearly running and reachable at its correct local address, could you please also share a screenshot of exactly what you see when the app fails to connect, the spinning icon screen itself?
Have you tried restarting all related devices, including routers, switches, and Nucleus itself?
The wrong IP address didn’t appear anymore! But my ROON isn’t able to start the app on my iPhone nor on my Mac Studio!!!
What I did:
Completely set back my Router on factory settings! There is no VPN, DMZ or Port forwarding active!!! My nucleus appears everywhere with the correct IP address too which is 192.168.1.114!!! I can see it on my Router, My Mac + on my iPhone too!!! I went on the ROON interface too: all settings/status are ‘"OK’" there but I saw that with ‘"ROON Database & Settings’" only 95% of 205 GB are available! No idea if this would be a problem too! I’m also in touch with my ROON dealer to sort out if the RAM could be a problem too but there are clients who have more music stored than me too without any problems too! What is strange that ROON was working very well + fast too about two weeks before!!! + also now I can see sometimes some albzms too for a short time then they disappear again + ROON is looking for the server again… → I’m going to send you some screenshot below after I’ve reset the ROON Database yesterday!
Thank you very much for your help + support! I’m still a big fan of ROON nevertheless but it should work finally + it’s holiday season too!!!
Kind regards + thank you very much for your reply!
Sorry, but none of them shows the list of available Roon Servers in your network which I would expect to be shown when clicking on “Select a different Roon Server”. So no information or proof in your screenshots that you clicked it. That’s why I asked.
The fact that your Roon loads for a short time makes us think the issue is not network-related. We went through your Nucleus Titan’s server logs and found that the actual cause of the disconnects is your library.
Your Nucleus is currently managing 375,775 tracks across 28,532 albums, with 168,337 works and 256,896 performances behind them. That’s a large and metadata-rich library. Every time RoonServer restarts, it has to reprocess over a million changed database objects before it can finish loading. Given the size and complexity involved, that process is asking for more memory than the unit has available, and the operating system is shutting RoonServer down mid-scan to protect itself. That kill-and-restart cycle is happening every two to ten minutes, and has been since at least July 13. That matches exactly what you’re describing: albums appear briefly while RoonServer is partway through loading, then the connection drops and the app goes back to searching for the server, because the process just got killed and is starting over from scratch.
To be precise about what that page says: the published numbers aren’t a hard technical ceiling, and Nucleus Titan is built for libraries well beyond 10,000 albums. What matters more is how complex the library is to manage, not the raw track count. Your library’s ratio of works and performances to tracks suggests a lot of overlapping releases and recordings per artist, which adds to that complexity beyond what the track count alone shows. Combined with the overall size, that appears to be pushing past what the unit can hold in memory while processing it.
Two more things we noticed that are likely making this worse and are worth addressing regardless:
Your internal storage (the SATA SSD used for your music library) is at 99% capacity. This isn’t related to the crashes, but please free up some space there when you can, since there’s currently no room for new music and it may cause issues with library file operations.
Over 7,000 files in your library are failing audio analysis as corrupt on every scan. Please check whether these transferred correctly, since Roon retries them on every restart, adding to the load each time.
If you’re interested, Roon also has an official program to add memory to Nucleus warranty units. If you’d like to explore that option, please open a ticket with our RMA team: open the Typeform link below, select “Other,” then “This issue is related to a physical component,” and they’ll walk you through it from there.
