Syncthing device seen by one device but not the other

Hello. I have 3 syncthing devices, all running version 0.12.19: one at home and two at the office. The two devices at the office correctly see each other, but only one of them see the home device. The strange thing is that the node that can’t see the home device indicates a very recent time in the “last seen” field of the “invisible” device, which gets updated every few minutes. So it looks like it can contact the device but can’t really connect to it and transfer data. Any suggestions? Thanks

Check the logs. I suspect corporate firewall.

The fact is that there is no firewall. Both the office devices are connected to a simple modem/router in the same way, which makes me suspect it’s a machine-specific issue, otherwise both machines would be affected. Also, I have just noticed this, because once it used to work correctly. I’ll try and find the logs, and I will report back if I find them :slight_smile:

Here is what the log says:

[monitor] 14:49:13 INFO: Starting syncthing
[CU3KR] 14:49:13 INFO: syncthing v0.12.19 "Beryllium Bedbug" (go1.5.3 linux-arm) unknown-user@build2.syncthing.net 2016-02-14 19:26:33 UTC
[CU3KR] 14:49:13 INFO: My ID: CU3KR3F-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ
[CU3KR] 14:49:14 INFO: Single thread hash performance is ~11 MB/s
[CU3KR] 14:49:19 OK: Ready to synchronize STCloud (read-write)
[CU3KR] 14:49:19 INFO: Using discovery server https://discovery-v4-1.syncthing.net/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA
[CU3KR] 14:49:19 INFO: Using discovery server https://discovery-v4-2.syncthing.net/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC
[CU3KR] 14:49:19 INFO: Using discovery server https://discovery-v4-3.syncthing.net/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ
[CU3KR] 14:49:19 INFO: Using discovery server https://discovery-v6-1.syncthing.net/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA
[CU3KR] 14:49:19 INFO: Using discovery server https://discovery-v6-2.syncthing.net/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC
[CU3KR] 14:49:19 INFO: Using discovery server https://discovery-v6-3.syncthing.net/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ
[CU3KR] 14:49:19 INFO: Device CU3KR3F-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ is "OrangePI" at [dynamic]
[CU3KR] 14:49:19 INFO: Device CV32T6W-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ is "Amilo-Si1520" at [dynamic]
[CU3KR] 14:49:19 INFO: Device HHWREMG-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ is "RasPi Home" at [dynamic]
[CU3KR] 14:49:19 INFO: Device W35ZTEH-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ is "Luca-PC" at [dynamic]
[CU3KR] 14:49:19 INFO: API listening on [::]:8384
[CU3KR] 14:49:19 INFO: GUI URL is https://127.0.0.1:8384/
[CU3KR] 14:49:21 INFO: Completed initial scan (rw) of folder STCloud
[CU3KR] 14:49:23 INFO: Established secure connection to CV32T6W-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ at 192.168.0.4:55962-195.154.XX.YYY:22067 (relay-dial)
[CU3KR] 14:49:23 INFO: Device CV32T6W-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ client is "syncthing v0.12.19" named "Amilo-Si1520"
[CU3KR] 14:49:29 INFO: New UPnP port mapping: external port 26208 to local port 22000.
[CU3KR] 14:49:38 INFO: Established secure connection to HHWREMG-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ at 192.168.0.4:59034-188.226.XXX.YY:22067 (relay-dial)
[CU3KR] 14:49:38 INFO: Connection to HHWREMG-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ closed: EOF
[CU3KR] 14:49:43 INFO: Connection to CV32T6W-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ closed: switching connections
[CU3KR] 14:49:44 INFO: Connection to CV32T6W-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ closed: EOF
[CU3KR] 14:49:46 INFO: Established secure connection to CV32T6W-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ at 192.168.0.4:22000-151.64.XX.YY:55954 (direct-accept)
[CU3KR] 14:49:46 INFO: Connection to CV32T6W-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ closed: EOF
[CU3KR] 14:49:46 INFO: Device CV32T6W-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ-TUVWXYZ client is "syncthing v0.12.19" named "Amilo-Si1520"

(I edited the machine IDs and IPs out)

The “unreachable” machine is the one starting with HHWREMG (RasPi Home)

Any suggestions?

So it’s initially connected via relay and then switches to a direct connection, which somehow fails. I suspect there is something wrong with your router/pi on the other end.

Try disabling relaying in advanced config on both sides and see if that helps.

I’ll try that and report back.

I’ve also tried using the fixed ip of the raspi to connect to it instead of the “dynamic” option, but the result is the same.

What I don’t understand is, if the problem is the Pi why does my other office machine see the Pi correctly? :confused:

[EDIT: it seems that disabling relaying on the office side the office machine and the pi don’t see each other. The other office machine still works correctly. I will try disabling relaying on the pi too, as soon as I get home, and see what happens.]

I think there was a similar case on the forums already. It’s best if you setup a static port mapping on the router at home and disable upnp.

I am fairly sure that I have already done that, but I will double check as soon as I get home.

Ok, the problem was that the home pi suddenly “forgot” the office device, therefore it wouldn’t allow it to connect to it.

I have no idea what might have caused this behaviour, but once I added the office machine to the home pi, it all started to work again.

Is there any way I can try to find out how the office device vanished from the device list of the pi?

Thanks

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.