Mistakenly "unauthorized" my Roon core

Hey @Russell_Reising,

Thanks for writing back in!

One way to do this would be to simply power down your Mac or Windows PC you’re not wanting Roon Server to run on. That said, you can also typically quit Roon Server via the task bar on either machine as well - just click the Roon jellyfish and you’ll see a dropdown to quit Roon Server.

Based on your admin page, there is a chance you’re running two separate local subnets within your local network, which could be causing you your discovery issues with your W4S server.

An easy way to check this would be to access your router settings > devices list, and check all your IP addresses. Make sure they all have the same initial numbers, like 192.168.0. for example. You want all your Roon devices to share the same .0.

Let me know if this helps! :raised_hands:

I will check all of these options. Thank you for your help and your patience with me. :ok_hand::v:

1 Like

Sounds good @Russell_Reising, let us know how it goes! We’ll be here to help if you run into any additional questions along the way. :+1:

To view background processes on your Mac, use Activity Monitor, a built-in tool that lists all running processes and displays their resource usage (CPU, memory, network).

Here’s how to access and use Activity Monitor:

  • Open Activity Monitor:

    • Spotlight Search: Press Command+Space, type “Activity Monitor”, and press Enter.
    • Finder: Go to Applications > Utilities, then double-click “Activity Monitor”.
  • View Processes:

    • CPU: The default view shows processes and their CPU usage.
    • Memory: Click the “Memory” tab to see memory usage.
    • Network: Click the “Network” tab to see network activity.
    • Energy: Click the “Energy” tab to see energy usage.
  • Get Process Information:

    • Select a process: Click on a process in the list.
    • Double-click or click “Info”: This will display detailed information about the selected process, including its path, command-line arguments, and resource usage.
  • Quit a Process:

    • Select the process: Choose the process you want to quit.
    • Click the “X” button: Or click the “Quit” button in the Activity Monitor window.

You may also need to remove it from auto start?

To prevent a process from automatically starting in macOS, you can either remove it from the “Login Items” in System Settings or, if it’s a Dock app, uncheck “Open at Login” in the Options menu.

Here’s a more detailed explanation (multiple methods):

  1. Using System Settings (Login Items):
  • Open System Settings: Click the Apple menu () in the top-left corner of the screen, then click “System Settings”.
  • Go to General: Click “General” in the sidebar.
  • Select Login Items: Scroll down and click “Login Items & Extensions”.
  • Remove the Item: Select the item you want to prevent from opening automatically, then click the “-” (minus) button below the list.
  1. Using the Dock:
  • Right-Click the App: Right-click the app’s icon in the Dock.
  • Select Options: Hover over “Options” in the menu that appears.
  • Uncheck “Open at Login”: Uncheck the box next to “Open at Login”.
  1. Using Activity Monitor (for more complex processes):
  • Open Activity Monitor: Go to Applications > Utilities > Activity Monitor.
  • Select the Process: Find the process you want to stop in the list and select it.
  • Stop the Process: Click the “Stop” button in the upper-left corner of the Activity Monitor window.
  • Choose Quit or Force Quit: Choose “Quit” (to allow the process to shut down gracefully) or “Force Quit” (to immediately stop the process).

Bear. Thank you so much for your extraordinarily good and detailed help!

As it ends up, you were right and I was able to remove the undesired Roon setting from the menu of automatic at startup and in every other way.

I will try to have it operate now and see how it works!

1 Like

Hi @Russell_Reising,

Please let us know how it goes!

We’ll follow up with instructions from there to prevent this condition from occurring again.

I am finally listening to David Bowie’s last album and loving it. Bear and you have given me excellent advice and I seem to have fixed the problem which was one of too many connections. I was finally able to permanently unauthorized the other roon core

Any advice as to how to prevent this from happening again would be greatly appreciated.

I am deeply appreciative of all the help and patience I have received here.

1 Like

Hi @Russell_Reising ,

Glad to hear that you were able to permanently unauthorize the other Core. You can unauthorize/reauthrozie servers as often as you’d like, so it shouldn’t be too difficult to fix if you happen to run into this again. One suggestion I can give you is to have the Mac Mini not even start RoonServer, you can do this by starting Roon Server (don’t authorize it on the Mac), right clicking on it in the task bar, and uncheck the “Start at startup” option. Then it won’t be running at all (unless one day you decide to switch over to the Mac Mini and manually boot RoonServer up).

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