Tailscale DERP
on your own machine
Runs derper, Tailscale's relay server, for your tailnet's own DERP map. Use a domain on port 443 for a Let's Encrypt certificate, or an IP address on any port for a self-signed one; STUN needs a second, UDP allocation. Clients can't be verified without tailscaled, so anyone who finds it can relay their encrypted traffic through it.
$12 a month per machine, with as many servers as it can run. Already on Raptor? It's in your team's Eggs, as software/tailscale-derp.
What Raptor does for it
- Backups
- Incremental and encrypted on your machine, every day by default. Restore one file or the whole server.
- Runs on
- x86 and ARM machines, on Raptor's Debian image.
- Every server
- A live console, a file manager with a trash, schedules, crash restarts, alerts, and SFTP. It keeps running if Raptor goes down.
Settings you can change
From the server's Startup tab, without touching a file.
- Version
- The Tailscale release derper is built from, such as 1.104.7, or latest.Default
latest - Hostname
- The domain name that points at this server, or its public IP address.
- Certificate
- letsencrypt gets a certificate for the domain (the server must be on port 443); manual uses certs/<hostname>.crt and .key, made for you when the hostname is an IP address.Default
letsencrypt - STUN port
- The UDP port STUN answers on, which helps devices connect directly: one of the server's allocations.Default
3478
From a bare machine
Link your machine
One command on any Debian or Ubuntu box, at home or rented.
Pick Tailscale DERP
Raptor installs it and starts it, on images it keeps updated.
Open it
At an address your machine comes with, or your own domain.
Made by Raptor and MIT-licensed. Written for Raptor from Tailscale's custom DERP server documentation, https://tailscale.com/kb/1118/custom-derp-servers (derper is BSD-3-Clause); no upstream egg. Icon: the Tailscale logo, from https://github.com/tailscale. The egg's source.