How to avoid joining an inaccessible relay

In Shanghai, a relay 125.36.77.84 would be selected

[CCKOM] 2023/09/06 10:13:25 INFO: Joined relay relay://121.229.97.36:22067

However, this relay is not accessible from anywhere in China (red for timeout), see 多个地点ping[125.36.77.84]服务器,网站测速,站长工具.

As a result, Syncthing relays can not help with connecting WAN nodes, is this expected?

I don’t think there’s any reasonable way to guarantee end-to-end connectivity. Your best bet might be a VPN.

1 Like

Oh that is sad, but what I seek is whether Syncthing could turn to other accessible instead, since it is stuck on retrying connections to this relay forever, without attempting other relays.

That should happen, because the other side should register with a relay and publish that address.

1 Like

If the problem persists, I agree with bt90, you can always use a free mesh style network app that creates a virtual private LAN over the Internet. Then, the sync becomes a direct ip peer to peer sync.

I use this method on my cell phone to remotely sync with my PC at home.

Fairly off-topic but since it’s been mentioned twice now;

We seem to be talking in the context of China here. Pointing towards VPN-solutions may be a bit tricky and should only be considered while exercising a decent level of caution.

1 Like

You could also configure a relay on both sides that is reachable.

Yes. Always be careful.

The solution I use provides an encrypted tunnel only it’s not a conventional VPN product that masks your primary IP address. It merely gives you an additional private IP address just for Syncthing. Regular traffic is unaffected and unencrypted as normal.

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