[Support] Linuxserver.io - Syncthing

[BjornH]

6.9.2. Thought I'd just clarify regarding the specifying of pathways in SyncThing. I'm transferring files from a backup server to my Plex Share "PlexMedia" within Unraid. I specified the folder path as /sync/PlexMedia, SyncThing was able to see the share and is now transferring files. One issue however was upon navigating to the PlexMedia share on Unraid from my desktop, I found the folder to be empty. Is there a chance I may be specifying the wrong directory and inadvertently sending the files elsewhere? I have a screenshot below for context. 

[kwatz]

I am running Syncthing between my local Unraid machine and a remote linux server. I had great success for many months until recently when sync speeds dropped to around 500kbps. I have gigabit speeds and typically get 30-50 MBps sync speeds. When I restart syncthing on either end, speeds go back to 30-50 MBps for a few minutes, before immediately dropping down to 250-500kbps. I have turned off relaying and still experience the same issue. Below is the log from the remote server from boot up to when the issue resurfaced. Nothing seems out of the ordinary:   2021-07-02 03:34:38 My ID: [remote server ID] 2021-07-02 03:34:39 Single thread SHA256 performance is 278 MB/s using crypto/sha256 (275 MB/s using minio/sha256-simd). 2021-07-02 03:34:40 Hashing performance is 234.16 MB/s 2021-07-02 03:34:40 Overall send rate is unlimited, receive rate is unlimited 2021-07-02 03:34:40 Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=[discovery id] 2021-07-02 03:34:40 Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=[discovery id] 2021-07-02 03:34:40 Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=[discovery id] 2021-07-02 03:34:40 TCP listener ([::]:22000) starting 2021-07-02 03:34:40 Ready to synchronize "completed" (76xvq-hmumr) (sendonly) 2021-07-02 03:34:40 QUIC listener ([::]:22000) starting 2021-07-02 03:34:40 ... 2021-07-02 03:34:40 GUI and API listening on [::]:8384 2021-07-02 03:34:40 Access the GUI via the following URL: http://127.0.0.1:8384/ 2021-07-02 03:34:40 My name is "remote server name" 2021-07-02 03:34:40 Device [Unraid ID] is "Unraid server name" at [dynamic] 2021-07-02 03:34:44 Completed initial scan of sendonly folder "completed" (76xvq-hmumr) 2021-07-02 03:34:49 quic://0.0.0.0:22000 detected NAT type: Symmetric NAT 2021-07-02 03:34:54 Detected 1 NAT service 2021-07-02 03:35:31 Established secure connection to [Unraid ID] at [remote server ip]:22000-[local ip]:24974/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256 2021-07-02 03:35:31 Device [Unraid ID] client is "syncthing v1.17.0" named "f1ac3d8880d3" at [remote server ip]:22000-[local ip]:24974/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256 Now, the log for my Unraid server, rebooted a minute or two after the remote server:   2021-07-01 18:35:19 My ID: [Unraid ID] 2021-07-01 18:35:20 Single thread SHA256 performance is 438 MB/s using minio/sha256-simd (434 MB/s using crypto/sha256). 2021-07-01 18:35:21 Hashing performance is 376.18 MB/s 2021-07-01 18:35:21 Overall send rate is unlimited, receive rate is unlimited 2021-07-01 18:35:21 Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=[Discovery ID] 2021-07-01 18:35:21 Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=[Discovery ID] 2021-07-01 18:35:21 QUIC listener ([::]:22000) starting 2021-07-01 18:35:21 TCP listener ([::]:22000) starting 2021-07-01 18:35:21 Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=[Discovery ID] 2021-07-01 18:35:21 Using discovery mechanism: IPv4 local broadcast discovery on port 21027 2021-07-01 18:35:21 ... 2021-07-01 18:35:21 Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027 2021-07-01 18:35:21 Ready to synchronize "completed" (76xvq-hmumr) (receiveonly) 2021-07-01 18:35:21 GUI and API listening on [::]:8384 2021-07-01 18:35:21 Access the GUI via the following URL: http://127.0.0.1:8384/ 2021-07-01 18:35:21 My name is "f1ac3d8880d3" 2021-07-01 18:35:21 Device [remote server id] is "remote server name" at [dynamic] 2021-07-01 18:35:21 Completed initial scan of receiveonly folder "completed" (76xvq-hmumr) 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file -1"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file 0"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file 1"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file 2"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file 3"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file 4"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file 5"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file 6"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 Puller (folder "completed" (76xvq-hmumr), item "file 7"): syncing: no connected device has the required version of this file 2021-07-01 18:35:21 "completed" (76xvq-hmumr): Failed to sync 9 items 2021-07-01 18:35:21 Folder "completed" (76xvq-hmumr) isn't making sync progress - retrying in 1m0s. 2021-07-01 18:35:31 Established secure connection to [remote server ID] at [Unraid IP address]:22000-[remote server IP address]:1026/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 2021-07-01 18:35:31 Device [remote server ID] client is "syncthing v1.17.0" named "remote server name" at [unraid IP address]:22000-[remote ip address]:1026/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256 2021-07-01 18:35:31 New NAT port mapping: external TCP address 73.5.10.244:61571 to local address [::]:22000. 2021-07-01 18:35:31 New NAT port mapping: external TCP address 73.5.10.244:24974 to local address [::]:22000. 2021-07-01 18:35:31 Detected 2 NAT services 2021-07-01 18:35:40 quic://0.0.0.0:22000 detected NAT type: Port restricted NAT 2021-07-01 18:35:40 quic://0.0.0.0:22000 resolved external address quic://73.5.10.244:22000 (via stun.syncthing.net:3478) 2021-07-01 18:35:40 Failed to exchange Hello messages with [remote server id] at [Unraid server ip address]:22000-[remote server ip address]:58672/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256: EOF The remote server does in fact have the correct version of these 9 files. Also, the "failed to exchange hello messages EOF" error precedes the speed slowdown by a couple minutes - there's no event in the log that corresponds with the slowdown. I have given a dedicated IP address to syncthing - do I need to set a static listening address and forward the port on my local network? I just left the listening addresses as default in the setup and haven't done any port forwarding. Please let me know if I can provide any additional information.

 

 

