TLS protocol error / TLS handshake issue - how to debug?

Hey there,

Logs below. Both device have port forwarding open, and both are on v1.22.0. LMK if there’s any guidance you can give here. Thanks!

2022-10-25 09:36:12 Established secure connection to 5BMU7PB-MGYDGPC-ACPZWHA-UM1CFTN-WNF7SAU-N2SS3K6-ANYFHUJ-X6E7XA7 at 192.168.1.118:22000-70.187.140.30:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
2022-10-25 09:36:12 Device 4BMU7PB-MGYDGPC-ADPZWHA-BM2CJTQ-CNG7S6U-P2CS1K3-ANYJVUJ-X7E7MB7 client is "syncthing v1.22.0" named "9 Arrows" at 192.168.1.118:22000-70.187.140.30:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
2022-10-25 09:36:14 Completed initial scan of sendonly folder "Media" (bq96k-9htzp)
2022-10-25 09:36:25 Detected 1 NAT service
2022-10-25 09:37:25 Joined relay relay://38.145.211.217:22067
2022-10-25 10:06:13 Sent usage report (version 3)
2022-10-26 02:45:11 Listen (BEP/tcp): TLS handshake: read tcp 192.168.1.118:22000->167.248.133.44:43852: read: connection reset by peer
2022-10-26 02:45:11 Peer at 192.168.1.118:22000-167.248.133.44:34516/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 did not negotiate bep/1.0
2022-10-26 02:45:11 Got peer certificate list of length 0 != 1 from peer at 192.168.1.118:22000-167.248.133.44:34516/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256; protocol error
2022-10-26 02:45:11 Peer at 192.168.1.118:22000-167.248.133.44:36818/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 did not negotiate bep/1.0
2022-10-26 02:45:11 Got peer certificate list of length 0 != 1 from peer at 192.168.1.118:22000-167.248.133.44:36818/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256; protocol error
2022-10-26 02:45:12 Listen (BEP/tcp): TLS handshake: tls: first record does not look like a TLS handshake

Other side is something non-Syncthing or some proxy or antivirus is interfering.

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