· I use Roon on my phone, wirelessly connected to a Mac computer that contains my music library. Recently, when I open Roon on my phone, it says I have to login. When I login, both the app on my phone and on the computer freeze. I’ve updated the app, restarted the computer, etc. This is new over the past 2 months or so, so I’m suspicious that it has to do with a recent update.
Tell us about your home network
· I have Verizon FiOS, and my computer’s Ethernet is plugged to the wall, which is in turn directly wired to the Verizon router. So it’s hardwired.
Roon update, sorry for not making that clear. It’s all a bit strange as I’ve never had to login before - I would just open the app on my phone and it would work.
Thank you for taking the time to write in and share your report!
We were able to take a closer look into a fresh Roon Server diagnostic report, and saw that your server appears to be stuck in a NotLoggedIn / NoAccountConfigured state since at least February 4, 2026 — matching your “past 2 months” timeline perfectly.
On every login attempt (most recently March 31), this sequence happens:
Login to Roon's account server succeeds and your credentials are valid.
Roon then tries to register this machine (Daves-Air, machine ID 662494e1...)
The server replies: NeedsBump meaning a differentDaves-Air (machine ID 557b079c...) is already occupying your license slot
Both apps freeze during this bump resolution process, and it eventually rolls back to NoAccountConfigured
The NeedsBump condition almost always stems from one of:
A macOS update or migration that changed the machine's hardware identifier (Roon sees it as a "new" machine)
Running Roon Server inside a VM, Docker, or as a different user after an OS change
A Time Machine restore or disk clone that created a machine identity mismatch
Have you performed any of the above actions?
For next steps in troubleshooting, let’s fix the machine authorization via your Roon account settings.
Go to
and log in. Under Devices/Machines, you’ll likely see two entries for “Daves-Air.” Delete/deauthorize the old one (ID 557b079c), then try opening Roon Server again. This is the fastest fix and directly addresses the NeedsBump error.
Another important item to note, it looks like your Mac (Daves-Air) may be seeing itself on two different subnets simultaneously, which could also be causing you issues.
If possible, can you temporarily disable all but a single subnet in your local network, reboot your devices, and see if that helps as well?
When I login to account.roon.app I see my account info (name, billing info, etc). I don’t see any tab for Devices / Machines. I see “login sessions” which show my login on Daves-Air and on my phone.
I have no idea how to disable all but a single subnet and I’ve never had to do this before … I haven’t done any of the other things you described, OS update / running the server as a different user, or time machine restore.
Ok I’ve closed all open sessions and stopped and restarted both Roon and the Roon server multiple times. I’m still getting the error.
I re open Roon, and it says “connect to Roon server.” I connect, then I’m still getting the message “you’re already signed in.” When I click “go back” everything freezes.
Isn’t there anything that can be reset on your end? This is beyond frustrating and I’m beginning to regret signing up for a lifetime subscription …
Here is more information around subnets that will help:
To check for multiple subnets from a Verison FiOS router:
Step 1: Log in to the Router Admin Panel
Open a web browser on a device connected to your network.
Enter 192.168.1.1 in the address bar and press Enter.
Log in using the Admin Password found on the sticker located on the back or bottom of your router.
Note: This is different from your Wi-Fi password.
Step 2: Access the Basic Device List
To see a visual list of all connected devices regardless of their subnet:
Look for the Devices tab (usually on the left-hand sidebar or at the top of the Home dashboard).
This screen shows all active and inactive devices.
To see the IP/Subnet: Click on an individual device name to see its IP address. Devices on the primary network usually start with 192.168.1.x, while guest devices often start with 192.168.200.x.