[unrno.spam]

I'm running the latest version of this container with Syncthing 1.18.0 on my my UnRaid-System.

Is there any way to avoid error logs to fill up my cache drive?

I had once a problem with syncing over night and there were tons of error logs in the container's folder.

Maybe a way to configure a certain amount of space in the config.xml?

[SohailS]

Hi Hoping someone can help me.

 

I have set syncthing up to sync the photos i take on my phone to a folder on my server but when i try to delete unwanted items it says i need permission from Server\nobody to make changes

 

have i done something wrong here?

[smashingtool]

On 7/26/2021 at 7:53 AM, SohailS said:

Hi Hoping someone can help me.

 

I have set syncthing up to sync the photos i take on my phone to a folder on my server but when i try to delete unwanted items it says i need permission from Server\nobody to make changes

 

have i done something wrong here?

I came here with the exact same question. I can tell you that going to Unraid webGui > Tools > New Permissions and then running it against the share(s) with your Syncthing files will fix it so that you can edit the files that Syncthing has moved around.

Edited August 6, 2021 by smashingtool

[SohailS]

On 8/6/2021 at 2:40 PM, smashingtool said:

I came here with the exact same question. I can tell you that going to Unraid webGui > Tools > New Permissions and then running it against the share(s) with your Syncthing files will fix it so that you can edit the files that Syncthing has moved around.

Thanks for the info.  i have also found that if you create the root folder yourself the files syncthing place in it are also ok 

[blaine07]

Anyone else seeing basically persistent "connection error" with this? I open it in browser and every 15-20 seconds it pops up. Not seeing anything prevalent in logs.

Anyone have any ideas at all?

[widdefmh]

The instructions is not that informative when installing syncthing..
The instructions says:

-v /data1 Data1

-v /data2 Data2

