Connection Reset / WRN Failed TLS handshake

Support
1

I am having problems with my laptop (Win 10) and phone (Android) connecting to my home server (TrueNAS) while outside the local network. The devices will connect once in a while, become disconnected for long periods, then reconnect briefly again and the cycle continues. I have tried both public wifi (Starbucks) and mobile data on phone.

Laptop log (public wifi):

2025-08-20 12:04:13 INF Established secure connection (device=VO6T5H6 connection.local=172.16.224.210:22000 connection.remote=142.113.192.193:22000 connection.type=tcp-server connection.lan=false connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=30 connection.id=62TGKM044E5JM2TQPJD4CKSPTG log.pkg=connections) 2025-08-20 12:04:13 INF New device connection (device=VO6T5H6 address=142.113.192.193:22000 remote.name=TrueNAS remote.client=syncthing remote.version=v1.30.0 log.pkg=model) 2025-08-20 12:05:44 INF Lost device connection (kind=primary device=VO6T5H6 connection=172.16.224.210:22000-142.113.192.193:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGKM044E5JM2TQPJD4CKSPTG error=“reading length: read tcp 172.16.224.210:22000->142.113.192.193:22000: wsarecv: An existing connection was forcibly closed by the remote host.” remaining=0 log.pkg=model) 2025-08-20 12:05:44 INF Connection closed (device=VO6T5H6 connection=172.16.224.210:22000-142.113.192.193:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGKM044E5JM2TQPJD4CKSPTG error=“reading length: read tcp 172.16.224.210:22000->142.113.192.193:22000: wsarecv: An existing connection was forcibly closed by the remote host.” log.pkg=model) 2025-08-20 12:06:31 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:22000 error=“Application error 0x0 (remote): closing” log.pkg=connections) 2025-08-20 12:06:45 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:57944 error=EOF log.pkg=connections) 2025-08-20 12:06:51 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:22000 error=“Application error 0x0 (remote): closing” log.pkg=connections) 2025-08-20 12:07:36 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:22000 error=“Application error 0x0 (remote): closing” log.pkg=connections) 2025-08-20 12:07:45 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:57944 error=“write tcp 172.16.224.210:22000->142.113.192.193:57944: wsasend: An existing connection was forcibly closed by the remote host.” log.pkg=connections) 2025-08-20 12:08:46 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:57944 error=“write tcp 172.16.224.210:22000->142.113.192.193:57944: wsasend: An existing connection was forcibly closed by the remote host.” log.pkg=connections) 2025-08-20 12:09:06 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:22000 error=“Application error 0x0 (remote): closing” log.pkg=connections) 2025-08-20 12:09:26 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:22000 error=“Application error 0x0 (remote): closing” log.pkg=connections) 2025-08-20 12:09:46 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:57944 error=“write tcp 172.16.224.210:22000->142.113.192.193:57944: wsasend: An existing connection was forcibly closed by the remote host.” log.pkg=connections) 2025-08-20 12:10:41 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:22000 error=“Application error 0x0 (remote): closing” log.pkg=connections) 2025-08-20 12:10:47 WRN Failed to exchange Hello messages (device=VO6T5H6 address=142.113.192.193:57944 error=“write tcp 172.16.224.210:22000->142.113.192.193:57944: wsasend: An existing connection was forcibly closed by the remote host.” log.pkg=connections) 2025-08-20 12:12:21 WRN Failed TLS handshake (address=142.113.192.193:22000 error=“read tcp 172.16.224.210:22000->142.113.192.193:22000: wsarecv: An existing connection was forcibly closed by the remote host.” log.pkg=connections) 2025-08-20 12:13:27 INF Established secure connection (device=VO6T5H6 connection.local=“[::]:22000” connection.remote=142.113.192.193:22000 connection.type=quic-client connection.lan=false connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=40 connection.id=62TGMMDFIF3K4O492L5V9RP63S log.pkg=connections) 2025-08-20 12:13:27 INF New device connection (device=VO6T5H6 address=142.113.192.193:22000 remote.name=TrueNAS remote.client=syncthing remote.version=v1.30.0 log.pkg=model) 2025-08-20 12:13:50 WRN Failed TLS handshake (address=142.113.192.193:22000 error=“read tcp 172.16.224.210:22000->142.113.192.193:22000: wsarecv: An existing connection was forcibly closed by the remote host.” log.pkg=connections) 2025-08-20 12:13:52 INF Established secure connection (device=VO6T5H6 connection.local=172.16.224.210:22000 connection.remote=142.113.192.193:57944 connection.type=tcp-client connection.lan=false connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=30 connection.id=62TGMPB6QGB3EMV97O9E52C470 log.pkg=connections) 2025-08-20 12:13:52 INF Additional device connection (device=VO6T5H6 address=142.113.192.193:57944 count=1 log.pkg=model) 2025-08-20 12:13:52 INF Lost device connection (kind=primary device=VO6T5H6 connection=“[::]:22000-142.113.192.193:22000/quic-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P40-62TGMMDFIF3K4O492L5V9RP63S” error=“replacing connection” remaining=1 log.pkg=model)

