NeutronSync on Unraid

Community Applications

The template lives in WilhelmZA/unraid-templates, the repository submitted to Community Applications. Until NeutronSync is listed there, add it under Apps → Settings → Template Repositories:

https://github.com/WilhelmZA/unraid-templates

Then search for NeutronSync and install from the template. The template pulls ghcr.io/wilhelmza/neutronsync:latest.

First start

Web Password (NEUTRONSYNC_WEB_PASSWORD) is optional. Start the container and find NeutronSync setup code: ... in the Unraid container log.

Open http://<unraid-ip>:8080. Enter the setup code and enter a password of at least 12 characters twice. Then sign in to Proton Drive from the Account page. The setup code changes on each start and stops working after setup. The container can become healthy before setup; sync controls remain locked.

If you supply Web Password or NEUTRONSYNC_WEB_PASSWORD_FILE, it seeds the first password and skips setup. It never replaces a saved password. Change the password under Account → Change web password; other browser sessions are signed out.

For recovery, set Web Password and add NEUTRONSYNC_WEB_PASSWORD_RESET=1, then restart. Remove the reset flag after recovery. Alternatively, remove the password variables, delete /config/web/auth.json from appdata, and restart to return to setup. Proxy mode skips both setup and login.

Paths

Narrow /data to the shares you actually sync. Leaving it on /mnt/user works but gives the container a wider view than it needs.

Session key

On first start the container writes /config/secrets/session.key next to the encrypted session file. That protects a copied session.enc alone, but not a copy of the whole /config folder. To keep them apart, set Session Key (NEUTRONSYNC_SESSION_KEY) to a 32-byte key (base64) from a Docker/Unraid secret or password manager, and do not store that key under appdata.

Unraid inotify gap

/mnt/user is the shfs FUSE union. Changes made through /mnt/user (SMB, other containers mapped there) raise inotify events. Writes straight to /mnt/diskN or /mnt/cache do not. The container's starter config sets full_walk_interval = 21600 (six hours) so the safety-net full walk catches those.

Deleted files

With local_delete = "trash" (the default), a local file removed because it was deleted on Proton Drive goes into that mount's .Trash-<uid>/files/ folder (freedesktop per-volume trash via gio). It stays on the share and can be restored from the Unraid file browser.

Updates

Unraid follows the latest tag. That tag moves when a release is promoted to stable (scripts/promote.sh), not when a pre-release is published.

To follow every pre-release, change Repository to ghcr.io/wilhelmza/neutronsync:edge; to stay on one version, use a version tag such as ghcr.io/wilhelmza/neutronsync:0.8.2.