· None of the above quite fits
· None of these quite match
· Docker not working with QNAP after last update
· QNAP TVS-471 Intel i3-4150 4 GB ram firmware QTS 5.2.93451 Router ORBI RBR850
To provide a bit more context.
I have downloaded and installed Roon server in the container station on the QNAP. It runs.
On a remote device (phone, etc.) QNAP server shows up as ready under the 2.65 build but will never connect to it.
Any thoughts would be appreciated.
Uh duh.
May have been obvious in retrospect, but….
When I tried to get at the Roon Server it was showing the QNAP with “ready to connect” from my devices with the option to connect. It never did.
I finally logged out/removed the QNAP from my Roon account licence, added it back in as a device, and voila, working and restoring from backup as I type. I guess this allowed a reset of a faulty path.
Just putting this out there as it wasn’t an obvious troubleshooting step. Basically a “forget this device”kind of thing
Hello @john_lingertat
Thank you so much for following up and sharing the solution you found. Unauthorizing the previous core from your account and logging back in is a fantastic troubleshooting step when a remote device gets stuck trying to connect to a newly migrated Docker instance. Sometimes the system just needs that manual “nudge” to clear out the old authorization state and establish a fresh connection to the new container.
We really appreciate you taking the time to document your experience here, as it will undoubtedly help others who might run into the exact same hiccup. I have made a note of your feedback, and if we see this connection behavior becoming a trend for users migrating to Docker, we will certainly escalate it to our R&D team to see if we can smooth out that part of the transition.
I am glad to hear your server is back up and running and successfully restoring from your backup! Please don’t hesitate to reach out if you need anything else.
Hi, similar problem here. How did you removed the QNAP from Roon account licence?
I forget the specific keystrokes, but when it ask to connect to the core on the remote device, instead go into the Roon account, delete the core from Roon access on the remote and then reconnect.