Phone log (public wifi):

2025-08-20 12:10:36 Device VO6T5H6 client is “syncthing v1.30.0” named “TrueNAS” at 172.16.227.158:57266-45.86.153.95:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-62TGM2F9QHA1EPO9I0T72KQFFG 2025-08-20 12:14:17 Established secure connection to VO6T5H6 at 172.16.227.158:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGMS8UFSG0EORCCPQH9EQD78 2025-08-20 12:14:17 Additional connection (+1) for device VO6T5H6 at 172.16.227.158:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGMS8UFSG0EORCCPQH9EQD78 2025-08-20 12:14:17 Lost primary connection to VO6T5H6 at 172.16.227.158:57266-45.86.153.95:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-62TGM2F9QHA1EPO9I0T72KQFFG: replacing connection (1 remain) 2025-08-20 12:16:34 Lost primary connection to VO6T5H6 at 172.16.227.158:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGMS8UFSG0EORCCPQH9EQD78: reading length: read tcp 172.16.227.158:22000->142.113.192.193:57944: read: connection reset by peer (0 remain) 2025-08-20 12:16:34 Connection to VO6T5H6 at 172.16.227.158:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGMS8UFSG0EORCCPQH9EQD78 closed: reading length: read tcp 172.16.227.158:22000->142.113.192.193:57944: read: connection reset by peer

Phone log (data servic):

2025-08-20 12:21:32 Joined relay relay://194.104.156.154:22067 2025-08-20 12:21:51 Established secure connection to VO6T5H6 at 10.104.171.153:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGOH488SDVI143LJCB4GH9HC 2025-08-20 12:21:51 Device VO6T5H6 client is “syncthing v1.30.0” named “TrueNAS” at 10.104.171.153:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGOH488SDVI143LJCB4GH9HC 2025-08-20 12:23:38 Lost primary connection to VO6T5H6 at 10.104.171.153:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGOH488SDVI143LJCB4GH9HC: reading length: read tcp 10.104.171.153:22000->142.113.192.193:57944: read: connection reset by peer (0 remain) 2025-08-20 12:23:38 Connection to VO6T5H6 at 10.104.171.153:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-62TGOH488SDVI143LJCB4GH9HC closed: reading length: read tcp 10.104.171.153:22000->142.113.192.193:57944: read: connection reset by peer 2025-08-20 12:24:25 Failed to exchange Hello messages with VO6T5H6-HSEYYT5-P2YQ5BG-F2J4TQV-LEAYGLE-L5KY7RN-RMHIF5S-4RIZSQG at 10.104.171.153:22000-142.113.192.193:57944/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30-31EOCHHLJ808GD5ENQOOAH3TVK: EOF

