· I am another of those users with problems using a QNAP server. I have rebooted. I have downloaded Container Station. I have tried to create a new application. I have installed the script. I have validated ir and got a green checkmark. Then I get a "loading" screen that doesn't load, and then I get kicked out. Help!!!!
Thanks for the details, and for outlining what you have already tried on the QNAP side. Please share a few screenshots of the issue, including the loading screen and the point where you get kicked out:
First, I want to sincerely apologize for the delay in getting back to you. I completely understand how frustrating it is to be stuck on a loading screen without access to your music, especially after following the migration steps. Let’s get this sorted out right now.
The “loading and getting kicked out” loop you are experiencing on your Roon Remote app almost always happens because the app is desperately trying to connect to your old native QNAP Roon application, which is now incompatible. If both the old native app and the new Docker container are running on your NAS at the same time, they cause a network conflict, and your remote gets confused.
To break out of this loop and connect to your new Docker server, please follow these exact steps:
1. Stop the old native application Go to your QNAP App Center. Find the original, native Roon Server application and click Stop (or completely remove it). It is crucial that only the Container Station version is running.
2. Force the Remote to look for the new Server Open your Roon Remote app on your phone, tablet, or computer. When it hangs on that “Loading” or “Looking for your Roon Server” screen, do not wait for it to kick you out. Look for a button or link on that screen that says Select a different Roon Server
3. Connect and Restore You should now see your new Container Station Roon Server listed (it will likely show as “Ready”). Select it to connect. Note: Because this Docker container is technically a new installation, Roon will treat it as a new Core. When prompted to log in, click the Restore a Backup link to reload all your previous playlists, settings, and play history.
Please give this a try and let us know if your Roon Remote successfully connects to the new server!
I have removed the old roon server from my qnap. It is not hanging at the poiny of selecting a new server. It is hanging on the verified image I am trying to load into Container Station. Please see above photos.
I completely understand the frustration—getting that “green checkmark” of validation only to have the system hang at the finish line is incredibly teasing.
Based on the symptoms you’re describing, it’s likely that the Roon container is hitting a “silent wall” when trying to actually write its files to the disk.
The Theory: Volume & Permissions
If Container Station was installed on a system volume that is nearly full, or on a partition with restricted write permissions, the container will “validate” just fine (as the code is correct) but will fail to actually launch the environment.
Recommended Fix: Reinstall on a Different Volume
To rule out a storage bottleneck or a permission error on your current QNAP volume, please try the following:
Uninstall Container Station: Go to the QNAP App Center and completely remove Container Station.
Reinstall and Choose a New Path: When you reinstall Container Station, it will ask you to select a “Default Folder” or Volume for your container data.
Crucial: If you have multiple Storage Pools or Volumes, try selecting a different one than before (e.g., move from DataVol1 to DataVol2 if available).
Ensure the volume you select has plenty of free space and isn’t a “Read Only” or highly restricted system partition.
Run the Script Again: Once reinstalled on the new volume, try creating the Roon application again using your validated script.
Please let us know which Volume you selected during the reinstall and if the logs show any specific error messages! We’re committed to getting your QNAP back in the Roon lineup.
