Syncthing doesnt connect to relays.

Support
1

i have issue with syncthing on my FileServer with runnig on ubuntu. the main issue is that im unable to sync files out side my LAN, which i believe the reason for that is because my file server for some reason unable to connect to relay server.

in all other syncthing devices on my network im able to connect to relay server. so im not so sure the issue its on my network

Thanks.

2

One reason could be that the file server doesn’t have the CA certificates installed to verify the HTTPS connection. Does curl https://relays.syncthing.net/ work on that box or return an error?

Another thing to check is to set the environment variable STTRACE=relays before starting Syncthing, and it should tell you what’s going on when trying to connect to relays.

3

it return error

curl  https://relays.syncthing.net/
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

and STTRACE=relays return

orangepi@OrangePI:~$ syncthing  STTRACE=relays
[monitor] 11:04:33 INFO: Starting syncthing
[YEECK] 11:04:33 INFO: syncthing v0.12.20 "Beryllium Bedbug" (go1.6 linux-arm) u     nknown-user@lxslave.syncthing.net 2016-03-06 10:59:03 UTC
[YEECK] 11:04:33 INFO: My ID:YEECKW4-QYUEZ5P-KK4GPMV-EE4DMJV-TJBRXP5     KO6IK-NIJ7PQA
[YEECK] 11:04:33 INFO: Single thread hash performance is ~11 MB/s
[YEECK] 11:04:34 OK: Ready to synchronize בניין  (read-write)
[YEECK] 11:04:34 OK: Ready to synchronize testss (read-write)
[YEECK] 11:04:34 OK: Ready to synchronize בניין   (read-write)
[YEECK] 11:04:34 OK: Ready to synchronize בניין 2 (read-write)
[YEECK] 11:04:34 INFO: Using discovery server https://discovery-v4-1.syncthing.n     et/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA
[YEECK] 11:04:34 INFO: Using discovery server https://discovery-v4-2.syncthing.n     et/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC
[YEECK] 11:04:34 INFO: Using discovery server https://discovery-v4-3.syncthing.n     et/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ
[YEECK] 11:04:34 INFO: Completed initial scan (rw) of folder testss
[YEECK] 11:04:34 INFO: Using discovery server https://discovery-v6-1.syncthing.n     et/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA
[YEECK] 11:04:34 INFO: Using discovery server https://discovery-v6-2.syncthing.n     et/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC
[YEECK] 11:04:34 INFO: Using discovery server https://discovery-v6-3.syncthing.n     et/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ
[YEECK] 11:04:34 INFO: Completed initial scan (rw) of folder בניין 
[YEECK] 11:04:34 INFO: Completed initial scan (rw) of folder בניין 
[YEECK] 11:04:34 INFO: Completed initial scan (rw) of folder בניין
[YEECK] 11:04:34 INFO: Device KL4CG47-OHWDGMX-E46NLKJ-EACN63S-WCALTQZKL4CG47-OHWDGMX-E46NLKJ-EACN63S-WCALTQZ     XJZIG-OD22OAR is "bo" at [dynamic]
[YEECK] 11:04:34 INFO: DeviceYEECKW4-QYUEZ5P-KK4GPMV-EE4DMJV-TJBRXP5     KO6IK-NIJ7PQA is "FileServer" at [dynamic]
[YEECK] 11:04:34 INFO: Device 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL    3V2HM-MULZMA6 is "da" at [dynamic]
[YEECK] 11:04:34 INFO: Device 64FYEHZ-VIZ6HJN-X4O6H5C-CQ2DDQ7-EQ75LXS    6DQLM-ASW2EAS is "lg g3" at [dynamic]
[YEECK] 11:04:34 INFO: Starting usage reporting
[YEECK] 11:04:34 INFO: API listening on [::]:8384
[YEECK] 11:04:34 INFO: GUI URL is https://127.0.0.1:8384/
[YEECK] 11:04:41 INFO: Established secure connection to 6IJJ5FR-VSLV4HX-NT2B52T-     TDC2RJX-KAOCIFL-SOKV5S6-A23V2HM-MULZMA6 at 192.168.88.19:35368-176.9.54.201:2206     7 (relay-dial)
[YEECK] 11:04:41 INFO: Device 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL    3V2HM-MULZMA6 client is "syncthing v0.12.20" named "מחשב"
[YEECK] 11:04:44 INFO: No UPnP device detected
[YEECK] 11:04:45 INFO: Connection to 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL-SOK     V5S6-A23V2HM-MULZMA6 closed: switching connections
[YEECK] 11:04:45 INFO: Connection to 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL-SOK     V5S6-A23V2HM-MULZMA6 closed: switching connections
[YEECK] 11:04:45 INFO: Connection to 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL-SOK     V5S6-A23V2HM-MULZMA6 closed: read tcp 192.168.88.19:35368->176.9.54.201:22067: u     se of closed network connection
[YEECK] 11:04:45 INFO: Established secure connection to 6IJJ5FR-VSLV4HX-NT2B52T-     TDC2RJX-KAOCIFL-SOKV5S6-A23V2HM-MULZMA6 at 192.168.88.19:45404-192.168.88.20:220     00 (direct-dial)
[YEECK] 11:04:45 INFO: Connection to 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL-SOK     V5S6-A23V2HM-MULZMA6 closed: read tcp 192.168.88.19:45404->192.168.88.20:22000:      use of closed network connection
[YEECK] 11:04:45 INFO: Device 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL    3V2HM-MULZMA6 client is "syncthing v0.12.20" named "מחשב"
[YEECK] 11:04:49 INFO: Established secure connection to 6IJJ5FR-VSLV4HX-NT2B52T-     TDC2RJX-KAOCIFL-SOKV5S6-A23V2HM-MULZMA6 at 192.168.88.19:45405-192.168.88.20:220     00 (direct-dial)
[YEECK] 11:04:49 INFO: Device 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL    3V2HM-MULZMA6 client is "syncthing v0.12.20" named "מחשב"
^C[monitor] 11:05:13 INFO: Signal 2 received; exiting
[YEECK] 11:05:13 OK: Exiting
orangepi@OrangePI:~$ syncthing STTRACE=relays
[monitor] 11:05:17 INFO: Starting syncthing
[YEECK] 11:05:17 INFO: syncthing v0.12.20 "Beryllium Bedbug" (go1.6 linux-arm) u     nknown-user@lxslave.syncthing.net 2016-03-06 10:59:03 UTC
[YEECK] 11:05:17 INFO: My ID:YEECKW4-QYUEZ5P-KK4GPMV-EE4DMJV-TJBRXP5     KO6IK-NIJ7PQA
[YEECK] 11:05:18 INFO: Single thread hash performance is ~11 MB/s
[YEECK] 11:05:18 OK: Ready to synchronize בניין (read-write)
[YEECK] 11:05:18 OK: Ready to synchronize בניין  (read-write)
[YEECK] 11:05:18 OK: Ready to synchronize testss (read-write)
[YEECK] 11:05:18 OK: Ready to synchronize בניין  (read-write)
[YEECK] 11:05:18 INFO: Using discovery server https://discovery-v4-1.syncthing.n     et/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA
[YEECK] 11:05:18 INFO: Using discovery server https://discovery-v4-2.syncthing.n     et/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC
[YEECK] 11:05:18 INFO: Using discovery server https://discovery-v4-3.syncthing.n     et/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ
[YEECK] 11:05:18 INFO: Using discovery server https://discovery-v6-1.syncthing.n     et/?id=SR7AARM-TCBUZ5O-VFAXY4D-CECGSDE-3Q6IZ4G-XG7AH75-OBIXJQV-QJ6NLQA
[YEECK] 11:05:18 INFO: Using discovery server https://discovery-v6-2.syncthing.n     et/?id=DVU36WY-H3LVZHW-E6LLFRE-YAFN5EL-HILWRYP-OC2M47J-Z4PE62Y-ADIBDQC
[YEECK] 11:05:18 INFO: Using discovery server https://discovery-v6-3.syncthing.n     et/?id=VK6HNJ3-VVMM66S-HRVWSCR-IXEHL2H-U4AQ4MW-UCPQBWX-J2L2UBK-NVZRDQZ
[YEECK] 11:05:18 INFO: Completed initial scan (rw) of folder testss
[YEECK] 11:05:18 INFO: Completed initial scan (rw) of folder בניין 
[YEECK] 11:05:18 INFO: Completed initial scan (rw) of folder בניין
[YEECK] 11:05:18 INFO: Completed initial scan (rw) of folder בניין
[YEECK] 11:05:18 INFO: Device KL4CG47-OHWDGMX-E46NLKJ-EACN63S-WCALTQZ     XJZIG-OD22OAR is "bo" at [dynamic]
[YEECK] 11:05:18 INFO: DeviceYEECKW4-QYUEZ5P-KK4GPMV-EE4DMJV-TJBRXP5     KO6IK-NIJ7PQA is "FileServer" at [dynamic]
[YEECK] 11:05:18 INFO: Device 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL    3V2HM-MULZMA6 is "da" at [dynamic]
[YEECK] 11:05:18 INFO: Device 64FYEHZ-VIZ6HJN-X4O6H5C-CQ2DDQ7-EQ75LXS    6DQLM-ASW2EAS is "lg g3" at [dynamic]
[YEECK] 11:05:18 INFO: Starting usage reporting
[YEECK] 11:05:18 INFO: API listening on [::]:8384
[YEECK] 11:05:18 INFO: GUI URL is https://127.0.0.1:8384/
[YEECK] 11:05:22 INFO: Established secure connection to 6IJJ5FR-VSLV4HX-NT2B52T-     TDC2RJX-KAOCIFL-SOKV5S6-A23V2HM-MULZMA6 at 192.168.88.19:35386-176.9.54.201:2206     7 (relay-dial)
[YEECK] 11:05:22 INFO: Device 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL    3V2HM-MULZMA6 client is "syncthing v0.12.20" named "מחשב"
[YEECK] 11:05:28 INFO: No UPnP device detected
[YEECK] 11:05:45 INFO: Connection to 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL-SOK     V5S6-A23V2HM-MULZMA6 closed: switching connections
[YEECK] 11:05:45 INFO: Established secure connection to 6IJJ5FR-VSLV4HX-NT2B52T-     TDC2RJX-KAOCIFL-SOKV5S6-A23V2HM-MULZMA6 at 192.168.88.19:22000-192.168.88.20:131     19 (direct-accept)
[YEECK] 11:05:45 INFO: Connection to 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL-SOK     V5S6-A23V2HM-MULZMA6 closed: read tcp 192.168.88.19:35386->176.9.54.201:22067: u     se of closed network connection
[YEECK] 11:05:45 INFO: Connection to 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL-SOK     V5S6-A23V2HM-MULZMA6 closed: read tcp 192.168.88.19:22000->192.168.88.20:13119:      use of closed network connection
[YEECK] 11:05:57 INFO: Established secure connection to 6IJJ5FR-VSLV4HX-NT2B52T-     TDC2RJX-KAOCIFL-SOKV5S6-A23V2HM-MULZMA6 at 192.168.88.19:45428-192.168.88.20:220     00 (direct-dial)
[YEECK] 11:05:57 INFO: Device 6IJJ5FR-VSLV4HX-NT2B52T-TDC2RJX-KAOCIFL    3V2HM-MULZMA6 client is "syncthing v0.12.20" named "מחשב"
[YEECK] 11:35:19 INFO: Usage report: Post https://data.syncthing.net/newdata: x509: certificate signed by unknown authority
4