I have changed routers, internet provider, upgraded TrueNAS and Syncthing across devices over the last several months, but I don’t recall when this started to happen after which network change. I’m rarely outside my network so I can’t pinpoint exactly when this issue happens as a result of what change.

2

What Syncthing and Android version are your devices running?

Also, have you confirmed that you have paired your devices properly? That looks like (from the logs) and sounds like (from what you’re describing about briefly connecting) a paused or unpaired device.

3

v2.0.1, Windows (64-bit Intel/AMD) and v1.27.3 (Android 15).

What do you mean by pairing devices properly?

Listeners are (3/5):

The following methods are used to discover other devices on the network and announce this device to be found by others:

Some discovery methods could not be established for finding other devices or announcing this device:

Discovery cycle between 4/5:

The following methods are used to discover other devices on the network and announce this device to be found by others:

Some discovery methods could not be established for finding other devices or announcing this device:

and 3/5:

The following methods are used to discover other devices on the network and announce this device to be found by others:

Some discovery methods could not be established for finding other devices or announcing this device:

The files do sync when the connection is made. But most of the time it remains disconnected:

image

4

Try updating to 2.0.2. It contains this fix, which is potentially relevant to this issue.

1 Like
5

Is there any reason for running a 1-year-old version of the Android app? You will need to switch to https://github.com/Catfriend1/syncthing-android if you want to continue receiving updates on Android, however even if you were willing to stick to the discontinued official app for the time being, the last version of that was v1.28.1.

1 Like
6

I have updated to the latest v2.02 on both Windows and Android (fork v2.0.2.1)

TrueNAS 25.04.1 and Syncthing App Version: v1.30.0, Version: v1.2.5 (latest)

Same issue persists on both Android and Laptop. Everything connects up fine when I Tailscale into my home server network. However, Tailscale on my server also appears to have uptime issues, so thinking this maybe related. I am starting to think this has something to do with my router, internet connectivity, or the server hardware itself?

7

Did you change any options related to discovery or relaying on any of the devices?

8

I have not changed any options. Discovery and relaying are checked.

Since upgrading to v2.02 on laptop, I am seeing “Detected a flip-flopping listener” pop up constantly on the server side.

10

This is the log on server side:

2025-08-20 16:48:53 Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down 2025-08-20 16:48:53 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get “https://relays.syncthing.net/endpoint”: dial tcp: lookup relays.syncthing.net on 192.168.2.1:53: read udp 192.168.2.201:53995->192.168.2.1:53: i/o timeout 2025-08-20 16:48:53 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting 2025-08-20 16:49:03 Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down 2025-08-20 16:49:03 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get “https://relays.syncthing.net/endpoint”: dial tcp: lookup relays.syncthing.net on 192.168.2.1:53: read udp 192.168.2.201:37972->192.168.2.1:53: i/o timeout 2025-08-20 16:49:03 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting 2025-08-20 16:49:03 Detected 0 NAT services 2025-08-20 16:49:13 Relay listener (dynamic+https://relays.syncthing.net/endpoint) shutting down 2025-08-20 16:49:13 listenerSupervisor@dynamic+https://relays.syncthing.net/endpoint: service dynamic+https://relays.syncthing.net/endpoint failed: Get “https://relays.syncthing.net/endpoint”: dial tcp: lookup relays.syncthing.net on 192.168.2.1:53: read udp 192.168.2.201:36316->192.168.2.1:53: i/o timeout

11

DNS lookup for relays.syncthing.net using the server 192.168.2.1 is timing out.

3 Likes
12

Thanks. Looks like I am having connectivity issues on TrueNAS that I am now troubleshooting on their forums. Lots of dropped packets ever since I updated from Core to Scale.

13

I found that my router decided to automatically assign my Echo device with the static IP set for my TrueNAS. This is why I was having DNS and dropped packets on TrueNAS.

1 Like
14

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