Use this page as the order of operations. Each step names the setting and the command, and links to the page that explains the reasoning. Run behind Cloudflare lists what the proxy does not hide.
The one-command path
levelrail-cli cdn setup <app> runs the checklist below for one app and returns one result per step: provider connected, zone SSL/TLS mode, DNS-01 certificates, client address preset, a DNS preview, the apply, and a final check. Add --dry-run to stop before any change.
- A failed step stops the apply and changes nothing. A zone in Off or Flexible SSL mode is a failure, because it causes a redirect loop.
- A warning does not stop the apply. DNS-01 and the client address preset are reported with the command that fixes them. Setup never changes the zone’s settings, and it never turns on the client address preset for you, because that setting weakens a check and needs your confirmation.
- The apply turns the proxy on for the app and re-syncs only the DNS records Levelrail created for it.
- The same run is available as
POST /api/v1/apps/{name}/cdn/setup with {"provider": "cloudflare", "dry_run": true}. Only Cloudflare is connected through setup today.
levelrail-cli cdn edge <app> (API: GET /api/v1/apps/{name}/edge) shows the app’s proxy state, provider, zone, SSL mode, the last cache purges and the cache hit rate of the ingress cache. The purge history is kept in memory, so it resets when the control plane restarts.
Setup and the edge view are not yet verified against a live Cloudflare zone (pending run). The manual steps below remain the reference.
Before you turn the proxy on
Set the zone
Set the client address source
Without the preset, every visitor appears to come from a Cloudflare address in access logs, Shield rate limits and country rules. With it, the ingress reads CF-Connecting-IP only when the connection comes from Cloudflare’s published ranges. A forged header from any other peer is ignored. The preset is a stored setting and applies at once. The ranges refresh in the background, and the last good list is kept if a refresh fails.
Turn the proxy on, one app at a time
For a new record, levelrail-cli settings ingress set --dns-proxied makes proxying the default for records Levelrail creates. Keep it off until the steps above are done.
Upload size and long requests
Keep the origin reachable only through the proxy
Cache purge
When an app’s records are proxied, a static publish, a deploy, a held build publish and a rollback each purge Cloudflare’s cache for the app’s hostnames. A container app is purged when the deploy or rollback is accepted, before the new release is serving, so a page cached in between can still be old. A build triggered by a push to the repository does not purge a container app yet. Every attempt is added to the purge history shown by cdn edge.
The purge is best effort. If it fails, the deploy, publish or rollback still succeeds, and the response carries a cdn_warning field. See CDN and caching.
Rollback does not restore the proxy
A rollback puts back an earlier release and purges the cache. It does not change the proxy setting or the DNS records. If you turned the proxy on or off after that release, the rollback leaves the current setting in place. Set it back with levelrail-cli apps cdn set <app> --proxied on|off|inherit.
This is read from the documented behavior, not yet confirmed on a live proxied record (pending run).
Verify from outside
Last modified on November 8, 2026