You need to upgrade your CA certificates, they must be ancient.

5

I have the same problem

curl https://relays.syncthing.net/
curl: (35) Unknown SSL protocol error in connection to relays.syncthing.net:443

and in syncthing I get lots of errors like this

[JQH46] 2016/03/20 22:11:32.445640 relay.go:47: DEBUG: Service: Failed service 'DynamicClient:0xc82191e420:dynamic+https://relays.syncthing.net/endpoint@dynamic+https://relays.syncthing.net/endpoint' (4.884901 failures of 5.000000), restarting: true, error: "DynamicClient:0xc82191e420:dynamic+https://relays.syncthing.net/endpoint@dynamic+https://relays.syncthing.net/endpoint returned unexpectedly", stacktrace: [unknown stack trace]
[JQH46] 2016/03/20 22:11:32.445668 dynamic.go:59: DEBUG: DynamicClient:0xc82191e420:dynamic+https://relays.syncthing.net/endpoint@dynamic+https://relays.syncthing.net/endpoint looking up dynamic relays
[JQH46] 2016/03/20 22:11:42.605767 dynamic.go:63: DEBUG: DynamicClient:0xc82191e420:dynamic+https://relays.syncthing.net/endpoint@dynamic+https://relays.syncthing.net/endpoint failed to lookup dynamic relays Get https://relays.syncthing.net/endpoint: net/http: TLS handshake timeout

what could I do to solve this as I have no any clue?

6

Maybe you could try the same steps that were suggested to the previous person…?

7

In your case it looks like a firewall?

8

I’ll investigate that more, as other devices on this network also can’t connect to https://relays.syncthing.net/

9

So i managed to fix this issue i had. i didn’t had ca certs in my machine so i found this artical

it i follow the instruction

i had issue with the firewall so i opened TCP port for 22000 to my machine and its worked.

but the question is: isn’t relay show make the first connection to over come the NAT blocking? i mean skype like operation ?

10

That depends, did you open it o out going or incoming? Are you talking about your router’s firewall or your machine’s?

11

income to my router firewall

12

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