Can't Deauthorize Other Core

Core Machine (Operating system/System info/Roon build number)
Windows 10 x64, Threadripper 2990wx, 64GB RAM, Samsung 1TB 970
Roon 1.7 Build 505 (Stable)

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Intel Gigabit LAN (gigabit monkeybrains internet)

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Chord Qutest DAC via USB

Description Of Issue

I use Roon at work during the day on a macbook pro and then deauthorize the core and use it at home when I get home. Today, however, when I opened roon on my home desktop it worked as normal except all playlists showed up as empty and qobuz/tidal pages would randomly show up as empty. Some tracks would stream. Only after uninstalling and reinstalling Roon and waiting 15 minutes did it give me the option of deauthorizing my laptop.

The deauthorization process worked fine in 1.6.

Hi @Alfredo_Luque,

Thanks for reaching out to us here. It sounds like something may have gone awry in Roon before you reinstalled it, would you by any chance still have a copy of the old Roon Logs? Note, since reinstalling it is possible that this folder was automatically replaced with the new database log folder, I would be more interested in the one from the Roon install that had the issues.

Does this mean that the authorization process went through successfully after a while? Are you able to use Roon as expected now?

Authorization did go through after 15 min or so. But now I have the same issue on OSX. I’m sending you my logs via PM

Hi @Alfredo_Luque,

Thanks for sending those logs over. I am looking through them and I am noticing a few networking errors when trying to authenticate, specifically you appear to be getting Name Resolution Failures quite often in the logs.

We have seen users have a better experience in the past if they change their DNS servers from the ISP provided ones to Google DNS or Cloudflare DNS. Can you please give this a try and let me know if it helps?

So, I tried both google DNS and using a BIND DNS server. I can confirm that for 1k lookups of various domains using the dig tool I’m able to achieve DNS lookups <2ms. Yet I still have the same issue where it takes 5-10 min before I’m prompted to deauthorize another Roon core. This happens both on Windows and Mac. Both on my home and office network.

Hi @Alfredo_Luque,

Thanks for checking the DNS servers.

Can you provide some more information regarding this network setup? What is the model/manufacturer of your router and networking gear? I did a search for Monkeybrains and this looks like an ISP, are you using their equipment?

Since you have changed DNS servers, can you let me know the exact local time + date when you next experience this issue and send a new copy of logs? I would like to take a look to see if there are any additional clues.

At home:

I have a Juniper SRX 340 gateway (I tried disabling packet inspection but it had no effect). It’s connected to a Mellanox SN2100 switch via gigabit copper Ethernet and my server is connected via redundant 25 gigabit QSFP+ connections to the switch with LACP failover. I’ve set the DHCP DNS servers to google dns (to no effect) and also hitting my local Bind DNS server cache. My ISP is symmetrical gigabit microwave (monkey brains).

At work:
It’s a huge company network so I’m not really sure what the topology is (I believe Palo Alto networks firewalls and Cisco switches). But on that same MacBook Pro as on my company network I can replicate the issue at my girlfriend’s apartment and she has a simple netgear nighthawk 802.11ac router and netgear modem.

Hi @Alfredo_Luque,

Thanks for providing that additional context. Can I please request that you note the exact local time + date when this behavior next occurs on the affected machines and manually send a new copy of your logs? Thanks!

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