Troubleshooting: symptoms

Last updated 2 November 2026

Machines are not open yet. These pages describe Machines as they will open; until then, a create answers region_not_offered (422), “Machines are not offered in any region yet.”

Find what you see when a Machine does something you did not expect and no refusal says why: the cause, and what to do.

What you see	Why	What to do
Files, memory or processes are gone after a sleep.	Every wake starts fresh (see What a wake starts with).	Keep what must last in its database or on its Volume (see Keep data in its database and Volume).
Its own connections fail after a wake, or its timers never fire.	A wake is a new boot: no connection or timer from before the sleep comes back.	Connect again after each wake, and keep anything that must happen later in the database rather than in a timer.
It sleeps after about 2 minutes.	No request and no connection of its own was open, and it used almost no CPU or network.	Expected; the next request wakes it (see When it sleeps).
A change of image, command, env or shape did not apply.	It applies at the next wake, and requests have kept the Machine awake.	`tonbo machine sleep` (see Apply it now).
A push under the same tag did not apply.	The tag was resolved to a digest when you named it.	Name the tag again (see A new image).
It stopped while it was working.	No request was open, so it went to sleep; it used more memory than its shape; or your credit could not pay for the next ten minutes, and Tonbo stopped it.	Keep a request open while the work runs, choose a larger shape, or add credit (see What keeps it awake and Credit); the next request wakes it.
It went to sleep with a request or a connection open.	Tonbo removed or patched the host it ran on; a request still running then ends with 502 and may have run.	Send the request again; it wakes the Machine on another host. Send an Idempotency-Key with any request that must not run twice (see Request guarantees).
Its state stays creating.	Its image is still being pulled; some registries limit anonymous pulls per address.	Wait; `tonbo machine show` says when it is `active`.
My program exits or crashes, and I cannot see why.	What a Machine’s program prints cannot be read. A program that exits as it starts makes requests wait and fail, then answer crash_backoff.	Run the image on your computer with the same command and environment variables (see Try it on your computer first); `tonbo machine show` gives the Machine’s state and any image failure.
The database will not open in the Machine.	The image is based on musl (Alpine), which the database package is not built for.	Use a glibc-based image (see Requirements).
Every outbound connection from the Machine fails.	Tonbo blocked the outbound access of this Machine or of your whole account, as the outbound access text allows. `tonbo machine show app --json` lists an `egress_blocked` condition in `status.conditions`, with its scope and, for a block that ends by itself, when it ends.	Wait until the time it names; a block with no end stays until Tonbo lifts it.