But what is Data1 and Data2??? Please, make a better explanation rather than just describe it as data1 and 2.  Sorry, but you can rather left the description out rather than print the same again.

[Viper-694]

On 10/31/2021 at 4:52 AM, widdefmh said:

The instructions is not that informative when installing syncthing..
The instructions says:

-v /data1 Data1

-v /data2 Data2

But what is Data1 and Data2??? Please, make a better explanation rather than just describe it as data1 and 2.  Sorry, but you can rather left the description out rather than print the same again.

The naming here is confusing but the data1 and data2 are the directories that you are passing into the container. For example, if you want to pass you Media share into the container you'd put /mnt/user/Media into Path /data1.

Now everything in your Media share will show up in /data1 directory within the container.

Same thing with data2. I'm only using syncthing to sync my media share with another unraid server so I removed the data2 variable. 

[Soiled.Tomato]

So I've been trying to figure out what I believe should be a permission issue. I have 4 syncthing installs on various boxes (Unraid, 2x Windows, Synology). I can get Windows > Unraid to pair just fine as well as Windows > Synology. However, I cannot seem to get Unraid > Synology or vice versa. Both Unraid and Synology run linuxserver io Syncthing docker. The connection addresses on each of those, when left to dynamic show several relay addresses and my public facing ip.

 

At no point can I get them to see the other syncthing instance's machine ip.

I thought maybe the Unraid host was being firewalled or something in that nature but a ping check from the host to the other machines and WAN shows everything is working normally.

 

I've dug through the docker documentation as at one point I believed it to be related to the networking setting within each docker image, but that seems to have turned out being incorrect.

A different forum resource along with the syncthing github made it seem like there could have possibly been a bug in the 1.18.x version of syncthing but i don't know much more than that atm.

 

EDIT: I forgot to add that when I connect from either Unraid/Synology with Windows I can see their static IP. I'm not entirely sure what IP I see from windows to Unraid but I believe that sees a relay. Will double check since it seems important to be sure of.

EDIT2: In the docker tab under the configured port access mappings, which cannot be changed in the image config settings, these address mappings show up:

172.17.0.5:21027/UDP10.130.1.243:21027
172.17.0.5:22000/TCP10.130.1.243:22000
172.17.0.5:22000/UDP10.130.1.243:22000

These seem to look very similar to the addresses syncthing is using in one of my other screenshots with a 172.17.x.x address. I’ve thought about adding these addresses as virtual IP’s to the firewall but have no real reason to believe they are even coming up on its end.

EDIT3: Issue resolved. Adding in firewall rules to the Unraid and Synology boxes to the NIC of the firewall allowed them to communicate. Something seems off there tho as I do not have any static routes that would route traffic in traffic this way. I’m inclined to believe the possible bug issue from the other forum resource i mentioned is the cause. SyncTrayzor seems to be wrapped around a previous syncthing build that didn’t map traffic in this manner but I cannot be certain as I do not recall a syncthing version mentioned in there before.

Edited December 11, 2021 by Soiled.Tomato

[fxhe]

Hi, I want to use syncthing in lscr.io/linuxserver/syncthing but I dont understand the meaning of paths for data1 and data2. Can you give me more infomathin about the paths? Thanks.

[Ghostwalker42]

HI Guys, 

 

I dont know if this the place for some Syncthing help. I have move my docker images and configs from one drive to another drive and now i'm getting a weird error when i spin up the syncthing container. when the container starts i get a " WARNING: Failed to load/generate certificate: save cert: open /config/cert.pem: permission denied" in the log files. The data is stored on and drive  using unassigned drives. 

 

Any help with this would be great. Thank you. 

[VictorCharlie]

I have used Synching for a while on other devices.  I have 2 server on the same LAN. One is set to send only and the other is set to receive only. The servers show connected and appear to be fine. I have 6 shared folders between them. The send only server shows the receive only server as out of sync but no files are transferring to the other system. Can anyone help me figure out why nothing syncs?

 

I have removed and reinstalled both dockers several time. I can not see anything obvious in the logs.

