Several tunnels

Every route normally goes on your machine's tunnel, which Teitunnel creates with the first route. You can give the machine more tunnels, for example to keep staging routes apart from production: each tunnel runs its own connector, so you can stop, restart or keep one running on its own, and each has its own logs and traffic.

Use several tunnels when groups of routes should start and stop independently, or when one group should keep running after you quit the app and another shouldn't. For one hostname served by several machines, use load balancing instead.

Create a tunnel in the appCopy Anchor Link

Put routes on itCopy Anchor Link

With more than one tunnel, the New Route sheet has a Tunnel menu ("Which of this Mac's tunnels serves the route."). It starts on the machine's default tunnel. The routes list then says which tunnel serves each route (→ localhost:4000 · staging), and a route is only live when its own tunnel's connector is.

A hostname is routed once per machine: Teitunnel refuses a route that another of your tunnels already serves ("beta.yourhost.com is already routed on tunnel “staging”. Remove it there first, or edit it there."), so the DNS record can only point one way.

Run and removeCopy Anchor Link

In Tunnels, each of the machine's tunnels has:

• Stop on This Mac / Start on This Mac;
• Keep running when Teitunnel quits (Always-on): the connector runs as a service, and routes stay up after you quit the app and start again when you log in;
• its Connectors, Logs and details (routes, tunnel ID, when it was created);
• Delete….

Deleting a tunnel removes its routes and the DNS records Teitunnel created for them, with their logins, offline pages, webhook inboxes, edge rules and service tokens; your other tunnels aren't touched. Private networks stay on the default tunnel.

The Doctor checks each tunnel on its own, and its fixes apply to the tunnel the problem is on.

Run an existing tunnel hereCopy Anchor Link

A tunnel made elsewhere in the account (in the dashboard, or by Teitunnel on another machine) can run on this machine too: select it in Tunnels (In Cloudflare) and choose Run on This Mac…. Nothing changes in Cloudflare; its routes stay as they are and this machine serves them as well.

If another machine runs it at the same time, Cloudflare splits requests between both ("Another machine runs this tunnel now. Cloudflare will split its requests between both machines, so only do this if this Mac runs the same services."). To serve one hostname from several machines on purpose, with health checks, use load balancing.

Tunnels configured with a local config.yml can't be run this way; import their routes instead. Teitunnel doesn't change the routes of tunnels it didn't create.

From the terminalCopy Anchor Link

teitunnel tunnels                                # this machine's tunnels (--json)
teitunnel tunnel create staging
teitunnel route add beta.yourhost.com 4000 --tunnel staging
teitunnel route remove beta.yourhost.com         # finds the tunnel by itself
teitunnel always-on on --tunnel staging          # keep only staging running as a service
teitunnel export config-yaml --tunnel staging
teitunnel tunnel adopt home-lab                  # run an existing tunnel here too
teitunnel tunnel delete staging

tunnel create and tunnel delete show the plan first; -y applies without asking and -a picks the account. tunnel adopt takes a name or id and changes nothing in Cloudflare.

What happens on CloudflareCopy Anchor Link

• Create makes a remotely-managed tunnel with that name. It costs nothing: Cloudflare Tunnel is free on every plan.
• A route on it puts the hostname in that tunnel's configuration and points the DNS record at that tunnel.
• Delete stops its connector, removes the tunnel's routes and the DNS records Teitunnel created for them (with what Teitunnel put in front of them), then deletes the tunnel. DNS records Teitunnel didn't create are never deleted.

TroubleshootingCopy Anchor Link

RelatedCopy Anchor Link