3 ms·

> You can also use Tailscale serve to get a HTTPS url like Cloudflared but it's only visible to your tailnet For public access, similar to these cloudflare tun

> You can also use Tailscale serve to get a HTTPS url like Cloudflared but it's only visible to your tailnet For public access, similar to these cloudflare tunnels, there's Tailscale Funnel. https://tailscale.com/docs/features/tailscale-funnel https://tailscale.com/docs/features/tailscale-funnel

nacs 20d ago
Tailscale funnel works well but you can only have 1 per Tailscale instance (1 per machine) at the https endpoint so if you want to have a few apps, the others will go on non-https, custom-port URLs.
- deleted 20d ago
  [deleted]
- fragmede 20d ago
  [dead]
- MattCruikshank 20d ago
  That's why I keep using tsnet directly, where you can have as many virtual machines, doing sharing or funneling, as you want to. The CLI doesn't let you do as much as the go library does.
- bakkoting 20d ago
  You can set up paths that route to different local ports. As long as your apps don't need to live at the root path you can have as many as you like. And you can still have something on the root path as long as it doesn't need the subpath. Here's `tailscale funnel status` on my machine: $ tailscale funnel status # Funnel on: # - https://my-machine.tailXXXX.ts.net https://my-machine.tailXXXX.ts.net (Funnel on) |-- / proxy http://localhost:3000 |-- /foo proxy http://localhost:3001 |-- /bar proxy http://localhost:3002 |-- /baz proxy http://localhost:4004
  - Natfan 18d ago
    or just use a tailscale sidecar[0] in a docker container and give it any hostname you want [0]: https://tailscale.com/blog/docker-tailscale-guide https://tailscale.com/blog/docker-tailscale-guide
- justinc8687 19d ago
  I have multiple funnels running at once. I just put a tailscale container into my compose stack and that way each compose stack gets its own tailscale instance and thus its own funnel. Happy to share the setup if at all interested.
- havnagiggle 19d ago
  Reverse proxy to additional endpoints.

nacs 20d ago

Tailscale funnel works well but you can only have 1 per Tailscale instance (1 per machine) at the https endpoint so if you want to have a few apps, the others will go on non-https, custom-port URLs.

deleted 20d ago
[deleted]
fragmede 20d ago
[dead]
MattCruikshank 20d ago
That's why I keep using tsnet directly, where you can have as many virtual machines, doing sharing or funneling, as you want to. The CLI doesn't let you do as much as the go library does.
bakkoting 20d ago
You can set up paths that route to different local ports. As long as your apps don't need to live at the root path you can have as many as you like. And you can still have something on the root path as long as it doesn't need the subpath. Here's `tailscale funnel status` on my machine: $ tailscale funnel status # Funnel on: # - https://my-machine.tailXXXX.ts.net https://my-machine.tailXXXX.ts.net (Funnel on) |-- / proxy http://localhost:3000 |-- /foo proxy http://localhost:3001 |-- /bar proxy http://localhost:3002 |-- /baz proxy http://localhost:4004
- Natfan 18d ago
  or just use a tailscale sidecar[0] in a docker container and give it any hostname you want [0]: https://tailscale.com/blog/docker-tailscale-guide https://tailscale.com/blog/docker-tailscale-guide
justinc8687 19d ago
I have multiple funnels running at once. I just put a tailscale container into my compose stack and that way each compose stack gets its own tailscale instance and thus its own funnel. Happy to share the setup if at all interested.
havnagiggle 19d ago
Reverse proxy to additional endpoints.