Connectivity

Connectivity contains host-level network connectors that are separate from Sites and applications.

Cloudflare Tunnel

Control supports a remotely managed Cloudflare Tunnel. Create the tunnel in Cloudflare Zero Trust, then paste its tunnel token into Control. The token is write-only and is not shown again.

Connect a tunnel

1. Create a remotely managed tunnel in Cloudflare Zero Trust.
2. Copy the tunnel token.
3. Open Server → Connectivity and choose Connect tunnel.
4. Paste the token and wait for Control to report the connector online.

Publish a Site

After the connector is online, publish an eligible running Site from its Cloudflare Tunnel section. Control uses the configured Cloudflare DNS provider to create/update the publication it is responsible for.

Existing unrelated Cloudflare rules, DNS records and Access policies are not silently adopted or overwritten. A conflicting external configuration is shown for review.

Disconnect or remove

Disconnect stops the local connector while keeping its configured credential for later reconnection. Remove Connector removes Control's connector configuration. Unpublish Control-managed Site routes before removing the connector.

Dedicated catch-all ingress for external Micro CMS domains

A Host address can be assigned to one running Site as Dedicated IP · catch-all. This supports a Micro CMS Bridge/Silo host that accepts external domains registered in Micro CMS.

1. Add/select the external address under Server → Host Networking.
2. Bind the Micro CMS Site to that address as Dedicated catch-all ingress.
3. Register the customer's exact domain in Micro CMS.
4. At the customer's DNS provider, point the hostname's A/AAAA records to the dedicated Control address.

After public DNS is ready, Control can issue the exact-name certificate for the registered hostname. Unknown hostnames that merely point at the address do not become managed domains automatically.