Syncs but destination changes local items immediatly

I installed Syncthing on a TrueNas system. After configuring it, I tried to add a new folder. However, it syncs and then immediately shows “locally changed items”.

My Syncthing source device folder is configured to only send to the TrueNas Syncthing.

The destination Syncthing is configured to only receive from the source.


As soon as the initial synchronization finishes, the destination Syncthing changes the local items somehow.


When I try to “revert the local changes”, the local items change again immediately.

So, I’m not sure why this is happening. Any thoughts on this matter?

I’ve had this problem for months and I’ve just ignored it. Unfortunately it looks like that’s all you can do because after digging through posts it looks like this has been a problem for years with no solution. I was gonna make my own post but it seems useless at this point.

Edit: I stand heavily corrected. I’m not sure if this would work for you but I enabled ignore file permissions on both clients and that seemed to fix it, for now at least. I found it from another post that said it didn’t work for them but I decided to give it a try and it works. I guess what doesn’t work for one might work for another.

3 Likes

The root cause here is likely that the underlying filesystem is doing something unexpected (ACLs? SMB?) and the apparent file permissions change after Syncthing syncs them. That is a local change, which Syncthing will flag unless told to ignore it.

2 Likes

Comparing the source and destination files, I still couldn’t tell what kind of permissions had changed.

After enabling the Ignore Permissions setting, the folder was “up to date” and there were no more warnings.

Thank you so much for the insights.

2 Likes

Take this with a grain of salt because I’m not experienced on the topic, but I’m pretty sure windows makes changes to the permissions in an smb share so that will be different compared to the host.