[fxhe]

On 1/11/2022 at 6:23 AM, VictorCharlie said:

I have used Synching for a while on other devices.  I have 2 server on the same LAN. One is set to send only and the other is set to receive only. The servers show connected and appear to be fine. I have 6 shared folders between them. The send only server shows the receive only server as out of sync but no files are transferring to the other system. Can anyone help me figure out why nothing syncs?

 

I have removed and reinstalled both dockers several time. I can not see anything obvious in the logs.

You must keep the folder ID in both sides of a Synching same.

[unrno.spam]

On 7/21/2021 at 10:33 AM, unrno.spam said:

I'm running the latest version of this container with Syncthing 1.18.0 on my my UnRaid-System.

Is there any way to avoid error logs to fill up my cache drive?

I had once a problem with syncing over night and there were tons of error logs in the container's folder.

Maybe a way to configure a certain amount of space in the config.xml?

 

After updating to 1.19.0 I still see no option to limit the space for error logs. Does anybody know a way to handle this or at least get notified by e.g. mail?

Edited February 19, 2022 by unrno.spam
spelling

[lumpenherr]

So perhaps this is an embarrassing question, but while I got the docker running just fine and syncing up with devices works, the location of the folders on the Unraid server side are not where I want them to be. Perhaps I am gravely misunderstanding how the /data1/ and /data2/ folders are supposed to work.

 

I want the synced folders on my PCs/Phone to be stored and show up in a separate SMB share so I can read & write to the folders from my File explorer. I created a share in Unraid, lets call it 'sync'.

In my docker setup I put in the appdata in (as per default) :

/mnt/user/appdata/syncthing

 

and for  "Path: /data1:"  I put in the created share:

/mnt/user/sync/

 

Started up the docker, it works just fine, the default folder is at "/config/Sync" , i.e. the appdata/syncthing/Sync folder (not sure if it is named "sync" by default or if it is because I named the data1 folder "sync").

So the folders in syncthing are now WITHIN the appdata subfolder, not in the desired separate "sync" share

 

 

I tried changing the default folder (and shared folders from other devices) to be in /sync/ instead of /config/sync but then I get a permission denied message.  

If this is not possible, should I create a share in Unraid for the default folder within the /appdata/syncthing/ folder? Or do I need to share the whole appdata/syncthing folder? I'd like to avoid that if possible.

 

Thanks for the help  

 

Edited June 28, 2022 by lumpenherr

[kmarq13]

On 1/7/2022 at 8:46 PM, Ghostwalker42 said:

HI Guys, 

 

I dont know if this the place for some Syncthing help. I have move my docker images and configs from one drive to another drive and now i'm getting a weird error when i spin up the syncthing container. when the container starts i get a " WARNING: Failed to load/generate certificate: save cert: open /config/cert.pem: permission denied" in the log files. The data is stored on and drive  using unassigned drives. 

 

Any help with this would be great. Thank you. 

 

 

@Ghostwalker42 were you able to resolve this? I'm having the same issue suddenly after having been running the container for years. 

[Dusterz]

