v1.44.1October 6, 2026

Adopt Any Tunnel

Cloudflare Tunnels whose services live on the VPS itself, on localhost ports or a Kubernetes (k3s) ingress, can now be adopted with a new "Run on the entry-point VPS" option that checks every hostname before changing anything. This release also fixes the SSL certificate list re-checking domains in a loop and the adoption dialog closing mid-adoption.

Download v1.44.1

Get this version from GitHub Releases

Download

What's Changed

New Features

Take over a Cloudflare tunnel whose services live on the VPS itself — a new "Run on the entry-point VPS" adoption option handles tunnels that point at localhost ports or a Kubernetes (k3s) ingress on the same machine
Every existing hostname is verified reachable from the VPS before the new connector starts — if any check fails, nothing changes on the server or in Cloudflare
Tunnels are fully checked no matter how many hostnames they carry, not just the first few
An old connector Server Compass can't identify — like one managed by Kubernetes — no longer blocks adoption
After adopting, keep managing those hostnames in Cloudflare; adding Docker service routes needs a standard connector

Improvements

A clearer reason when an origin points at localhost — the adoption check now suggests the entry-point VPS option instead of a generic "unreachable" error
Long hostname lists scroll in the adoption dialog instead of overflowing it

Bug Fixes

Fixed the SSL certificate list re-checking every domain in a loop — statuses now finish checking once instead of restarting each time a result arrived
Fixed the tunnel adoption dialog closing mid-adoption — pressing Escape while it's working no longer dismisses it
Fixed an old error message sticking around when switching between adoption options