Machine not auto-stopping/suspending

Questions / Help
1

App: counsel-openclaw-spike
Machine: 784065dc3e1d68 (iad, shared-cpu-2x, 2048MB)
flyctl: 0.4.13

My machine won’t auto-stop or auto-suspend despite having the correct configuration and zero client connections.

Current machine config (verified via fly machine status -d):
“autostop”: “suspend”,
“autostart”: true,
“min_machines_running”: 0

What I’ve verified:

  • Zero external connections — confirmed via /proc/net/tcp on the machine. Only the Fly proxy
    keepalive and SSH session present.
  • No persistent outbound connections (Telegram plugin disabled)
  • Waited 20+ minutes with no clients connected — state stays started
  • Tested both “suspend” and “stop” values for autostop — neither triggers
  • Ran fly machine uncordon — command succeeded but no change in behavior
  • rootfs.persist is “never”
  • Machine was last deployed today via fly deploy (release v19)

Service config: Single [http_service] on internal port 3000. Node.js process bound to 0.0.0.0:3000
(confirmed via /proc/net/tcp). Also listens on 127.0.0.1:3003 (localhost only, not proxied).

Could you check if there’s any machine-level state preventing the proxy from auto-stopping this
machine? I saw a similar issue in this thread (fly machines not auto stopping even when auto_stop_machines = ‘stop’) where a machine had been cordoned by mistake — I’ve already tried uncordon but the problem persists.

3

The machine started suspending correctly after two changes:

  1. Disabled a plugin that maintained persistent outbound HTTPS polling connections — these were keeping the machine “active” from the proxy’s perspective, even though no inbound client connections existed
  2. Replaced the machine (via fly secrets set, which triggers a rolling replacement) — the fresh machine picked up auto-suspend behavior immediately

The original machine may have had stale proxy state. The replacement suspends within ~5 minutes of the last connection closing and wakes in 1-3 seconds on the next request.

Root cause: Persistent outbound connections count as activity for Fly’s idle detection. Once those were eliminated, auto-suspend worked as expected.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.