RoonServer Docker on Synology fails to trigger restore and login hangs (ref#NMXP79)

Support
1

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

· Subject: RoonServer Docker (official image) — restore never triggers, login redirect hangs indefinitely

System details:
- Synology DS918+, DSM 7.2.2-72806
- Official RoonServer Docker image (ghcr.io/roonlabs/roonserver:latest), Roon 2.71 (build 1683) production
- Migrating from a community Docker image (steefdebruijn/docker-roonserver) to the official image
- Container run with: --net=host, -v :/Roon, -v :/MyMusic, -v :/Backup, TZ=Asia/Manila
- Library: ~5,000+ albums, Roon backup file is ~8GB

What I'm trying to do:
Migrate my existing library/database from the old container to the new official Docker image using Settings > Backups > Restore, as documented for this migration path.

What's happening:
1. On a fresh container, Roon Remote reaches the Login/Sign-up screen with "Restore a backup" at the bottom.
2. I select "Restore a backup" and choose today's backup from the /Backup mount. The Backup Manager screen appears briefly ("twiddling"/in progress).
3. It then returns to the Login screen. Tapping Login opens my browser, which is already signed in (no password prompt) and shows "Redirecting..." indefinitely, with a fallback "click here" link that just repeats the same redirect loop.
4. Closing the browser and returning to Roon Remote shows the "Add your music" fresh-setup screen (0 tracks/albums), not a restored library.
5. This repeats consistently across many full quit-and-relaunch cycles of Roon Remote, on both Windows PC and Android phone (including testing the phone on mobile data instead of home WiFi, to rule out our router's double-NAT — no change).
6. A full restart of the roon-official container did not change the behaviour.

What I've verified myself:
- The backup file is present and appears valid on disk: correct folder structure, _roon_backup_root_ marker file present, dated correctly, reasonable size for our library.
- RoonServer_log.txt on the server shows the server running normally and successfully reaching Roon's cloud services (device registration, discovery, etc. all returning 200 OK), but shows zero restore-related activity in the log at any point — it appears the restore step is never actually triggered server-side.
- Library stats in the log consistently show 0 tracks, 0 albums, 0 playlists throughout.
- Separately, the log shows a port test to your servers returning a 504 and detecting "MultipleNatFound" on our network — not sure if this is related to the login handoff failing, but flagging it in case it's relevant.
- Our original (non-official) Docker container remains stopped but intact throughout, so we've been able to safely roll back each time without any data loss.

What I'd like help with:
Understanding why the restore/login handoff isn't completing, and whether this is a known issue with the official Docker image on Synology, or something specific to our account/network that support can see from your side. Happy to provide further logs or try anything you'd like tested.

Tell us about your home network

· Asus RT-AC1900P,

2

Hello @John_Rainey

That is an unusually complete report, and it saves us a round trip. Two things we can settle first, then the sequence we would like you to follow.

The 504 and MultipleNatFound are not related. Those come from the ARC port test, which checks whether your server is reachable from outside your network. MultipleNatFound is Roon reporting more than one router doing NAT, which matches the double-NAT you already mentioned. It affects Roon ARC only, and has nothing to do with the restore or the login.

Your container paths are wrong, and this may be the whole problem. Two of your three mounts use paths the image does not expect:

-v ...:/MyMusic should be -v ...:/Music
-v ...:/Backup should be -v ...:/RoonBackups

Only the host side of each mount, the part before the colon, is yours to choose. The paths inside the container are fixed, and our guide says so explicitly:

The easiest way to get it right is to let the generator build the configuration. Enter your timezone and your three host folders and it produces the correct mapping with the container paths already set:

Then please do it in this order, and the waiting matters.

  1. Recreate the container from the generated configuration, keeping your host paths as they are.
  2. Start it and leave it alone for ten minutes. Do not open Roon Remote yet. On first run it has to unpack and initialise, and connecting to it mid-start is likely what has been ending your restore attempts early.
  3. Open Roon on your Windows PC. If it says it is waiting, click Select a different Roon Server, and wait until your new server shows as Ready with a green indicator.
  4. Only then, log in to your account and make sure that Roon is working. Open Settings → Backups, click Restore a backup, and choose your backup.
  5. An 8 GB backup will take a long time. Afterwards Roon will ask to relaunch, and the app may look stuck or cycle between server states. That is expected.

Three things we still need, whichever way it goes:

What Roon version made that backup?

The complete container configuration, including the host paths you removed before posting and any :ro flags. If /RoonBackups is mounted read-only, the restore will not work.

Free space on the volume holding /Roon. An 8 GB backup needs considerably more than 8 GB to unpack.

If it still fails after all that, please note the clock time and your timezone, then send the logs from the /Roon mount here:

https://workdrive.zohoexternal.com/collection/nocvrfc5b2ddab55140af8640f1d7ce13291e/external

Please keep the old container stopped and intact, as you have been doing. That is exactly right.

3

Many thanks indeed. While the backup said it had completed, it started reloading the database. I’ve decided to let it run rather than fiddle any more. I’ll leave the old container for a few days before deleting. I’ll come back if it runs into any more issues. Cheers, John

4

Hey, @John_Rainey.

Thanks for letting us know. We’ll be standing by if you run into any further issues.

5

Hi, I had a few issues but I think things have settled down but the biggest mystery concerns Home. I’ve add new files but they don’t show up in home - they go straight to the artist. Is that normal?

6

It seems to be back to normal so please treat this issue as closed. Many thanks, John