Roon server static IP issue after database restore (ref#0VQ67L)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon server is set to 127.0.0.1 in about roon server - even though windows pc is fine. room can play to other devices on network. but other devices can not connect to roon server - pc is using a static ip. this is after a restore of db from the older roon server

Tell us about your home network

· google nest wifi - multiples nas - roon on a static ip win 11 pro machine

2

Hello @joe_comeau,

it is normal that it shows 127.0.0.1 there.

You are likely facing a different issue that is not related to that local IP address.

We cannot currently retrieve diagnostic data directly from your PC. Please extract your Roon Server logs using these instructions and upload them to our logs storage.

This will help us find the root cause of the problem.

Please also outline your network topology, including any switches or other networking equipment you have connected.

We also recommend temporarily disabling your static IP, switching to your router’s DHCP server, and disabling your firewall to see if that improves the situation.

Thanks,
Looking forward to your reply.

3

thanks

I’m a 40 year systems admin- with a very complicated home network. Ive uploaded the logs for you to look at where roon server was migrated from 106/107 dual homed connection - to 108 single 2.5 connection. logs from 108 new system with my name were uploaded

network consists of google nest wifi - 6 ap plus 24 port switch all back haul connected plus 2.5 gb network switch with old 107 plus new 108 plus 3 nas all connected - info only for network

music on nas

blusound and sonos speakers and amps

all work fine from the new 108 system with roon windows controller on 108

even though the old 107 roon was shut down not running - in theory

restarted google wifi, new roon 108 , old roon 107

dns on google wifi

107 & 108 static ips

renamed old 107 roon folder - could not rename if running - so was not running

I may have started roon 108 - before stopping renaming roon 107 - maybe issue

maybe something to do with dual homing on the old machine and the backup/retore process to a single connection on new system

Its working this morning vs last couple days

i was going to uninstall and reinstall - recover from backup again

from roon controller on my android phone can connect to 108

thanks for your help

4

@joe_comeau ,

We have reviewed the logs from your machine and could not spot any failed connections from remote devices.

In a case like this, it most likely indicates a network issue that is preventing your remotes from reaching your Roon Server in the first place.

We also noticed that you appear to have multiple routers or subnets active, specifically on the 192.168.86.x and 10.0.0.x ranges.

Please clarify if you have multiple VLANs or any network isolation set up.

It would be very helpful if you could temporarily simplify your network configuration so we can confirm the root cause of the problem.

Thanks.

5

Hi @joe_comeau,

Sorry for the confusion here as there was some conflicting information presented above.

It looks like the database restore latched onto the loopback when you restored.

The most immediate solution would be to just repeat the database refresh and then restore again. Roon should scan for available network interfaces and then connect to the first available. It might be worth it to disable any secondary VLANs or VPNs you have active and rely on the ethernet interface alone while you perform this step.

  • Create a Backup of your current database
  • Exit out of Roon + RoonServer (from taskbar area)
  • Navigate to your Roon Database Location
  • Find the folder that says “Roon Server” and “Roon”
  • Rename the “RoonServer” folder to “RoonServer_old” and “Roon” to “Roon_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder
  • Verify if the issue persists on a fresh database by checking Roon Settings → About before restoring the backup

Please let us know if this helps.

6

Hi Connor

thanks for the advice.

that was what i did pre-reading this reply from you.

So your instructions are spot on for anyone else migrating servers.

In addition

on new pc - uninstalled roon & db - for a clean new install and restore from backup

I reset my internet router and internal router to clear the cache while the old roon server was shutdown, just to be safe.

So my new low power nuc system is perfectly running, roon, emby and hyper-v

anyone interested:

ryzen 7 6800H, 32 gb, 512 gb nvme, 2.5 gbps

7

Hello @joe_comeau,

Since you mentioned running Hyper-V, I do want to offer a quick, transparent heads-up from the support side. As a sysadmin, you likely know the quirks of virtualized networking better than most! However, please keep in mind that Roon does not officially support virtualized environments (such as Hyper-V, ESXi, Proxmox, or Docker).

Because virtualized network layers and CPU timing can sometimes interfere with Roon’s time-sensitive audio streaming protocols, our ability to troubleshoot complex issues in the future might be limited if the server remains in a VM. If you ever run into mysterious network drops or playback halts down the road, the very first step we’d have to ask is for you to test the core on a bare-metal OS.

That being said, since everything is humming along perfectly right now, don’t touch a thing! Sit back, relax, and enjoy the music.

8

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.