Self-host Syncthing Relay Server with Levelrail

Private relay server that carries Syncthing traffic between devices that cannot connect directly. Exposes a small status page.

  • Authorsyncthing
  • LicenceMPL-2.0
  • Memory64 MiB
  • Services1

How to self-host Syncthing Relay Server

  1. Pull the images

    One image is pulled on your server.

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

    One service starts in a single Compose app, on ports 22070, 22067.

  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

  • Add the relay address to each device under the relay servers setting, using port 22067. The status page is on port 22070.

Syncthing Relay Server requirements

Memory
About 64 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
22070, 22067
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 Relay 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 Relay Server docs page.

Deploy Syncthing Relay Server your way

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

Deploy Syncthing Relay Server from the CLI

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

Deploy Syncthing Relay 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-relay/deploy

Syncthing Relay Server configuration

Syncthing Relay Server services

ServiceImagePortsVolumes
syncthing-relay syncthing/relaysrv:2.1.7 22070, 22067 none

Syncthing Relay Server environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
22070, 22067
Volumes
none

Syncthing Relay Server FAQ

How much memory does Syncthing Relay Server need?

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

Does Syncthing Relay Server run on arm64?

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

What licence is Syncthing Relay Server under?

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

Does Syncthing Relay Server need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Syncthing Relay Server use?

Syncthing Relay Server listens on ports 22070 and 22067 inside the stack.

Can I deploy Syncthing Relay 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 Relay 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/relaysrv:2.1.7 is what you deploy there.

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