Network filter munges external device's Device-ID

I live in a care home and connect via their Internet connection. It has some filtering on it. (Fortinet?)

I have an external VPS on which I have installed Syncthing. But when I try to connect any device to it (desktop, laptop, 2x smartphones) when they are on the care home’s Internet connection, it fails.

Here’s what appears in the Syncthing interface on things that I attempt to connect to the VPS.

tcp://[VPS IP]:22000


I’ve tried using a different port - 22001 - and the same thing happens.


If I connect laptop, mobile phones to a different Internet connection - e.g. mobile Internet - it all works just fine, and everything syncs.

So I’m assuming something in this hokey Internet connection provided by the care home messes with Syncthing.

  • Have you come across anything like this before please?
  • Is there a way of getting round it?! (I don’t want to have to permanently VPN)

Thank you


It seems like a TLS-inspecting proxy is in use, which is essentially a man-in-the-middle attack. Syncthing is designed to be resistant again this, i.e., there is no work-around in Syncthing. You need to get a clear path to the other side, via a VPN, a firewall or proxy exclusion, etc.


Much appreciated, thank you ever so much - and for an excellent piece of software.

Ah. This is another reason to avoid the home’s Internet. I think I may resurrect my Starlink connection.


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