# Self-host Syncthing Discovery Server

> 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.

- Page: https://levelrail.com/templates/syncthing-discovery/
- JSON: https://levelrail.com/templates/syncthing-discovery.json
- Category: Networking
- Licence: MPL-2.0 (Copyleft license)
- Source: https://github.com/syncthing/syncthing
- Upstream docs: https://docs.syncthing.net/users/stdiscosrv.html

## Requirements
- Memory: about 64 MiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: 2.1.7

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| syncthing-discovery | syncthing/discosrv | 2.1.7 | 8443 | data -> /var/stdiscosrv |

## Deploy

### CLI

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

### API

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

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

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

## Questions

### 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.

Self-host Syncthing Discovery Server, Syncthing Discovery Server docker compose file, deploy Syncthing Discovery Server on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
