Intermittent Disconnection Issues After 2.57 Update (ref#8T7T3A)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· since 2.57 my server keeps disconnecting, it plays for 2 minutes and loses connection, my backup only takes me to 2.60, and that doesnt work. ive reinstalled , refreshed all my network. all is exactly the same, but now its just not working.

Tell us about your home network

· nothing new here

logs are sent

You need to be on the latest version for Roon Server, Roon Bridge and all clients as some recent changes only work together.

Roon and Roon Server: 2.62 (build 1641)
Roon Bridge 2.60 (build 1501)

my last fresh install was back in 2022, i’ve cleaned it all up and is importing all local music into library again now, playing from tidal is flawless again. A fresh start is sometimes a good thing, its just an effort some times.

1 Like

Hello @Havard_Hegg,

I completely understand that starting over with a fresh database after four years is no small effort! Thank you for taking the time to do that. I am thrilled to hear that it paid off and your Tidal streaming is flawless once again.

Since the fresh install seems to have completely resolved those two-minute disconnects, are you comfortable with us going ahead and closing out this support thread? Or is there anything else you’d like us to keep an eye on while your local music finishes importing?

Will it be advised or not, to import the latest backup?

Hello @Havard_Hegg,

That’s a great question. Now that you have verified that a “clean” Roon works perfectly, yes, I would absolutely advise trying to restore your latest backup.

Restoring the backup will bring back all your custom edits, playlists, and play history, which is much better than starting from zero. Since you’ve already updated to the latest build, the database migration process should handle the transition smoothly.

If the issues return after the restore, then we’ll know for sure that the problem was a corruption within the database itself. In that case, you can simply go back to the fresh start you just created.

Give the restore a shot and let us know if the flawless performance continues!

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