Jump to content
linuxserver.io

[Support] Linuxserver.io - Syncthing

155 posts in this topic Last Reply

Recommended Posts

On 5/11/2018 at 7:05 AM, NewKrewLinux said:

I managed to get this to sync with my devices perfectly over LAN using the info I provided below.

 

But I still have one problem. I am unable to directly add a file to a folder via Windows Explorer on my SMB share. That is, I cannot drag and drop a photo into the
//Server/Storage/sync/My_Folder directory to be sent to my other devices. It says "permission denied" in Windows. How do I fix this?

 

 

_________________________________________________________

 

 

Just letting you guys know. I had to swap my interface from "Bridge" to "br0" for this to work properly. Otherwise I also got the issue with it not connecting ever again after 15 mins. Also disabled the relay on all of my devices to first properly work out the LAN issues I was having, because if after a certain time a LAN connection can't be made it'll just move to using a relay and it's sort of hard to work out if it's using the relay (gotta scour the log, or look at the slow speed etc). In addition to that I added the port "22010" to the port mappings before installing the Docker app. Then I changed the listen address in the app to "TCP 22010" because having it set as "default" causes a "connected to myself, not supposed to happen" error every 60 seconds.

 

Then I set the listen address on each of my devices as follows TCP 22011, 22012 etc. and port forwarded these over my router. Not sure if I had to do these 2 steps but I did it anyway.

 

After this I re-enabled the relay so my files can sync when I am away from home. Over LAN I'm able to get just up to 50MB/s transfer speeds (Smartphone is the bottleneck) which is much, much higher than Nextcloud which used to only get me about 10MB/s. Probably due to less overhead and not having to write to a DB etc.

 

Hope this helps someone and thanks for providing this app.

Regarding the 'permission denied' issue. The resolution on this side kicked in after running the /Tools/DockerSafeNewPerms which corrected the directories and their permissions.

 

(update)

Buuuuut. It does seem that anything new/created such as syncing a new folder will inherit the original permissions upon creation and the 'permission denied' kicks in again.

Edited by DirtyHippy
update

Share this post


Link to post

I'm having this same permissions issue.  

 

I just ran DockerSafeNewPerms which fixed all the files created by syncthing, however, I can't modify new files created by syncthing.  Can I somehow pass to the docker to create the files as 777 or some such thing?  

 

Worst off maybe schedule DockerSafeNewPerms to run daily at night... not an ideal solution.  

 

FYI my speed seems fine.  I had to turn off everything but local discovery, and changed my server's ip from dynamic to it's actual ip.  Things go much faster now, although still slower than transferring files in windows explorer.

Share this post


Link to post
9 hours ago, Mysticle31 said:

I'm having this same permissions issue.  

 

I just ran DockerSafeNewPerms which fixed all the files created by syncthing, however, I can't modify new files created by syncthing.  Can I somehow pass to the docker to create the files as 777 or some such thing?  

 

Worst off maybe schedule DockerSafeNewPerms to run daily at night... not an ideal solution.  

 

FYI my speed seems fine.  I had to turn off everything but local discovery, and changed my server's ip from dynamic to it's actual ip.  Things go much faster now, although still slower than transferring files in windows explorer.

Still digging around and since Resilio operates in a similar fashion and we have a thread based on that. There was a mention (thanks to SelfSD) suggesting a variable of UMASK_SET with initially a 0777 but others utilized a 0000 with a good result. Check up on the following responses after that initial post, seemed to work well for them.

 

Share this post


Link to post

This is a syncthing issue, not a docker issue, but thought I'd ask here in case someone has also had this issue:

 

I've just installed Syncthing on 2 unRAID servers. The use-case here is one of the servers is a snapshot backup of the main server.

So My main server (sender) sends all data to the other (receiver) unraid server, with versioning enabled. 

 

On the sender server, i've given syncthing readonly access to the whole array /sync/ -> /mnt/user/

and on the receiver server, I've created a share, and given syncthing read/write access /sync/ -> /mnt/user/syncthing/

 

I've created a folder in the GUI as follows:

source: /sync/MediaServer/Home Videos

send only, no versioning at the moment.

Share with receiver server.

 

This fails because the SOURCE is read-only and syncthing attempts to write to the source folder

I'm not going to give syncthing read/write access to all my data. It should only need read access to read and send the data to the other server.

 

Anyone know how to do this?

 

Syncthing Error message:

Quote

2018-12-26 12:50:14: Saving .stignore: open /sync/MediaServer/Home Videos/.syncthing.tmp.105273867: read-only file system

2018-12-26 12:50:14: Failed to create folder marker: mkdir /sync/MediaServer/Home Videos/.stfolder: read-only file system

2018-12-26 12:50:14: Error on folder "MediaServer / Home Videos" (q4esr-ishsp): folder marker missing

2018-12-26 13:11:35: Saving .stignore: open /sync/MediaServer/Home Videos/.syncthing.tmp.669697141: read-only file system

 OK

 

Edited by jj_uk

Share this post


Link to post

Having a problem getting Syncthing connected to remote server.

 

I'm having problems getting Syncthing to connect to an instance I have running on a seed box.  I've used Syncthing in the past, but this is my first experience in using it as a docker under Unraid.  The gui is showing the listeners as 0/1 (in red) with the following message " tcp://10.0.30.xxx:22000: listen 10.0.30.xxx:22000: bind: cannot assign requested address"

 

I've got 22000 assigned in the docker.  I've tried port forwarding from my router to my ip address of Unraid.  I'm not certain what I'm missing at this point.

I'm running Unraid 6.6.6 in Vlan 30 of my managed switch

 

Anyone have any ideas?

 

Never mind.  I had to completely uninstall the docker and my user settings and then re-install everything.  That fixed the problem.

Edited by Moose_Flunky

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now