Discovery Failures: connection refused for v4 and v6

Hi, I am facing an issue with Global Discovery on one of the computers I setup Syncthing on. I have 3 devices on a Home 1 network: Android Phone, Windows Laptop, Linux Headless PC. 1 device on Home 2 which is directly connected to internet.

Now, All except for Arch Linux:

1. Devices are able to connect with each other out of the box (local and global)
2. Each of the device has “Listeners 3/3” and “Discovery 4/5”
3. For Global Discovery ipv6 is failing because my ISP does not support it.

Now, Arch Linux:

1. Device is able to connect with each other out of the box for LOCAL but NOT for GLOBAL
2. The device has “Listeners 2/3” and “Discovery 3/5”
3. For Global Discovery ipv6 is failing because my ISP does not support it.

For “Listeners 2/3” the error is:

dynamic+https://relays.syncthing.net/endpoint: Get "https://relays.syncthing.net/endpoint": dial tcp: lookup relays.syncthing.net on [::1]:53: read udp [::1]:36305->[::1]:53: read: connection refused

For “Discovery 3/5” the error is:

• global@https://discovery-v4.syncthing.net/v2/: Post "https://discovery-v4.syncthing.net/v2/": dial tcp: lookup discovery-v4.syncthing.net on [::1]:53: read udp [::1]:36772->[::1]:53: read: connection refused
• global@https://discovery-v6.syncthing.net/v2/: Post "https://discovery-v6.syncthing.net/v2/": dial tcp: lookup discovery-v6.syncthing.net on [::1]:53: read udp [::1]:44185->[::1]:53: read: connection refused

for Home 1 this is port forwarding:

When I SSH to Arch Linux and run:

resolvectl query discovery-v4.syncthing.net
discovery-v4.syncthing.net: 198.211.120.59     -- link: enp1s0
                            139.59.84.212      -- link: enp1s0

-- Information acquired via protocol DNS in 1.3ms.
-- Data is authenticated: no

resolvectl query discovery-v6.syncthing.net
discovery-v6.syncthing.net: 2a03:b0c0:0:1010::bb:4001 -- link: enp1s0
                            2400:6180:100:d0::741:a001 -- link: enp1s0

-- Information acquired via protocol DNS in 1.6ms.
-- Data is authenticated: no

I can confirm DNS is working correctly. All devices are running version v1.8.0

At this point I am stuck and don’t really know how to troubleshoot the issue. Any help?

Thanks

7 posts - 4 participants

Read full topic