I want to be able to Sync two Unraid server folders- both servers on same LAN. I have Syncthing working via Global settings Relay but don’t need or want internet connectivity. I changed the settings on both devices to LAN Discover and entered the IP of each in the Sync Protocol Listen Addresses box followed by port 22000. The two servers cannot connect now, what am I doing wrong? Both show as disconnected and a red connection refused. What can I do to get these two unraid folders to see each other?
Can the two Devices ping one-another using these same IP addresses? Do the logs give you any clues?
You can bypass this issue, I suspect, by setting the Remote Devices back to “dynamic” and go to Actions / Settings / Connections and turn Enable Relaying off. You can also turn off Global Discovery on the same page.
Did you add tcp:// or quic://?
tcp://192.168.1.100:22000,quic://192.168.1.100:22000
1 Like
Yes Each has tcp:// and they can each ping one another.. Tried setting it back to Dynamic on one server and had already turned off Relaying and Global Discovery. I really don’t know where to start now as I’m not that familiar with Syncthing setup. I had it working via Relay but cant over LAN!.
Not familiar with unraid but I would suspect a firewall problem. Being able to ping them doesn’t necessarily mean a tcp connection on some arbitrary port will work.
is syncthing running in a container inside the unraid?
1 Like
Yes it is. It runs okay via relay but that takes hours and hours to complete and I’d rather have it on local network for speed and security. I can use rsync etc. to connect the two Unraid boxes but can’t figure out why this should be a firewall issue.
With a relay both syncthjng containers are initiating outgoing connections. To get a local connection one needs to be able to receive an incoming connection. If you don’t have the ports open on at least one side that connection cannot happen.
Rsync is also running in a container and it works?
check to make sure your port forwards to the container are set up properly. If you’re not exposing 22000 from the container you will have a problem.
the best option is to configure the container to use “host” networking. But it’s still possible even with that, that a firewall is interfering with the connection attempt.
Where did they say that they changed the addresses to connect to make outgoing connections to remote devices with? I see that they said they changed the listen addresses though.
I recommend keeping the listen addresses as default unless you have a reason to restrict the interfaces you accept incoming connections on.
1 Like
Correct sir. I misread the original post, thinking that it was working when the Remote Devices were set to dynamic.
1 Like