0.9.16 /cry **new problem**

Support
1

I looked at Syncthing back in April this year, but didn’t really use it. Yesterday I thought it was time to take another look. I updated my binaries to 0.9.15 and started syncing two nodes 1) Windows Vista x64 and 2) Linux Mint 15 x64.

The shares I had took right off. I had no trouble reconnecting (Linux box is a laptop and goes to sleep regularly) and syncing several files/directories.

Okay, now the trouble. This afternoon I see there is an update to 0.9.16, so I update my binaries and ut’oh. The Windows box seems happy, but the Linux box says this:

username@asus ~/sync/program $ ./syncthing [monitor] 15:17:19 INFO: Starting syncthing [IQRSQ] 15:17:20 INFO: syncthing v0.9.16 (go1.3.1 linux-amd64 default) jenkins@build.syncthing.net 2014-09-17 15:11:53 UTC [IQRSQ] 15:17:20 INFO: My ID: xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx [IQRSQ] 15:17:20 INFO: Starting web GUI on https://127.0.0.1:8080/ [IQRSQ] 15:17:21 INFO: Performing initial repository scan [IQRSQ] 15:17:21 INFO: Starting local discovery announcements [IQRSQ] 15:17:21 INFO: Starting global discovery announcements [IQRSQ] 15:17:21 OK: Ready to synchronize test (read-write) [IQRSQ] 15:17:21 OK: Ready to synchronize torrents (read-write) [IQRSQ] 15:17:21 INFO: Node xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx is “asus” at [dynamic] [IQRSQ] 15:17:21 INFO: Node yyyyyy-yyyyyy-yyyyyy-yyyyyy-yyyyyy-yyyyyy-yyyyyy-yyyyyy is “pc2010” at [dynamic] 2014/09/17 15:17:21 http: TLS handshake error from 127.0.0.1:33949: remote error: handshake failure 2014/09/17 15:17:21 http: TLS handshake error from 127.0.0.1:33950: remote error: handshake failure 2014/09/17 15:17:22 http: TLS handshake error from 127.0.0.1:33951: remote error: handshake failure 2014/09/17 15:17:22 http: TLS handshake error from 127.0.0.1:33952: remote error: handshake failure 2014/09/17 15:17:23 http: TLS handshake error from 127.0.0.1:33953: remote error: handshake failure 2014/09/17 15:17:23 http: TLS handshake error from 127.0.0.1:33954: remote error: handshake failure 2014/09/17 15:17:24 http: TLS handshake error from 127.0.0.1:33955: remote error: handshake failure 2014/09/17 15:17:24 http: TLS handshake error from 127.0.0.1:33956: remote error: handshake failure ^C[monitor] 15:17:25 INFO: Signal 2 received; exiting

The handshake errors go on forever, but I stopped and restarted a few times. I only let it run a few seconds this last time so my post wouldn’t be annoying.

I will try and provide any additional information I am asked for if needed. Thank-you.

2

Update. I started the client again after an hour and now it is happy. The “TLS handshake” messages stopped spewing.

3

It happened again. I didn’t think to just let it run to see how long it would last. Sorry about that. It’s running fine again now, but if it happens again I’ll leave it be to see if it can just fix itself and how long it takes. If you need/want any additional information from me, please let me know.

4

Might be https://github.com/syncthing/syncthing/issues/700

5

Thank you for the feedback. I read through that thread and my symptoms are different.

I’m going to upgrade my binaries to 0.9.17 now and I’ll see if the situation continues.

6

Update: When I upgraded the binaries on both machines to 0.9.17 (from 0.9.16) they both connected to the Global Discovery Server without problem, but they wouldn’t connect to each other. I waited about a half hour and then shut both of them down & waited another 15 minutes (in case there was some networking port open contention). Then I started the binaries on both platforms. They still would not talk. I left them and went and did other things. Upon checking back in on them they are talking, but the same TLS handshake issue is back. Let me be clear. They are working and syncing. The Linux one isjust spewing these handshake errors as well.

7

I think I have it!!

I need to confirm this, but I believe it is my FF (Firefox) configuration. In about:config, I keep the setting “security.ssl.require_safe_negotiation” as true. The default is false.

The FF setting is related to this TLS bug.

So, do I need to file a bug or enhancement request to address this?