Home » CloudZat UK » Set up Syncthing on TrueNAS with the right datasets and permissions

Set up Syncthing on TrueNAS with the right datasets and permissions

CLOUD BACKUP & PHOTO LIBRARIES

The important part of Syncthing on TrueNAS is deciding which dataset the app can change. A clearly separated sync dataset is easier to protect than granting the application access to an entire pool.

Editorial review: 15 November 2026 · UK

Quick answer

Use the Syncthing app instructions for your TrueNAS release. Persist its configuration, mount a dedicated dataset and align the app’s user permissions with the intended read/write workflow.

Steps to follow

  1. Before you start

    Choose the current package and record its runtime and file-ownership settings. Prepare dedicated configuration and test data locations. Preserve a recoverable copy before connecting an existing dataset, and note both host and internal folder paths.

  2. Set up the right scope

    Check the current TrueNAS app catalogue and deployment guide. Create a dedicated data location and a separate configuration location, then record the app’s configured user and group. Take a recoverable snapshot before connecting an existing populated dataset.

  3. Apply the relevant settings

    Install the supported app with the chosen host paths and appropriate permissions. Open its management interface through the documented local route, pair the second device and verify its device ID. Add a test folder using the path visible inside the app.

  4. Complete the first run

    Transfer a small sample in both intended directions and confirm its owner and permissions from TrueNAS. Restart the app, recheck the files and schedule dataset snapshots or a separate backup with enough retention for accidental changes.

Decisions and checks

The limitation that matters

Do not follow an old Kubernetes deployment recipe on a newer Docker-based TrueNAS installation. A receive-only Syncthing folder can still receive deletions from a peer; it does not replace snapshots or an independent backup.

How to verify the result

Confirm that a peer’s edit arrives, that an authorised SMB user can open the file if required, and that a prior version can be restored to a separate location without disrupting the current share.

Keep the result reliable

Recheck mapped datasets and new-file ACLs after app or storage changes. Confirm the identity after recreation and monitor snapshot or backup retention. Periodically recover a sample outside the active share before deliberately reintroducing it.

Give the synchronization app a defined dataset and a tested recovery boundary

Check the current catalog package rather than an old chart

Identify the supported Syncthing app for your installed TrueNAS release and read its current storage, network and user settings. The modern catalog entry and an older Kubernetes-based deployment can describe different procedures. Record the package version and the Syncthing version separately. Also distinguish the container's runtime context from settings that control file ownership; do not assume another image's default user ID applies to this package. Read the installed package's description and inspect the resulting files. If the service is already in use, retain its configuration and a recovery copy before changing deployment methods. Reinstalling an app with new empty settings is not an ordinary upgrade of its previous identity.

Limit the mapped data to the actual sync task

Create a dedicated test dataset or subdirectory and a persistent configuration location. Map only the required data rather than giving the application an entire pool. The path entered in Syncthing must match the location visible inside the app, which may differ from the host dataset path. Verify a known test file through that mapping before pairing a populated archive. This protects against accidentally selecting an empty directory with a similar name. Keep a diagram of host paths, internal paths and the devices sharing each folder. It becomes useful when replacing a pool, moving data or diagnosing why an apparently healthy app sees a different collection from the NAS file browser.

Test ACL behavior from both the app and the human user

Configure the dataset permissions using the current app's documented requirements. Confirm that Syncthing can create and update the test files, then inspect ownership and effective access from TrueNAS. If the same data is shared over SMB, test an authorized ordinary SMB account too. An administrator's access does not establish that either of those identities has the right permissions. Avoid granting broad pool access to make a single write succeed. Preserve the previous ACL before adapting an existing populated dataset and make one focused change at a time. Also inspect newly created files, because their inherited permissions may differ from older files that were fixed manually during setup.

Decide whether the NAS is a peer or a receiving copy

If people edit files directly through the NAS share and on other devices, the folder is participating in a multi-writer workflow. If the NAS should only receive the workstation's authoritative state, select the appropriate folder types on each device and test them. Receive Only can still apply deletions received from its peers; it is not an immutable archive. Preserve any pre-existing NAS-only files before introducing a one-way arrangement. Treat Override Changes and Revert Local Changes as decisions about competing states, not general error-repair buttons. Inspect useful differences and copy them outside the synchronized folder before using a control that may discard them.

Keep missing storage from becoming an empty valid source

When Syncthing reports a missing folder marker, first confirm that the expected dataset or mount is present and contains the real files. Do not create a marker immediately in an empty replacement path just to remove the warning. The marker helps distinguish unavailable storage from intentional removal of its contents. If the data is intact and only a cleaning tool removed the marker, follow the documented correction and prevent that cleanup from recurring. Restart the app after a controlled storage change and verify the mapped contents before resuming the full workload. A directory's existence alone is not enough to establish that the correct storage has returned.

Recover without rolling a live sync relationship backward blindly

Use snapshots or an independent backup with retention appropriate to the workload. A snapshot on the active pool is useful for some mistakes but does not survive total pool loss. For a recovery test, restore the needed file to a separate location and inspect it before introducing it back into the live share. Rolling a whole active dataset backward while peers continue editing can create a confusing new set of changes. Preserve current useful work and follow a deliberate coordination procedure for a larger recovery. If using Syncthing versioning, remember that it archives received remote changes on the configured device, not all local edits performed through that NAS share.

Example: synchronization is green but the SMB user cannot open a file

Suppose a newly transferred document is present and both peers report completion, yet a colleague receives access denied through SMB. The transfer itself may be correct while the resulting ownership or ACL is wrong for the SMB user. Compare that new file with a working older document and inspect inherited permissions. Correct the intended access rule on the test area, then transfer another sample to confirm the fix applies to future files as well. Do not restart the entire synchronization relationship or delete the remote copy to solve a local sharing permission. Validate the human workflow as well as the app's transfer status.

Compare the options

Situation / component Purpose / action What to check
Sync succeeds, SMB access fails Inspect new-file ownership and ACL App access and human-user access differ
Receive Only folder loses a peer-deleted file Check intended propagation and retention Receive Only is not an immutable archive
Dataset or marker is missing Confirm real storage and content first Do not validate an empty substitute path

Frequently asked questions

Can I use a whole-pool writable mount for convenience?

Map the specific dataset needed by the task. Broad access increases the scope of mistakes and makes permissions harder to reason about; test a limited folder and the actual authorized users first.

Should I roll back the dataset while peers keep running?

Plan a coordinated recovery rather than blindly changing the live state. For a simple file recovery, restore separately, inspect the content and deliberately reintroduce it after preserving current useful changes.

Official documentation

This guide combines current official documentation with practical recovery checks. It does not claim hands-on testing of your installation. Menu labels and supported procedures can vary by release; follow the documentation for your installed version.

Scroll to Top