Unable to unauthorize old core on Roon account (ref#T5G9GB)

What’s happening?

· I'm having trouble logging in

Where are you having trouble logging in?

· Other

How can we help?

· None of the above

Other options

· My Roon software won't start up

Describe the issue

Unable to unauthorize old core on my account

Describe your network setup

unifi dream machine pro max / 10gb fiber and backbone

When pressing (my desired action) the unauthorize button on the Mac Client, the screen returns to this state again. Indicating the unauthorize action did not complete.
I need to unauthorize this macbook to be able to authorize my Roon server hosted on a different machine.

Hey @Stef_van_Hooijdonk,

Thanks for writing in! Sorry to hear about your issues attempting to unauthorized an old Server!

As a first step, if you haven’t yet, I’d reboot both the Mac and Roon Server running on the Mac, as well as your router.

Do you have any third-party antivirus software active on the Mac? It may be worth temporarily disabling the Mac firewall, and test to see if the same issue persists.

I’d also set up a temporary hardwire ethernet connection from both Roon Servers to your router, and see if you run into the same issue.

We’ll be on standby for your results! :raised_hands:

Did all that already. On the new server I see in the logs most api calls towards api.roonlabs.net getting an unauthorized http status code. I installed roon on a debian server and then i can ssh into it to see the logs.

I seems my account is only halfway migrated to the new server ‘fingerprint’ (i am guessing mac-addr) but not fully assigned yet.
Other similar simptons now:

  • Unable to perform analysis calls
  • Metadata enrichment is not working (red triangle in the UI)
  • Cannot play any music
  • Will get kicked back to some UI screen in the app ‘if I am connected’ (wel… I am with 8Gb :slight_smile: )

screenshot:

As you can see, the api’s return many 401 and 5xx errors when doing a search.

Fiddle fiddle…

Weird roon server behaviour, but Local / UTC time problem. Setback the clock 1h and now it seems to work.

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