Self-host Syncthing Discovery Server with Levelrail

Private global discovery server that lets your Syncthing devices find each other without the public one. Plain HTTP mode, meant to sit behind your own TLS proxy.

  • Authorsyncthing
  • LicenceMPL-2.0
  • Memory64 MiB
  • Services1

How to self-host Syncthing Discovery Server

  1. Pull the images

    One image is pulled on your server.

    Show images
    • syncthing/discosrv:2.1.7
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 8443.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Put a TLS proxy in front of the address, then add it to each device under the global discovery servers setting.

Syncthing Discovery Server requirements

Memory
About 64 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8443
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MPL-2.0, copyleft license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Syncthing Discovery Server. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Syncthing Discovery Server docs page.

Deploy Syncthing Discovery Server your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Syncthing Discovery Server from the CLI

levelrail-cli templates deploy syncthing-discovery --name my-syncthing-discovery

Deploy Syncthing Discovery Server with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/syncthing-discovery/deploy

Syncthing Discovery Server configuration

Syncthing Discovery Server services

ServiceImagePortsVolumes
syncthing-discovery syncthing/discosrv:2.1.7 8443 data -> /var/stdiscosrv

Syncthing Discovery Server environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
8443
Volumes
1 named mount: data -> /var/stdiscosrv

Syncthing Discovery Server FAQ

How much memory does Syncthing Discovery Server need?

The catalog lists about 64 MiB of memory for Syncthing Discovery Server.

Does Syncthing Discovery Server run on arm64?

For Syncthing Discovery Server, arm64 support is not confirmed; amd64 is unknown.

What licence is Syncthing Discovery Server under?

Syncthing Discovery Server is licensed under MPL-2.0, which is copyleft, so changes you distribute must be shared under the same terms.

Does Syncthing Discovery Server need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Syncthing Discovery Server use?

Syncthing Discovery Server listens on port 8443 inside the stack.

Where does Syncthing Discovery Server keep its data?

In a named volume: data mounted at /var/stdiscosrv.

Can I deploy Syncthing Discovery Server on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Syncthing Discovery Server, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image syncthing/discosrv:2.1.7 is what you deploy there.

levelrail-cli templates deploy syncthing-discovery --name my-syncthing-discovery