I run in Docker. I installed the hotfix that was just released and restarted the container. The container is still showing up as “unhealthy” in the management tools I use.
Roon Server on NAS (Synology, QNAP, others) not updating to 2.71 build 1683 (ref#CVS9TY) [Ticket In]
Is the docker image still not reporting correctly?
It’s still reporting as unhealthy for me. This is after installing the hotfix and restarting the container.
My system NAS Synology would not install the hotfix, stops with an error.
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
· Can't update to release 2.71 build 1683 on Docker
Tell us about your home network
· pfSense router, Zyxel switches, Docker on QNAP
Hey @Alan_Sparks,
Thanks for writing in! From a fresh Roon Server diagnostic, we can see that your Aug 4 update worked correctly. The logs show 2.71 build 1680 downloading, installing, and staging cleanly, and since you’re now running 1680, the restart applied it as intended. Updating inside your Docker container isn’t broken.
If you can, please restart the container. Then click through the update as you did on the 4th. A plain stop/start in Container Station is all that’s needed, not a redeploy or recreate.
If it still doesn’t offer 1683 after a restart, let us know and we’ll pull a fresh diagnostic report. Thank you!
Thanks for the reply. I restarted the application and tried the update again. Unfortunately it again responded with the same “error checking for an update” message.
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
· Roon on Synology NAS container reports a problem. Hotfix update is offered but fails to install
Tell us about your home network
· Plain Jane Fritz 6690 with several unmanaged switches, almost all of the endpoints wired. No network performance issues anywhere. No VPN
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
· Roon Server will not update to 2.71 build 1683.
Roon Server is running in QNAP Container station and has always updated successfully in the past.
I've read that build 1683 is for specific hardware, so can this be safely ignored, or should I redeploy the container?
Tell us about your home network
· Ubiquiti firewall, switches, access points. Roon Server is running in the same VLAN as the endpoints.
Exactly the same here
I have tried restart the Roon server app in the container as well as restart the NAS, both doesn’t resolve the issue!
Hey @KMM,
Can you please use these instructions to access your Synology logs, upload them to our secure uploader linked below, and let us know once uploaded so that we can check?
https://workdrive.zohoexternal.com/collection/nocvrfc5b2ddab55140af8640f1d7ce13291e/external
Also, do you happen to have the YAML file you used for the container install? Or do you recall if you had network mode set to Host when you set it up?
This is a known issue that’s being worked on in the GitHub for the Docker container. It’s looking for a DLL, and Roon is now using an EXE, so that’s what’s causing the problem. It’s just a cosmetic problem, really. I think someone posted a fix this morning in GitHub. Don’t quote me on that 
Thanks for getting back to me. I am away from home until August 15th and then check on that.
Please keep the ticket open.
Thank you
Hi @Mark_Barter, @Patrick_Choy, @Piotr_Pekala,
Thank you for your posts.
The hotfix targets MacOS and RoonOS operating systems only, so it shouldn’t affect your QNAP setups. Remaining on build 1680 shouldn’t have any adverse effects.
Are you all currently able to use Roon and connect to your remotes without issue?
Same issue on my end. I thought it was my docker app, so I reinstalled it. Now I am stuck o 2.66 build 1658 with no possibility to go back to 2.70 as the latest version of roon available is giving these errors. V2.66 is giving me playback issues with track being loaded slow and then skipping the music file and starting the next one. I guess that is due to outdated information on blueos as that is the player I am testing with. For me this is an issue as I have 3 bluos devices in the house.
