Circular prompts on Roon login on ChromeOS, no access (ref#QCK8VK)

Tinkering
1

Affected Product

Roon

Roon Issue Category

Description of Issue

circular prompts on log in - no access

Roon Server Platform

Linux (NAS/SonicTransporter/Antipodes/Ubuntu/etc.)

Linux Server Type

Ubuntu

Roon Server Specifications

mojo audio Deja Vu

Connected Audio Devices

usb

Home Network Details

dont know - no change

3

DELETED my problem resolved itself.

4

Hi. I may add some specific information.
Our Chrome OS laptop is running the latest version of the android Roon Remote app from the play store.
On the same LAN, another computer is running Linux Roon Server.
The log there shows: Starting RoonServer v2.0 (build 1353) production on linuxx64.

  1. Click on Roon to run the remote application.
  2. It finds the server, identifies it as v2.0 build 1353 and prompts to press Connect.
  3. Upon clicking connect, a login window appears, “if you already have a roon account, log in now.”
  4. When we login, it says welcome back, choose an account, and the only account shown there is this one. When I click on that account, it brings me back to the previous page, “if you already have a roon account, log in now.”
  5. Step 4 would repeat forever. but at the bottom of the welcome back window, there is an option to “sign out and use another account”. Then I get “Continue As” and choose my name/email, or I can manually sign in, but then eventually, it goes back to “if you already have a roon account, log in now.”
  6. Meanwhile, the server doesn’t really show anything in the logs. It appears as if the remote client is just stuck authenticating with roon.
5

Sadly, Chrome OS is not a supported platform – you’re more or less on your own here with maybe some support from other users using Chrome OS too.

That aside though, most issues related to login seem to stem from OS independent issues (incompatible browsers [by design or misconfiguration], network issues [DNS server side, blocking proxies, …]). It is hard to give good advice here as we (other Roon users) don’t know details here (none shared). you can try and read through resolved threads about login issues and see if their solution applies to your case too: Search results for 'login status:solved in:title order:latest_topic' - Roon Labs Community

6

It has been stated elsewhere that Chrome does indeed work as a remote, but not as a core.
Before I upgraded to 2.0 I did in fact use this very same Chrome system as a remote.
So, I am only interested in getting the prior remote function back and running the system as before.
Also, I believed enough details were enumerated above to provide a proper base for a dialogue, but maybe I should provide some other info as well, but what then ?
Thank you.

7

Lucky you - Really wonder how that happened !

8

Just because “it works” doesn’t makes it supported though. You’re in the same boat here as Linux (desktop) users. Supported platforms as client are Android, iOS, MacOS and Windows.

As it looks to me, the login process is two steps:

  1. login (web / internet)
  2. send authentication token gathered in step above to Roon

If you have trouble with the first step it is on you to troubleshoot and fix (unless Roon servers are temporarily down). If your issue is with the second step, then you are likely lost here with your ChromeOS setup as it is not supported (a method to send the token from the browser to Roon on ChromeOS has not been tested/implemented). Try to use a supported client instead (phone for example). As far as I can say from my experience, once you logged in successfully your system is unlocked and you should be able to use your ChromeOS client again to control Roon.

1 Like
9

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