Roon Bridge stuck on enabling on Debian 12.13 armv7l (ref#JGL6SA)

[YuiFunami]

What best describes your playback issue?

· A connected audio device is not appearing in Roon

What type of Zone is affected by this problem?

· *Network Zones* are affected.

How is the affected Zone connected to your RoonServer machine?

· Network - Ethernet

Which network audio protocol is the Zone using with Roon?

· RoonReady

Does the device show up at all in Roon Settings -> Audio?

· Yes, it shows up there, but it isn't Enabled

Does the "Enable" button unlock the Zone?

· I pressed Enable, but the Zone remains disabled

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· Both the device and RoonServer are connecting to a *single router*

Try to disable any additional networking interfaces on your RoonServer machine.

· Disabling network interfaces had no change in behavior

Check to make sure RoonReady mode is selected on the device.

· I've checked this and the issue remains

If the device has multiple output options, do the other options work as expected?

· Only one output type is affected while the other output type works as expected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

What are the make and model of the affected audio device(s) and the connection type?

· Gustard R26 with internal streamer running Roon Bridge on Debian GNU/Linux 12.13 for armv7l connected via LAN

Describe the issue

Roon Bridge on Debian 12.13 armv7l stuck on Enabling

Describe your network setup

Just a router

[YuiFunami]

Note: I chose “Roon Ready” option because Roon Bridge wasn’t there as an option. Also dug through logs but nothing helpful there.

[vadim]

Hi @YuiFunami,

I have reviewed your system diagnostics, and I see that your Roon Server is running in a virtualized environment (QEMU) with a complex network stack consistent with Docker containers (visible via the multiple 172.x.x.x interfaces).

Please note that Roon Labs does not officially support running Roon Server in Docker or Virtual Machine environments.

The issue you are describing—where a device appears but gets stuck on “Enabling…”—is a classic symptom of network isolation. Roon relies on specific network protocols (multicast/broadcast) to handshake with endpoints. In Docker/VM environments, the default network bridging often blocks or misroutes these packets, preventing the Core from finalizing the connection to the Bridge.

To confirm if this is the cause, we recommend temporarily testing Roon Server on a standard, supported operating system (Windows, macOS, or Linux installed directly on hardware) on the same network.

[YuiFunami]

It was a compatibility issue between the EA and the new 2.60 bridge. Nothing more, nothing less. But while debugging this I did find one interesting issue that I’ll report.

[noris]

Hi @YuiFunami ,

Thanks for the update, glad to hear you were able to resolve the issue by switching to the same version!