Hi, can anyone please tell me how to restart the docker one time with -reset-deltas ? I have a read-only folder that which is showing an incorrect 'Global State' count. The 'master / send-only' device is online but restarting either/both devices, hitting the rescan button, etc does not correct the mismatch. Logs show no errors. Hopefully the -reset-deltas  command will fix it. (The folder is 50TiB so i really don't want to have to delete it and start again!). Thanks! Dusty

[Netix]

On 10/26/2020 at 7:24 AM, Rysz said:

For anyone experiencing write-permission errors on Samba shares as I did, please make sure that:

• Syncthing Container (Docker) configuration has a configuration key set as follows:
  UMASK_SET => 000 (UMASK_SET as "Key" / 000 as "Value")
  
  Such a key can be added by clicking on "Add another Path, Port, Variable, Label or Device".
  
  
   
• to enable "Ignore Permissions" on each individual shared folder inside the Syncthing Web UI on your UNRAID machine.
  

 

I have been investigating for hours why my files would keep ending up with the wrong permissions despite the supposedly correct UMASK of 000. Syncthing will, by default, try to synchronize the file permissions when exchanging data between two machines - beware of this functionality. Especially if you sync folders between another Linux machine and your UNRAID machine, Syncthing will initially create the file on your UNRAID machine respecting the UMASK 000 but later modify the permissions to reflect those on the original machine.

 

By ensuring that your synced folders are all set to "ignore permissions", you basically tell Synthing to stay out of setting permissions altogether and respect the default local permissions. (which you have previously set by handing the UMASK 000 to the container)

 

Hope this helps anyone experiencing permission troubles on Samba shares. 🙂

 

Thanks ! Had permission issue and that did the trick. I managed to reroute my download folder to an unassigned device. 

[tribble222]

For anyone from the future encountering the issue:

WARNING: Failed to load/generate certificate: save cert: open /config/cert.pem: permission denied

 

I was able to solve it with chmod nobody:users -R /mnt/user/appdata/syncthing and ensuring I had PUID and PGID set to 99 and 100 respectively, in the container's docker config.

Edited November 7, 2022 by tribble222

[Henke]

Hello beautiful people! I'm experiencing a new issue with Syncthing (linuxserver) on Unraid these last few weeks, possibly something that occured after upgrading Unraid to 6.11.1(?). I saw a post about similar issues on the Syncthing subreddit as well, so it seems I might not be the only one.

 

I'll mention that I'm somewhat a Unraid and homeserver/linux rookie.

 

Issue:

Syncthing is all of a sudden refusing to delete directories in "receive only"-folder on Unraid because they're not empty. This has never been an issue before. The directories are supposed to be deleted with content as they're deleted or moved from my seedbox's "send only"-folder. Interestingly, the issue might be limited to folders that have been "touched" by Sonarr/Radarr (on Unraid).

 

Setup/how it used to work:

1. On my seedbox, completed downloads are automoved to a "completed" directory. This directory is a "send only" folder in Syncthing.
2. Content in "completed" folder are synced to "receive only"-folder on Unraid server. This folder is monitored by Sonarr/Radarr. Sonarr/Radarr, in turn, hardlinks these downloads to their designated directories elsewhere.
3. On seedbox: After some time the download will either get moved to a different directory, or deleted. Both of these options means that the download is removed from the "send only"-folder, and when synced by Syncthing, also deleted from my "receive only"-folder on Unraid. It's all nice and clean and just how I like it.

 

Past few weeks (I think):

• When the download is moved/deleted on seedbox (step 3), Syncthing (on Unraid) will eventually just show the red "Out of sync"-warning. The out of sync items are the downloads (usually directories) that no longer exists on the seedbox side, and therefore should be deleted on the receiving end. Syncthing on Unraid states, however, that the directory/directories could not be deleted because they're not empty.
• The directories does not contain any hidden files (as far as I can tell), and I can't find anything else that seems odd with these folders...
• Pressing the "Revert local changes"-button removes the directories with their content, and "fixes" the problem, but I obviously don't want to keep doing this manually.
• Maybe an important detail: This seems to only happen to content that's been "touched" by Sonarr/Radarr before removal. If I create a new directory with a few files on the seedbox, let it sync, and then delete it, it is successfully deleted on Unraid as well.

 

This is driving me crazy. Any ideas?

 

Side note: I also feel like scanning takes a lot more time now than it used to as well, although I cannot be completely sure. I do however often see the scans taking a long time (like several minutes for one 10GB movie file or something like that), with very high CPU usage (like 80% on all cores, i5-8400), while I never noticed this earlier, so something seems to have changed.

 

Both Syncthing installs are v1.22.1. Unraid 6.11.2 (same issue on 11.1).

 

Edit: I just checked the logs a little closer and found this:

• First, it says "directory has been deleted on a remote device but contains changed files, scheduling scan"
• Then it rescans
• And finally it says "directory not empty".

 

Edited November 10, 2022 by Henke

[ikyn]

I'm having the exact same issues as the poster above.

In addition, however, Syncthing completely IGNORES my CPU pinning. It will use all cores even if I have pinned a certain number, such as 4 of my 12.

[Magic815]

On 11/10/2022 at 2:37 PM, Henke said:

Hello beautiful people! I'm experiencing a new issue with Syncthing (linuxserver) on Unraid these last few weeks, possibly something that occured after upgrading Unraid to 6.11.1(?). I saw a post about similar issues on the Syncthing subreddit as well, so it seems I might not be the only one.

 

I'll mention that I'm somewhat a Unraid and homeserver/linux rookie.

 

Issue:

Syncthing is all of a sudden refusing to delete directories in "receive only"-folder on Unraid because they're not empty. This has never been an issue before. The directories are supposed to be deleted with content as they're deleted or moved from my seedbox's "send only"-folder. Interestingly, the issue might be limited to folders that have been "touched" by Sonarr/Radarr (on Unraid).

...

 

On 11/26/2022 at 2:08 PM, ikyn said:

I'm having the exact same issues as the poster above.

In addition, however, Syncthing completely IGNORES my CPU pinning. It will use all cores even if I have pinned a certain number, such as 4 of my 12.

 

I'm curious - do you both still have this issue? I'm on UnRAID 6.10.3, and would like to upgrade to 6.11.x at some point soon, but I'm worried it's going to mess up my Syncthing docker container.

 

Also, question for everyone: What 'network type' did you select for your Syncthing docker container?

[Henke]

20 minutes ago, Magic815 said:

 

 

I'm curious - do you both still have this issue? I'm on UnRAID 6.10.3, and would like to upgrade to 6.11.x at some point soon, but I'm worried it's going to mess up my Syncthing docker container.

 

Also, question for everyone: What 'network type' did you select for your Syncthing docker container?

Yes and no; I changed my Syncthing shares to "Send & receive" on both ends instead of "send only" and "receive only" on the seedbox and Unraid respectively. Works as expected for my use case and solved my problem, so I haven't tried changing it back. I was afraid that deleting (or moving) something on my seedbox would trigger a sync from Unraid to the seedbox with this setting, but luckily that has not been an issue.

 

As to your question about network type, I'm routing the Syncthing container through the network of another, VPN-enabled, docker container (binhex-privoxyvpn). Not really sure if this is needed, but I feel like this provide an extra layer of privacy.

 

Edit: I'm running latest version of both Unraid and Syncthing.

Edited December 27, 2022 by Henke

[Januszmirek]

On 6/28/2022 at 7:57 PM, lumpenherr said:

So perhaps this is an embarrassing question, but while I got the docker running just fine and syncing up with devices works, the location of the folders on the Unraid server side are not where I want them to be. Perhaps I am gravely misunderstanding how the /data1/ and /data2/ folders are supposed to work.

 

I want the synced folders on my PCs/Phone to be stored and show up in a separate SMB share so I can read & write to the folders from my File explorer. I created a share in Unraid, lets call it 'sync'.

In my docker setup I put in the appdata in (as per default) :

/mnt/user/appdata/syncthing

 

and for  "Path: /data1:"  I put in the created share:

/mnt/user/sync/

 

Started up the docker, it works just fine, the default folder is at "/config/Sync" , i.e. the appdata/syncthing/Sync folder (not sure if it is named "sync" by default or if it is because I named the data1 folder "sync").

So the folders in syncthing are now WITHIN the appdata subfolder, not in the desired separate "sync" share

 

 

I tried changing the default folder (and shared folders from other devices) to be in /sync/ instead of /config/sync but then I get a permission denied message.  

If this is not possible, should I create a share in Unraid for the default folder within the /appdata/syncthing/ folder? Or do I need to share the whole appdata/syncthing folder? I'd like to avoid that if possible.

 

Thanks for the help  

 

Had exact same issue with my config. Tried to troubleshoot it for hours with no luck. Finally switched to binhex container and it works flawlessly.