· I'm having trouble logging in
· I can't log into the Roon app
· None of the above
· My Roon software won't start up
i changed the domain of my roon server pc and now it wont play and wont login anymore
roonserver on a pc, roon players on other pc's with their own audio devices
Extra info to clarify.
Roonserver and clientts have been working fine for a time. I changed my internal domain and have been changing clients after changing my internal DHCP and DNS server. Everything works fine, I changed roonserver and rebooted.
What happens now is that Roon client showed I had to login to roon. It showed the server so I clicked it, login and opens a webpage to roonlabs. I login, it said click here if it takes too long. I wait a bit and click the redirect link. Doesn’t do one bit. So roon just sits there waiting for the webpage I guess.
I try on my phone (iphone) and logging in actually works. Roon on the PC logs into but nothing plays. It just skips and says too many skips.
I logout Qobuz, try to log that in again but I am being logged out of Roon. Again the redirect doesn’t work so I grab my phone, that works but same issue, all tracks skipping.
I restart roonserver service, and now it won’t come online. It shows the retry button and I need to check network or internet.
Hi @I_Love_Vinyl,
Thank you for your information. It sounds like RoonServer is unable to resolve upstream addresses reliably, including both accounts servers and the Qobuz API.
I recommend first taking two steps:
Make sure the current DNS assignment is a known, reliable server for troubleshooting - Cloudflare (1.1.1.1) or QuadNine (9.9.9.9) are our recommendations.
Concerning login loops - also verify that adblockers/content blockers are disabled in the browser you’re using to login to Roon on your remotes. The browser redirect most commonly fails due to the Safari content blockers that are default on iOS, but other adblockers will cause the same issue.
What is the network pathway serving RoonServer? Please list all L2/L3 components that sit between RoonServer, the internet, and your networked storage or endpoints.
Do you encounter any issues if you play local content instead of streaming content?
We’ll watch for your response.
Basic physical schematic of the network:
Firewall lets all out, nothing in. Very basic setup for now, IPv4 only.
I tested with different browsers, no adblockers, no DNS filtering. In Chromium I would get a XDG popup, clicked allow but didn’t make a difference. I don’t think it’s a loop, it looks like that XDG thingy doesn’t find it’s way back, if that makes sense.
Perhaps because I changed the domain part of the fqdn, that XDG still wants to go back to the old fqdn? I don’t actually know how that particular part works though.
I’ll continue testing some things but I am mostly just shooting in the dark.
From macOS I can log into roon, it connects. It seems I lost all my playlists but I see my library and audio device is still there.
I browse around and before I could actually hit play, it drops to a screen with “are you online?” and a retry button.
I can login again, it will work for a minute or 2. When I play something, local or remote, it just skips everything and shows the message “too many failures”.
Hi @I_Love_Vinyl ,
I wonder if this could be the issue? If your Roon Server is unable to get a response from our account server, it could be causing the issue?
How did you change the domain? Did you plug it from one switch into the other, or can you clarify what you mean by this?
What I mean is that connections that can go out, are allowed to receive answers. So stuff is allowed in, but only when its requested from inside. New connections from outside cannot go in, they get dropped. This is how 99% of household routers work out of the box. I don’t run a basic router from my ISP, its the Mikrotik router, but I did nothing special to it. Not yet anyways 
. Its setup is very basic and allows all traffic to go out.
I use a domain name internally. Say I register the domain ilovevinyl.com. With that, I get control over DNS and I can create subdomains. So I created internal as a subdomain of ilovevinyl.com. This is what I use at home. My DNS server in my LAN uses internal.ilovevinyl.com as its domain to serve DNS queries. It also keeps track of DHCP addresses and registers their hostnames so that all local clients can reach each other by fqdn. For a while this was cool until I realized those fqdn’s are actually too long and I am typing a lot more than when I would use simple IP addresses. I deciced to change that so I that I have to type less, so I registered vinyl.com and changed it internally to int.vinyl.com. Much better! Less typing. I change the domain suffix in my DNS server to reflect the new domain and change all hosts that have fixed IP addresses to use the new suffix. Roonserver has a static lease from DHCP server, so all I had to do was reboot it.
Obviously, the domain names are examples. I can’t actually afford vinyl.com .
Hope that clarifies. Its really nothing shocking, very little changed on roon server itself.
Ive been making other changes in the network, to DNS and the firewall. I don’t know how that authentication process works exactly, so I cant be 100% sure about this, but I don’t see how those can be responsible for this process. Not when everythging else “just works”. Internet works, its accessible, there is no ad or domain blocking going on. Browser has extensions, but i disabled and tested another browser as well. I just don’t get why that xdg popup doesn’t trigger Roon that I logged in and I am authenticated. And I can’t think of anything else that has changed.
It’s solved, but don’t ask how. I hate it when this happens but I have no idea. It just started working again.
I hope that it continues to work you. Renaming a Domain Controller is a complex process and it could lead to further problems down the road. It will disrupt network services that rely on the old name, can cause applications disruptions that also rely on the old name.
It is way more complicated underneath the hood that just a name change of the server with regard to the other network related hardware and applications…
Again, glad to see that it is working again. 
–MD
Nobody mentioned domain controller.
Misunderstood what was done. My bad.
Again, glad it worked out for you.
–MD
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
