For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.
· I can't turn on Roon Server, I need help.
Describe the issue
I run roon on nuprime evolution stream and dac. Everything worked just fine until now, I’ve might have clicked on a update window that appeared in roon app on mi iphone and since than I can’t connect to my streamer anymore.
From the diagnostic data enabled on your account, we can confirm that your Roon Server is up and running.
10/31 11:18:55 Info: [1] Starting RoonServer v2.0 (build 1483) production on linuxx64
10/31 11:18:55 Info: [1] Local time is 10/31/2025 11:18:55, UTC time is 10/31/2025 10:18:55
10/31 11:18:55 Debug: [1] Init DefaultBackingApi: HttpWebRequest
10/31 11:18:55 Debug: [1] [easyhttp] default backing API HttpClient -> HttpWebRequest. This may cancel all in progress http requests
10/31 11:18:55 Trace: [1] Checking if we are already running
10/31 11:18:55 Info: [1] get lock file path: /tmp/.rnsems1000-
10/31 11:18:55 Info: [1] GetLockFile, fd: 60
10/31 11:18:55 Info: [1] GetLockFile, res: 0
10/31 11:18:55 Trace: [1] Nope, we are the only one running
10/31 11:18:55 Trace: [1] [bits] myinfo: {"os":"VitOS","platform":"linuxx64","machineversion":200001483,"branch":"production","appmodifier":"","appname":"RoonServer"}
10/31 11:18:55 Trace: [.NET ThreadPool Worker] [roondns] flushed 1 last-known-good entries
10/31 11:18:56 Debug: [.NET ThreadPool Worker] [easyhttp] [1] POST to https://bits.roonlabs.net/1/q/roon.base.,roon.internet_discovery. returned after 819 ms, status code: 200, request body size: 125 B
10/31 11:18:56 Trace: [.NET ThreadPool Worker] [bits] updated bits, in 906ms
10/31 11:18:56 Info: [1] Is 64 bit? True
10/31 11:18:56 Info: [1] Command Line Argument: -watchdogport=46607
10/31 11:18:56 Trace: [Worker (1)] [realtime] fetching time from NTP server
10/31 11:18:56 Trace: [.NET ThreadPool Worker] [orbit] init seq=0, pending=0, spcount=0, uidcount=0
10/31 11:18:56 Trace: [1] [ipaddresses] enumerating addresses
10/31 11:18:56 Trace: [1] [ipaddresses] FOUND lo 127.0.0.1
10/31 11:18:56 Trace: [1] [ipaddresses] SKIPPED enp1s0: no ipv4
10/31 11:18:56 Trace: [1] [ipaddresses] SKIPPED enp2s0: no ipv4
10/31 11:18:56 Trace: [1] [ipaddresses] FOUND z1br0 192.168.8.153
However, in the IP address section, we only see the network interface z1br0, which appears to originate from a virtualized or bridged network environment. Such configurations typically indicate that Roon Server is running within a virtual machine or containerized system (for example, Docker, QEMU, or a custom OS layer).
Please note that these environments are not officially supported by Roon. We recommend reaching out to NuPrime directly for further assistance with this specific setup, as they may have guidance tailored to their platform.
This thread is auto-closing shortly due to lack of response.
Diagnostic logging (activated for your account upon receipt of the original report) indicates that you might have used RoonServer in the interim. We’re going to assume this issue was resolved in the meantime, but please reach out if you require further assistance.
