tailscale serve: the commands that matter
Every tailscale serve command you will use, checked on Tailscale 1.102.4: foreground versus background, HTTPS ports, path routing, static files and raw TCP.
Filtering by topic #https · clear
Every tailscale serve command you will use, checked on Tailscale 1.102.4: foreground versus background, HTTPS ports, path routing, static files and raw TCP.
HTTP and HTTPS differ on the server side: a second listener, a redirect, HSTS you cannot easily undo, mixed content, and renewal that fails at 3am.
Tailscale serve puts HTTPS on a tailnet-only URL. Funnel opens that same port to the public internet. Which to use, and the policy gate that blocks funnel.
HTTP explained for people who run servers: methods, status codes, the headers that matter, what nginx logs, and where HTTP/3 and TLS fit in.
Run n8n on a VPS with Docker Compose, Postgres, and HTTPS behind a reverse proxy: the WEBHOOK_URL and encryption-key traps, plus every error string.