Advanced tunnel modes

Lumio-owned connector#

The advanced Cloudflare connection panel shows local-origin health, edge readiness, managed process and retry timing. Let Lumio manage the tunnel enables supervision. cloudflared executable is an advanced binary path; normal setup uses the bundled official executable. Connector token or Replace connector token · optional stores the protected credential. Save/check/start/stop actions apply to the owned connector, not arbitrary system processes.

The server supervises its child and retries failures with backoff. Closing Administration does not close that child. With managed remote access enabled, the native server holds an idle-system-sleep assertion; display sleep is allowed. Forced sleep, closing a laptop lid, logout, shutdown or losing the network can still interrupt access. Physical sleep/reboot qualification is not implied by an edge-ready label.

Existing external connector#

If a system connector already runs, Lumio avoids creating a duplicate. The One-time system-service migration disclosure describes stopping/disabling that exact external job before transferring ownership. This needs local administrator privileges and may require you to enter your Mac password locally. Preserve the previous service configuration for rollback. Never stop an unrelated tunnel.

Read-only monitoring#

Manage existing Cloudflare Tunnel → Monitor existing tunnel is a different mode. It accepts Cloudflare Account ID, Tunnel ID and a Cloudflare API token scoped to Tunnel Read. This is an account API credential, not the connector token.

1. Enter the intended IDs and read-only API credential.
2. Use the test/verify action and inspect the returned tunnel name, configuration owner and capabilities.
3. Confirm the intended tunnel before saving/enabling monitoring.
4. Use refresh/check controls to update the displayed time. Clear monitoring through its own controls if no longer needed.

Monitoring does not configure DNS, rewrite ingress, install a system service, acquire a connector credential or prove public playback. API authorization, the running child and public HTTPS health are independent. Keep advanced credentials out of browser storage, URLs and exported screenshots. See official Tunnel documentation.