Weak connection - checked firewalls/ports but no luck

To preface, I am a first time forum user and do not speak open source language very well - please forgive how dumb I am about to sound.

We are using Syncthing to remote backup a large amount of files for video editing from a NAS to NAS in two very different locations and both using Mac OS. Both devices are on version 2.1.2-1 and when checking for updates, we are said to be on the latest version (we do not have permission to manually update).

The issue: for months Syncthing has worked seamlessly. Both devices were pause and disconnected for a week and when reconnected this past Tuesday, we can not re-establish a connection. Tuesday and Wednesday, 0 connection was made, today we are getting connected but its very weak and almost immediately disconnects and provides the following errors.

We have checked our firewall permissions, quit and restarted both Syncthings and our machines, and are now considering uninstalling syncthing and re-installing. Before we do the latter, does anyone have an understanding of what is happening and if there is a solution for us AND/OR an opinion on uninstalling and re-installing Syncthing?

Don’t reinstall, that won’t change a thing. It’s simply not how (this) software works.

As for the connections, have you checked whether the reported IPs are sensible and reachable? Syncthing shows you what connections are attempted, but you’ll need some general purpose network diagnostic tools to check where those connections fail. QUIC is UDP, if that matters during testing.

If you can make a connection with netcat or similar, but not with Syncthing, then we have identified an issue. But that is unlikely to be the case.

When it disconnects after short periods, what does the log say (Actions > Logs)?

I’d still suspect some firewall or other network component blocking the traffic.

this is what the logs stated after the last connect drop:

2026-09-10 16:31:54 INF Lost device connection (kind=primary device=YJHRCC7 connection=192.168.0.90:52810-208.84.101.77:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-66K1UBASMMBGGK8USIQR702LTE error="reading message: local error: tls: bad record MAC" remaining=0 log.pkg=model)
2026-09-10 16:31:54 INF Connection closed (device=YJHRCC7 connection=192.168.0.90:52810-208.84.101.77:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-66K1UBASMMBGGK8USIQR702LTE error="reading message: local error: tls: bad record MAC" log.pkg=model)
2026-09-10 16:32:12 INF Established secure connection (device=YJHRCC7 connection.local=192.168.0.90:53750 connection.remote=208.84.101.77:22067 connection.type=relay-client connection.lan=false connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=50 connection.id=66K1V799V3GH01LKN2NN9DKP2U log.pkg=connections)
2026-09-10 16:32:12 INF New device connection (device=YJHRCC7 address=208.84.101.77:22067 remote.name=DMUNDY-LT.local remote.client=syncthing remote.version=v2.1.2 log.pkg=model)

That shows the relay connection failing because of some TLS error. Maybe the relay is not behaving properly, or there is some MITM attack going on (some people call it deep package inspection).

Do you also have logs from the direct connections being tried and failing?

Please use the code formatting feature when posting logs on the forum.

Apologies for the incorrect code formatting.

I do not have logs from the direct connections but happy to try if someone could educate me on how to…

Thank you for even attempting to help me resolve this!

Where you access the logs (Actions > Logs), there is a second tab “Debugging Facilities”. Find the connections category and set it to “Debug” level. Then you will see additional output for the failed attempts.