WAN connections not working

Support
1

I checked all the comments in the forum I have found and none helped me.

I have 3 linux boxes (homeserver, workserver, laptop). My computer connects correctly to my workserver, but not to my homeserver.

Both boxes have UFW disabled, and my home router has port 22000 forwarded to my homeserver 22000 (TCP&UDP).

When I check my homeserver discovery returns 3/5 and the error is one error is:

global@https://discovery-v4.syncthing.net/v2/: Post "https://discovery-v4.syncthing.net/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

(There is a IPv6 error, but I ignore IPv6 errors because my internet provider don’t use it)

When I connect using a browser from homeserver to this url it returns Not found (404)

Any hint of what to check?

Thanks

2

Your work server is probably firwwalled off or requires connecting via a proxy. Best that you talk to whoever maintains your work network.

3

I didn’t explain correctly… my workserver is working; my homeserver isn’t.

I have made both installations, following https://gist.github.com/pjobson/c833bfc3b2f7f53db23486f94be9ab6f; both are ubuntu, work 16.04, home 18.04

4

Right, the problem is no different.

For things to be able to connect, you need:

Firewall to permit traffic as per docs

And either of:

  1. Device not to be behind a NAT
  2. If device is behind a NAT you need either of:
  • Port forwarding/DMZ setup on the NAT
  • UPnP support on the NAT
  • Relaying enabled
5
  • My home router have port 22000 directed to homserverip:22000
  • HomeRouter doesn’t have firewall
  • UFW is disabled in homeserver
  • relaying is enabled (all options on connection page are checked)
6

You can enable connection logging facility to see what addresses its connecting to and why its failing.

Also, check the UI to make sure discovery and listener status is ok.

7
  • 2020-08-13 14:17:52 quic://0.0.0.0:22000 detected NAT type: Full cone NAT
  • 2020-08-13 14:17:52 quic://0.0.0.0:22000 resolved external address quic://?¿?.?¿?.?¿?.?¿?:22000 (via stun.syncthing.net:3478)
  • 2020-08-13 14:17:57 New NAT port mapping: external TCP address ?¿?.?¿?.?¿?.?¿?:11011 to local address 0.0.0.0:22000.
  • 2020-08-13 14:17:57 New NAT port mapping: external TCP address 0.0.0.0:29490 to local address 0.0.0.0:22000.
  • 2020-08-13 14:17:57 Detected 2 NAT services
  • 2020-08-13 14:18:24 Joined relay relay://185.173.235.112:22067
8

I mean debug logging, not general logs, on the connecting side.

Also screenshot from both sides would help.

9

I think I activated the correct logs:

  • 2020-08-13 15:23:59 globalClient.Lookup https://discovery.syncthing.net/v2/?device=XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-FSIQWAJ 404 Not Found
  • 2020-08-13 15:23:59 negative cache entry for XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-FSIQWAJ at global@https://discovery-v4.syncthing.net/v2/ valid until 2020-08-13 15:22:00.998152214 +0200 CEST m=+92.229322741 or 2020-08-13 16:21:00.998153279 +0200 CEST m=+3632.229323774
  • 2020-08-13 15:23:59 negative cache entry for XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-FSIQWAJ at global@https://discovery-v6.syncthing.net/v2/ valid until 2020-08-13 15:22:00.99815681 +0200 CEST m=+92.229327325 or 2020-08-13 16:21:00.998157282 +0200 CEST m=+3632.229327776
  • 2020-08-13 15:23:59 lookup for XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-FSIQWAJ at IPv4 local
  • 2020-08-13 15:23:59 addresses: []
  • 2020-08-13 15:23:59 lookup for XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-FSIQWAJ at IPv6 local
  • 2020-08-13 15:23:59 addresses: []
  • 2020-08-13 15:23:59 lookup results for XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-FSIQWAJ
  • 2020-08-13 15:23:59 addresses: []
  • 2020-08-13 15:23:59 Reconnect loop for XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-FSIQWAJ []
  • 2020-08-13 15:23:59 sleep until next dial 1m0s
10

The other node has not advertised any addresses, so either its failing to talk to it, or global discovery is disabled.

Best bet is to probably post screenshots from both sides.

11

Well, I posted just “the isolated” server:

  • workserver <— ok —> client
  • homeserver <— fail —> client So I thought the problem should be homeserver. client homeserver

The missing discovery in client is IPv6, and in server is IPv6 and IPv4

12

When you say missing, you mean ipv4 discovery failed on one of them? You should address the reason for failure.

13

I couldn’t find the error in logs, I will check again tomorrow

14

It should be visible as you hover over the 3/5 text.

15

The error is in the first message

global@https://discovery-v4.syncthing.net/v2/: Post "https://discovery-v4.syncthing.net/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
16

Right, something (firewall, corporate proxy, idk) is preventing it from talking to discovery server.

17

I use dynamic dns from Afraid, so I configured my laptop to connect the server as server:22000 (not dynamic) and now it connects. It is a work around, but I don’t know what limit it.

18

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