6 synced devices but 2 wont communicate with each other

Support
1

I started with 5 synced devices, and I just added a NAS as the 6th, but for some reason when I setup the final sync, one pair refuses to communicate. I re-setup it again and its the same result. There is data to be synced between them, but it gives 6 errors on both sides. What should I do?

quic://############### no recent network activity (09:30:38) quic://############### no recent network activity (09:30:38) quic://############### network is unreachable (09:30:33) tcp://################ i/o timeout (09:30:08) tcp://################ i/o timeout (09:30:08) tcp://################ network is unreachable (09:29:58)

2

Hard to tell with that little information. The two devices seem to have problems to discover each other. This is most likely caused by both of them being unable to gather their own IPs.

Are these Android or Docker nodes?

3

All synced devises are just running on Windows 10, except the new Synology NAS that I just added. The missing connect is between the NAS and one of the Windows 10 machine. Everything else communicates fine.

I apologize if i’m missing anything in response, I’m learning all of this as I go.

4

Check the network settings of your Win10 machine and make sure that your profile is set to Private.

5

That one was set to public, so I switched it to private, but its still not connecting. Just getting time-outs then unreachable in the errors.

For context aswell, All the windows machines are identical hardware, only they exists in different psychical locations and on different networks. I’m remoting in to both so I know for sure they are both online.

6

Anything else to try? Its so strange that all machines are syncing between eachother, its just this one pair does not connect.

7

Could you share the IPs that these machines are publishing(minus public ones)?

8

@bt90 How do I do that without doxing myself or my coworkers? Do i just pull the ip address/port from the browser URL when accessing the Syncthing UI? Sorry if its a dummy question, like I said, I’m learning as I go here.

9

Could you share a screenshot of the web UI?

10

@bt90 here is the webui for the windows machine I have here,

image
image1920Ă—1058 65.2 KB

11

I missed the important bit. Which nodes are refusing to connect? There’s a chance that both of them are unreachable from outside without a relay because of their NAT type or the provider only using CGNAT.

12

@bt90 Its the Nodes labeled “Peter” and “WPI_NAS”. “Peter” is the one that was set to a public network, and I switched it over to private. All the nodes talk to each other fine, I have one sync that is from my node “Joe” shared with “Peter” and “WPI NAS” and both are receiving it, they just dont send between each other.

Here is screenshot from “WPI NAS”

image
image1676Ă—1072 168 KB

13

Discovery 3/5 looks suspicious.

14

Strange, it says 4/5 now… looks like they’re all 4/5 with a “Failure to connect to IPv6 servers is expected if there is no IPv6 connectivity.” message

15

@bt90 I just caught it again when it was on 3/5 discovery, but it shortly switched right back to 4/5.

when it was on 3/5 the error was:

global@https://discovery-v6.syncthing.net/v2/: Post “https://discovery-v6.syncthing.net/v2/”: dial tcp [XXXX:XXXX:XXX:XX::XXX:XXXX]:XXX: connect: network is unreachable

16

That is expected if IPv6 is not available.

Could you check the logs of both devices and check if you can find the NAT type that is getting logged?

17

It only mentions “Nat” in the Peter windows machine log, doesnt mention in the NAS log. Peter’s log says:

2023-09-26 10:26:26 Detected 0 NAT services 2023-09-26 10:26:35 quic://0.0.0.0:22000 detected NAT type: Port restricted NAT

18

How are you running Syncthing on the NAS?

19

I’m not sure if I know how to answer that. I downloaded the app from the Synology Community app/package center. When I launch it opens its own browser tab.

20

@bt90 it keeps going from 3/5 to 4/5. but is mainly sticking to 4/5