· Sinve this morning my Roon does not find my server, server and remote on same pc. My other remotes can't see it either. In activity mgr I can see both RoonAppliance and RoonServer.
I have restarted both computer and Roon several times, re-installed a couple.
Welcome back to the Roon Community! I am sorry to hear that you are having trouble connecting to your server today.
It is definitely frustrating when the RoonServer and RoonAppliance processes are clearly running in Task Manager, but the user interface refuses to see them. Since the server and remote are on the exact same PC and a reinstall did not resolve it, this almost always points to a local network configuration or security software actively blocking the internal communication.
Let’s walk through the basic troubleshooting steps to clear any potential blockages.
Network Profile Settings
Windows updates or network changes can sometimes revert your network profile to "Public," which strictly limits local device discovery.
Open your Windows Settings.
Navigate to Network & internet and select your active connection (Wi-Fi or Ethernet).
Ensure the Network profile type is set to Private network.
Windows Defender Firewall
Even if Roon was allowed through previously, firewall exceptions can become corrupted or get reset. Let's make sure Roon has a clear path.
Click the Windows Start button, type Windows Defender Firewall, and press Enter.
Click on Allow an app or feature through Windows Defender Firewall on the left panel.
Click Change settings (you may need administrator privileges).
Scroll down the list and ensure that every entry for Roon, RoonServer, and RoonAppliance has both the Private and Public checkboxes ticked.
If they are missing, use the Allow another app... button to manually add the executables from your Roon installation folder.
Third-Party Antivirus and Security Software
If you are using a third-party security suite (such as BitDefender, McAfee, Norton, or Malwarebytes), it might be actively sandboxing the Roon processes.
Temporarily disable any third-party antivirus or firewall shields.
Completely restart the Roon Server process and open your Roon app to test the connection.
If Roon immediately connects, you will need to add Roon as a permanent exception or trusted application within your security software's settings.
VPNs and Virtual Interfaces
Active Virtual Private Networks (VPNs) or virtual network adapters can route Roon's local traffic into a dead end.
If you have a VPN active (like ExpressVPN, NordVPN, or a corporate VPN), turn it off completely.
If you have virtualization software installed (like Hyper-V, VMware, or VirtualBox), temporarily disable those virtual network adapters in the Windows Control Panel to ensure Roon binds to your primary TP-Link network.
Please run through these checks, restart the Roon application, and the server should reappear for both your PC and your remote devices.
Let’s try a more thorough clean test. Please follow these steps in order:
Quit Roon completely from the system tray (near the clock), not just closing the window.
Rename the Roon and RoonServer data [url=https://kb.roonlabs.com/Roon_OS_Data_Directory]folders[/url] under your user's AppData folder (for example, add ".old" to the end of each), rather than deleting them.
Uninstall Roon through Control Panel, and if there's a checkbox to clear app data during uninstall, please leave it checked, since your renamed folders are already safely out of the way, this won't affect them.
Download a fresh copy of Roon from the downloads page.
Install it.
Test the connection with this clean setup and let us know if it finds the server.
If it works, please quit the app again, restore your original folders (renaming them back), and test once more.
Let us know the result of that second test as well.
That last part matters: if the clean install connects but restoring your original data brings the problem back, that confirms the old data was the cause. If it still connects fine either way, we'll know to look elsewhere.
Ok, so I came to step 6. It said it found the new server but I could not login. Got some “There was an error logging in: InvalidRecaptcha”
Tried Step 7 but no luck, did not find my RoonServer…
But I don’t know if I did correct. Try to rename the old without renaming the new Roon and Roonserver folders but got a whole bunch of messages. I renamed the “new” folders and the renamed the old ones back…
I don’t know it this helps but I tried to start Roon again and now I come to the page where it says -“Connect to your Roon server…” where it jumps back and forth between “Connecting”, “Initializing” and “Ready”. Most time is spent on “Connecting”
Please try to confirm the issue doesn’t occur on a completely fresh database before trying to restore the backup. We were able to activate diagnostics for your account and the logs came in, but it looks like Roon is crashing over and over until the latest startup attempt you had. Are you seeing any change in behavior now? What is the amount of tracks you had in Roon?
Hi, I followed Vadim instructions once more and I can confirm that with a fresh install it works alright.
When I quit Roon, step 7, and restored my old Roon and Roonserver folders it does not work.
But I only stopped Roon and Roonserver without uninstall it. Should I have done that?
I can’t remember how many tracks, a number around 9000 pops into my mind…
I confirmed that the fresh server worked and installed the latest backup from July 12th. It seem to work pretty good, after 15 minutes anyway.
Hopefully it continues but ARC say “Not ready”, here are the diagnostics data: {
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:502,“error”:“error code: 502\n”},
“external_ip”: {“actual_external_ip”:“213.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“server_ip”:“192.168.0.1”,“found_upnp”:true,“error”:“<s:Envelope xmlns:s=“http://schemas.xmlsoap.org/soap/envelope/\” s:encodingStyle=“http://schemas.xmlsoap.org/soap/encoding/\”><s:Body><s:Fault>s:ClientUPnPError718ConflictInMappingEntry</s:Fault></s:Body></s:Envelope>”},
“multinat_autoconfig”: {“status”:“Failed”,“error”:“Port Already mapped to another Device”}
}
Thanks for the update, and good news buried in that diagnostic: the important part is healthy. Your external IP came back as a real, public, routable address, which means ARC can work on this connection. This isn’t one of the carrier-grade NAT situations where you’re stuck. The “Not ready” is down to one specific thing.
The two lines that matter are the UPnP 718 ConflictInMappingEntry and the MultiNAT Port Already mapped to another Device. They’re both telling us the same story: your router already has a port-forwarding rule for the port ARC wants, and it’s pointing at a different device (or your server’s old address). The router won’t overwrite it, so ARC’s connection test can’t reach the new server, and that’s what’s producing the 502 you see on the connectivity check. Since you just did a fresh install and restored the July 12 backup, the most likely culprit is a leftover mapping from the previous server that never got cleaned up.
Here’s what I’d try, in order:
Reboot your router. This clears out the stale mapping and is the most common fix for that specific “conflict” error. Once it’s back up, restart Roon Server as well, then re-check ARC.
If it comes back, change the ARC port. In Roon, go to Settings → ARC and change the port to a different unused number (something like 55002), then save. A fresh port has no existing rule to conflict with, so it can map cleanly.
If UPnP keeps giving you trouble, set up the port forward manually. On the router, create a static port-forward rule pointing the ARC port to your Roon Server’s local IP address (it’s worth reserving that IP in your router’s DHCP settings first so it doesn’t change). Manual forwarding takes the flaky auto-config out of the picture entirely and tends to be the most reliable long-term.
If you let me know your router’s make and model, I can point you to the exact menus for the port forward and IP reservation. And since it was running well at the 15-minute mark, keep an eye on whether “Not ready” is coming and going versus staying constant, that’ll tell us whether the mapping is being torn down after the fact rather than never getting created.
