Cloudflare Gateway Management
This page covers managing a gateway you’ve already set up. To enable it for the first time, start with Cloudflare Gateway — that page has the full setup walkthrough, prerequisites, and security notes.
Once the gateway is running, your CI Account at hub.ci.computer is where you control it remotely — including from a device that isn’t on your home network.
What you can do from your account
| Action | Where |
|---|---|
| See which apps are currently exposed | Device page → Exposed apps |
| Expose or unexpose an app | Device page, or your Hub dashboard |
| Check tunnel health | Device page → connection status |
| Disable the gateway entirely | Device page → Disable Gateway |
Exposing and unexposing works from either side — your CI Account or the Hub dashboard. Changes take effect immediately.
Unexposing an app removes its public URL, but anyone who was already using it loses access without warning. If an app was exposed by mistake, unexpose it and rotate any credentials that may have been reachable.
When your Hub is offline
The device page shows the last-known state. You can queue changes, but they apply when the Hub reconnects — the tunnel has to be up for the Hub to receive them.
If a device shows offline while it’s actually running, check that the Hub still has outbound internet access, then verify the tunnel container:
docker ps --filter name=cloudflaredUnpairing
Unpairing a device from your CI Account tears down its gateway and revokes the tunnel credentials. Exposed apps stop being publicly reachable immediately.
To pair again later, generate a fresh pairing code — codes are single-use. See Device Pairing.
If tunnel state is left behind after unpairing, see Remove tunnel token manually.