Cloudflare Container Gateway Auto-Start

Problem

When running a bot (Discord, Telegram, Slack) inside a Cloudflare Workers Container that's protected by Cloudflare Access, the bot goes offline because the gateway process only starts when an authenticated request comes in. Since bot messages are outbound connections (not inbound HTTP), no request triggers the startup.

Context / Trigger Conditions

• Bot stops responding to Discord/Telegram messages
• /api/status returns {"ok": false, "status": "not_running"}
• /sandbox-health returns {"status": "ok"} (container is up, but process isn't)
• Bot works after visiting the web UI in browser (which authenticates via CF Access)
• This happens after deploys or when the container restarts
• Using Cloudflare Workers Containers (Sandbox) with Durable Objects

Root Cause