I used the beta installer from February.
@James_Aguirre WIth me restoring a backup i created before reinstalling solved the issues.
I used the beta installer from February.
@James_Aguirre WIth me restoring a backup i created before reinstalling solved the issues.
What was the issue you were having? Was it the same connection to roon client problem weâre having?
How did you restore the backup?
Thx
I believe it is something different. My issue was that i could see my audio devices in the audio settings but could not select them as a playback device. I can connect to the core so i restored a backup from within the settings options.
It was a Roon issue and not related to the DSM7 installer. Nontheless i am happy i got it fixed and can enjoy using Roon again.
Pareil pour moi simplement restaurer une sauvegarde et op tout fonctionne avec DSM 7.0
Same for me just restore a backup and op everything works with DSM 7.0
How do you just restore a backup? I have a copy of my pre-upgrade roon folders. Do I just copy over the one roonâs currently using?
No, but you can restore a backup from within the backup settings in the app. I only had to move the backup folder to the Roonserver folder because of read/write limitations on other folders.
This was posted elsewhere, if youâre desperate.
Does anyone understand why restoring a backup appears to be a fix? Is there a possibility that Roon on DSM 7 is unable to index your local music folder(s) and backup restoration is giving you the impression that itâs working but is really just restoring an old catalog that canât be updated as music is added/removed?
Does seem that if you can stream a local track then that would be evidence that itâs not a broken permission issue. But Iâm confused about why a backup would fix things.
I canât get to the Roon app, thatâs the main problem. The web based UI doesnât open.
Update â while I canât open the web UI, the IOS app did connect and offered the option to restore from a backup and so far that might be working!
( Iâm not desperate enough to go back to DSM6. Eventually Iâll figure it out )
Progress but⌠so I did a restore from a backup but then end up on the roon login screen. If I try to log into my account, I get this.
Update - I hit Unauthorize and itâs working! I can connect from my mac and ios apps.
The only thing thatâs strange is that the web app still returns ERR_CONNECTION_REFUSED when I go to: https://192.168.1.15:8888/
@Bill_Wolf - Iâm not remotely an expert - using Roon just for a few months - but it doesnât surprise me that youâre new installed and configured core has a different unique id than the previous installation. Iâve played with using Roon in two physical locations. The Unauthorize operation simply removes your license grant from an instance of Core. Youâll need to do that to shift it be able to associate with the new instance.
Did you uninstall the old version before installing the beta package? I think doing so is the safest route but the question is academic in your case.
As far as I know, Roon Core running on a NAS does not have a web GUI. In my current DSM setup, there is no link to the GUI, so I canât click on anything that produces the error youâre seeing. If I create an equivalent link and try to access port 8888 on my NAS via http, I see a similar error since nothing is listening on that port.
I believe @crieke commented on this earlier. The actual issue is that the link youâre clicking on is being displayed at all, not that Roon isnât responding on 8888. I think you can ignore the link and expect that, in the future, it will disappear.
upgrade DSM 7 this morning.
The roon server stoped.
Hope the roon update wonât be too long to wait.
Thanks
I found this in another thread:
I was just able to start the sever manually with the following command via SSH:
sudo /var/packages/RoonServer/scripts/start-stop-status start
Server is up and running.Itâs not showing in the UI that itâs running but Roon finds my core again. So at least there seems to be a workaround.
see here: Roon Server on Synology DSM 7.0 Preview - #2 by Jonathan_Fallows
Hope it works for you too
Hello,
is there a workaround for not being able to have a Roon database on USB shared folder (other than moving it to HDD volume)?
I found a workaround that I believe it will do the trick until it gets officially solved.
Iâve:
It worked right away. And it seems to be working after the Synology restart.
Chistopher, Thank you for creating the beta install of Roon Server for DSM 7.0. After watching your video and moving my database off the USB SDD drive back onto the Diskstation, everything works as it should.
Importantly, either Disk Station Manager 7.0, or the new install from has resolved ongoing nagging issues with Roon on Synology.
First, since Roon 1.7, I was experiencing a roughly seven second delay from the end of one track of a playlist to the start of the next song. The delay was just long enough to be noticeable but not so long that it was worth submitting a ticket. This issue is now gone. Next songs start immediately.
Second, my NAD C368 had an ongoing issue that started with a Roon upgrade about a year ago where at first start-up sound would not start until I adjusted the volume either up or down. Every time I would fire up the NAD, nothing would play until I clicked on the volume button. Again an annoyance but nothing worth submitting a ticket on. With DSM 7.0, the new Server Install, and perhaps moving the database off the USB drive, somewhere in those changes something occurred and the NAD starts playing songs without me having to adjust the volume.
Last, as improbable as it may seem, Roon sounds better than ever! A halo effect for sure but Iâll take it!!
If you were running a usb flash drive and not a real SATA SSD then I might expect this.
The SSD I was using is listed below.
I might agree with you except my issues with slow starting of tracks and the NAD not starting as normal used to not happen at all while I was using this SSD. It was during updates to Roon that these issues crept in.
All I was doing was following Roonâs suggestions to kept the database on a SSD to improve performance. Now I realize the opposite might be true, at least based on my experience.