After the update first Roon didnt start at all. Figured that the new roonserver.exe was named: roonserver.exe_new. After renaming it starts up, but for 2 days it cannot connect to Tidal. Takes me to the tidal login screen, i log in successfully, then when i go back to the app it is just waiting, waiting for tidal login.
Honestly very frustrating that 99% of the updates are useless crap, and they regularly kill either the database or the tidal connection. Tidal connection is quite unreliable in roon anyways.
Same problem like me re-install didn’t help anything. After re-installed not thing changed and every time when I open Roon the program will let me setup step every time!!!. This problem happened after updated.
nope, but the password is correct. tried reinstalling roon couple of times, and for the first run it actually logs in to tidal, i can see my collections, but never starts playing anything. then i get back to the same spot: roon is trying to log in to tidal without any success…
Ben with the support team here, thanks for taking the time to write in! Sorry for the delay in getting to your issue.
When reviewing your account, I wasn’t able to connect to your core due to it being offline for the last week. Would you be able to recreate the issue, and share a set of manual logs so our team can take a closer look? Please use the directions found here and send over a set of logs to our File Uploader.
I have the same issue. Since last update, I am not able to reach my Tidal account in Roon. I have a custom built audio PC with Win Server 2019 and AO. I do not use Fidelizer. Before this update I had no issues. I tried to log in in the Android app also. I changed the password too, but it did not help.
As I see there is problem with reaching the network. I have cca 700 albums on the SSD drive and Roon has problem with getting information and picture of these albums. The connection with Roon Android app is not stable, sometimes it cannot see the Roon Core. Same situation with net radios, sometimes I can reach those and sometimes not. Roon ARC capability test shows it is not ready.
And again, all these problems are present since last update. I had no issues before.
I am happy to send Roon team the log files (or anything else) if it helps.
I have the same problem too since May 12th. Initially I thought Roon labs will soon release a new version to fix it but after 2 weeks I am still waiting. I also tried to update to Roon Server 2.0 Build 1273 early release but no luck. I just posted a new topic to describe the details.
I do not use VPN. My entire home network is set to DHCP and I’d like to keep it that way. It should work in this setup I guess. And again, there was no problem before the last update.
I think it will be better to start a new topic with the details of my system.
If the router is set to DHCP then DNS server IP is assigned automatically by the DHCP server (in this case my router), right? So I am not able to change it on a client computer.
Anyway, my Audio PC runs WinServer 2019 in core mode, and I am not aware how could I change any network parameter.
But again, it worked well before last update, so I don’t think I should change anything in my network.
True, but the router has a DNS setting for the DNS server it uses for name resolution on the internet. You can change this DNS on the router.
If the router provides a local DNS on the LAN, it will still communicate the router’s own IP to the clients by DHCP, and the clients will still ask the router for names. But the router will then use 8.8.8.8 (or whatever you configured) for names on the internet that it can’t resolve itself.
If the router does not provide a local DNS, it might communicate the 8.8.8.8 directly to clients by DHCP
in the meanwhile I changed hardware, and also updated from win2016 server to win2019 server, core mode, and the same error is happening. Exactly the same error is with my friend’s PC, who also uses win2019 server in core mode. I have Intel CPU, he has AMD. We will upload our logs as you described.
