Persistent login requirement after server reboot (ref#B0RP99)

[Jason_Adriaanse (Jason A)]

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

· I have to login into my Roon account every time my server reboots

Tell us about your home network

· I have 2 fixed network addresses on the server for 2 different IP ranges. There are multiple wireguard clients running as well

[connor]

Hi @Jason_Adriaanse,

Thank you for your post. If the network identity of your Roon Server changes between reboots, Roon’s authentication servers will treat the device as a new session and prompt you to log in again. This flexible interface setup with different subnets and multiple WireGuard clients is likely triggering this exact scenario.

Roon is really designed to function best in a simple, single-subnet consumer environment on a dedicated server machine. The solution is to pick one primary IP/subnet for Roon to use. WireGuard can also interfere if its virtual interface comes up first, so either delay WireGuard startup until after Roon or configure the VPN to exclude local LAN traffic. Once the network identity is stable, log in to Roon once and reboot the server; if the network interface remains the same, Roon should remember your login.

Hopefully this helps. Thank you!

[Jason_Adriaanse (Jason A)]

Hi Connor,

Thanks for your reply.

I disabled all my wireguard clients, rebooted and still had the same problem. Docker is also running on the server so I in put in a 30 second delay to start the service because a volatile veth interface gets created on reboot which I am sure will upset Roon.

I finally tracked down the problem though, so I will explain it in case someone else has the same issue. This is a for a server running Debian 13 with NetworkManager. The configuration files for the network interfaces are stored in
/etc/NetworkManager/system-connections/

Each file in this directory contains a .nmconnection file. The names of those files need to match with the network connections on the server so in my case they are

enp1s0.nmconnection  
enp3s0.nmconnection

One of the files did not match so I renamed it and now Roon seems to be happy. My VPN clients are up and running as well, the delay in docker is still there.