Im not sure what exactly is going on, but since i updated roon server to 1554 ive been having really strange network/roon server crashes.
I raised a topic on Roon support and sent them logs etc but in the absence of feedback from them i have been trying to diagnose it myself.
Here is the link to my topic i raised with them for your reference so you can see the symptoms ive been getting.
The reason im raising this with you now is that ive just noticed that before my server starts to crash and my network die, the web ui on one of my ropiee display endpoints starts to go on a go slow (i have 2 x Pi4 headless & 2 pi3 display - all wired network)
So i disconnected all my ropieee endpoints and amazingly my Roon Server will restart and network wake up… (which wasnt happening previously without me rebooting my Router).
I have a chromcast audio and roon arc on my phone so i can use Roon for the next day to try to see if the problem reoccurs without the ropieee devices switched on. (So far its only lasted a few hours before it dies).
But i wanted to raise it with you as i wondered if you had become aware of any networking issues since the roon server changes (possibly ipv6 related) with your ropieee release? Im on the latest release of ropieee on my devices - 2025.08.1 (2724 & 2725).
Im pulling my hair out right now as this only happened the moment i installed the latest roon server update 8 days ago…
It’s disappointing to see that the change in ownership has had no impact on the most important thing a subscriber should expect to receive for their money.
In any case, just wanted to mention I am using 6 ropieee endpoints with the latest roon server release and havent experienced the problems you’re mentioning. Obviously that doesn’t help (sorry) but it does imply it’s much more complicated than just the version of the server/bridge.
Thanks.. yes i assumed it wasnt that simple as i hadnt seen anyone else with the problem…
However, my ropieee endpoints are clearly affecting my server as since i took them out the equation it is running just fine… so they are contributing somehow…
I have three ropieee endpoints here too, and I am seeing the same problem.
My other endpoints are all just Airplay, so no RAAT.
Do you have any RAAT/RoonReady endpoint devices?
Note that (I think) a ropieee endpoint is just the standard Roon Bridge v1.8 (as released from Roon Labs) for Linux, installed in a custom Linux installation (the RoPieee part).
I wonder if the problem happens with the same Roon Bridge installed in other Linux boxes (DietPi, or even just native Raspbian or x86 Linux).
I don’t currently have time to look into that further but I do not believe it is anything to do with recent RoPieee release versions… it happens here even with an older (2025.02) RoPieee.
In general I’m not aware of such an issue. There’s, at least client side, also no change that should point in that direction. Furthermore, if there was an issue in general with RoPieee, I would have been informed by a lot of people
This sounds like something (at least related) server-side. ipv6 could be a trigger, because RoPieee itself also supports ipv6. But, I myself are fully ipv6 and don’t have your problems.
btw: are you running Squeezelite (LMS) by any chance?
No im not. It is certainly a trigger for the issue though. Its been running now for nearly 24 hours and no issues. Im out at work right now and roon arc is happily working.
I may try to introduce my endpoints in one at a time later. I have 2 hanging off a wifi extender and 2 wired directly into my main router.
Maybe i have a rogue installation or network issue on one of the PIs..
Well, its something to do with the ropieee i use for my display (not attached to a dac or hasnt got one onboard either.. just attached to a 7" screen for showing whats playing.
I got home earlier and firstly connected the ropieee i was using as an endpoint for my musical fidelity m6xdac. This worked fine.. i tried everything i could to get.it to break… nothing. So, after an hour i connected the display i use to show what im playing… and within 3.mins.. bang… the roon server went down and i coulsnt connect to the display ropieee. As soon as i disconnected the display ropieee it all went back to normal.
Both of these ropieee boxes are connected via an ethernet cable to a wifi extender.
Not sure if your feedback works after having to restart the ropieee in question but as i said i couldnt browse to it after things started going wrong. Ive rebooted it and before it all goes odd again ive sent feedback from it …
This sounds as if there is a IP conflict between the ‘display’ pi and Roon server.
While waiting for Harry to look at the feedback you sent, I suggest you check that the two boxes have different IP addresses.
What I do see, and this might also make sense in relation to “what’s the difference when I turn on thhe display unit”… the extension (that’s the difference when running display) detects that your Roon core is gone.
So it might be that the RoPieee extension, necessary when you have a display, somehow triggers your Roon server to go crazy. Now, nothing has changed in the extension (and many, many users exist), but maybe this explains at least the difference.
What you could try is delete all extensions that you have paired in Roon server. Maybe something got mixed up and a ‘clean up’ could help.
Roon server definitely doesnt like ropieee extensions on my environment since this latest update.
As you suggested, i deleted all extension authorisations in roon, plugged in my display.. and i didnt even have time to try to reauthorise the extension… roon died there and then.
I also tried it with my other display to make sure it wasnt hardware specific… exactly the same symptoms.
So it seems my roon now happily works but i have two displays i can use as doorstops
What i find odd is that no one else out there who has a ropieee acting as purely a display extension hasnt had this issue too… maybe those people havent updated the roon server yet?
As you cant see anything your end, have you got any suggestions how i pass this on to the roon team?
Well, I would expect that the Roon team is able to look into the logs of your Roon server. I would at least stay away of ‘steering them’: so don’t mention things about the extension, because that might also be a symptom. I think they need to look at your server ‘in general’ to see what’s going on.
Unfortunately they have had my logs over the last 10 days and havent been able to narrow it down.
At least i can now point them to what is (even indirectly) triggering the issue…
Also, this is not an old instance of the server that could be a victim of historic file changes and corrupt files as after the server upgrade and initial issue, i built a new server and did a virgin install of windows and roon server and i still got the issue.
