Confused: config for local discovery only

my syncthing listener port (22000) is accessible via a Traefik proxy via

On my home server, I have disabled Global Discovery, Relay, NAT Traversal. But what should I fill in “Sync Protocol Listen Addresses” ? I have seen the documentation, but whatever I do, when I check the log Syncthing keeps receiving local announcements from itself (same device ID).

Perhaps this is normal.

Issue now is: what do I fill in on my Android device? I have also disabled Global Discovery, Relay and NAT Traversal. But what should I fill in as Sync Protocol Listen Address?

I can add the device via its ID and, but it stays disconnected and the server does not show the usual popup.

I know the proxy part works because when I change the port in the proxy to 8384, my webUI becomes exposed (tested shortly).

Traefik is a http proxy, syncthing protocol does not use http.

AHA :slight_smile:Thanks for that. I realise now, last time I set up Syncthing I used a CNAME forward from my domain name directly to my homeip:22000 and that did work. I did not use a http proxy in between.

I wanted to use https but I guess thats a bit dumb since Syncthing already uses a secure transfer protocol.

I guess my remaining question is: if I only have a static setup with static IPs or domains (no proxy), what should the “sync protocol listening address” be on the server and on the clients?

Local discovery is still nice because it’s less manual work to configure clients on the local LAN, I still want that to work even with the static IPs.

Why don’t you just stay with the defaults? What are you trying to achieve?

It does not work with the defaults (“default”). I assumed I had to therefore change it.

I mean everything at their default settings, including discovery relays and what not.

Because I like to be independent of other (relay/discovery) servers. I only want to use owned devices, not someone elses server. SyncThing supports that, so why not, if I have a static IP server? There is simply no need for other servers in this situation.

Sure, then you just need to replace remote devices address to point at the static ip address, you don’t need to mess around with the listen address.

I found out what I did wrong. On client side all I had to do was fill in tcp://, that works.

In this case: >> forwards to … (Mikrotik dyndns) >> forwards to my IP.

At first, I had it like this: >> forwards to … >> forwards to my IP. On client side I used only tcp://, this does not work.

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