Unable to Connect to Roon Server on Pixelbook for JBL Playback (ref#MDJXM2)

[sdglazier]

Is Roon Server running?

· No, Roon Server is not running.

For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.

· I can't turn on Roon Server, I need help.

Describe the issue

Unable to connect to Roon server on Pixelbook (Chromebook) for playback on "Room Ready" JBL Authentic 500. No access to PC or Mac computer. Scan for Roon server is an endless fail.

Describe your network setup

Connected wirelessly from Xfinity modem/router gateway

[noris]

Hello @sdglazier ,

Welcome to the forum and thanks for reaching out — we understand how frustrating this can be, especially when the Pixelbook is the only device available. We’re happy to clarify what’s going on and outline the realistic options forward.

At the moment, ChromeOS (including Pixelbook) is not a supported platform for running or controlling a Roon Server. The Roon web interface available on Chromebooks is limited and cannot reliably discover or connect to a Roon Server for audio playback, nor can it act as a full Remote in the way Windows, macOS, iOS, or Android can. Because of this limitation, the Pixelbook won’t be able to control playback to your Roon Ready JBL Authentic 500 on its own.

Additionally, Roon always requires a dedicated Roon Server running on a supported platform (Windows, macOS, Linux, or a RoonOS-based device like Nucleus). Without access to any of those, there isn’t a way for Roon to function end-to-end.

What options do you have?

To use Roon with your JBL Authentic 500, one of the following will be required:

• Another computer (Windows, macOS, or Linux) to run Roon Server
• A RoonOS-based server (such as a Nucleus or ROCK install)
• A supported mobile device (iOS or Android) to act as a Remote after a Server is already running

If none of these are currently available, Roon won’t be able to connect or play back audio in your setup right now.

We realize this may not be the answer you were hoping for, but we want to be upfront so you don’t spend time troubleshooting something that ChromeOS simply doesn’t support today. If your situation changes or you’d like recommendations for the simplest hardware option based on your setup, let us know — we’re happy to help.