> Documentation index: https://docs.kiste.run/llms.txt, a list of every page in this documentation.

# K: Kisten (machines, snapshots, images, environments, commands)

> Every K error code: what it means, when it happens and how to fix it.

35 codes. Each one is part of an error answer as `code`; `type` is the stable name that scripts branch on. The CLI shows the code at the end of its message, for example `(code: K01)`. Words in braces, such as `{name}`, are filled in with the actual value.

## K01

`machine_not_found` · HTTP 404

> There is no Kiste named {name} in your account. (code: K01)

**When it happens.** A request named a Kiste that does not exist in your account, or that was deleted.

**How to fix it.** Check the name in your list of Kisten.

**In the CLI.** Check available names with `kiste list`.

**Retry.** No. Retrying the same request gives the same answer.

## K02

`machine_name_taken` · HTTP 409

> You already have a Kiste named {name}. (code: K02)

**When it happens.** Creating, renaming, forking or restoring a Kiste used a name another Kiste in your account already has.

**How to fix it.** Choose another name, or delete or rename the existing Kiste first.

**Retry.** No. Retrying the same request gives the same answer.

## K03

`machine_not_running` · HTTP 409

> {name} isn't running. (code: K03)

**When it happens.** The action needs a running Kiste (terminal, commands, metrics, SSH, desktop, publishing an app, capturing a snapshot), and this one is stopped or parked.

**How to fix it.** Start the Kiste, then try again.

**In the CLI.** Start it with `kiste start {name}`, then try again.

**Retry.** No. Retrying the same request gives the same answer.

## K04

`machine_not_ready` · HTTP 409

> {name} is still starting up. (code: K04)

**When it happens.** The Kiste is running but has not finished booting: its command channel, SSH server or terminal is not available yet.

**How to fix it.** Wait a few seconds and try again.

**Retry.** Yes, with backoff: wait a moment and try again, waiting longer each time.

## K05

`machine_busy` · HTTP 409

> Another change to this Kiste is still in progress. (code: K05)

**When it happens.** A start, stop, restart, resize or delete was requested while another one was still running.

**How to fix it.** Wait until it finishes, then try again.

**Retry.** Yes, with backoff: wait a moment and try again, waiting longer each time.

## K06

`invalid_machine_request` · HTTP 400

> That Kiste request isn't valid: {detail}. (code: K06)

**When it happens.** A Kiste request had a value outside the allowed range (name, shape, lifetime, SSH key, terminal size, profile).

**How to fix it.** Correct the request and send it again.

**Retry.** No. Retrying the same request gives the same answer.

## K07

`machine_start_failed` · HTTP 500

> This Kiste couldn't start. Its disk is kept. (code: K07)

**When it happens.** The Kiste could not be booted after it was created, started, restored or forked.

**How to fix it.** Try again. If it keeps failing, contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K08

`snapshot_not_found` · HTTP 404

> There is no snapshot {snapshot} in your account. (code: K08)

**When it happens.** A request named a snapshot that does not exist, is not ready, or was deleted.

**How to fix it.** Check the snapshot in your list of snapshots.

**In the CLI.** Check snapshots with `kiste snapshot list`.

**Retry.** No. Retrying the same request gives the same answer.

## K09

`snapshot_busy` · HTTP 409

> The snapshot {snapshot} is already being deleted. (code: K09)

**When it happens.** A snapshot was deleted or restored while it was already being deleted.

**How to fix it.** Wait a moment and refresh your list of snapshots.

**Retry.** No. Retrying the same request gives the same answer.

## K10

`invalid_snapshot_request` · HTTP 400

> That snapshot request isn't valid: {detail}. (code: K10)

**When it happens.** A snapshot name or option was outside the allowed range.

**How to fix it.** Correct the request and send it again.

**Retry.** No. Retrying the same request gives the same answer.

## K11

`snapshot_failed` · HTTP 500

> The snapshot couldn't be taken. The Kiste is unchanged. (code: K11)

**When it happens.** Capturing a snapshot failed on our side.

**How to fix it.** Try again. If it keeps failing, contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K12

`image_not_found` · HTTP 404

> There is no image {image} in your account. (code: K12)

**When it happens.** A request named an image that does not exist.

**How to fix it.** Check the image in your list of images.

**In the CLI.** Check images with `kiste image list`.

**Retry.** No. Retrying the same request gives the same answer.

## K13

`image_name_taken` · HTTP 409

> The image name {image} is already taken. (code: K13)

**When it happens.** A new image used a name of another of your images or of a built-in image.

**How to fix it.** Choose another name.

**Retry.** No. Retrying the same request gives the same answer.

## K14

`image_in_use` · HTTP 409

> The image {image} is still used by a Kiste. (code: K14)

**When it happens.** An image was deleted while a Kiste still uses it.

**How to fix it.** Delete the Kisten that use it first.

**Retry.** No. Retrying the same request gives the same answer.

## K15

`image_not_ready` · HTTP 409

> The image {image} isn't ready yet. (code: K15)

**When it happens.** A Kiste was created from an image that is still being built or failed to build.

**How to fix it.** Wait until the image is built, then try again.

**Retry.** Yes, with backoff: wait a moment and try again, waiting longer each time.

## K16

`invalid_image_request` · HTTP 400

> That image request isn't valid: {detail}. (code: K16)

**When it happens.** An image name, component, version or size was outside the allowed range.

**How to fix it.** Correct the request and send it again.

**Retry.** No. Retrying the same request gives the same answer.

## K17

`environment_not_found` · HTTP 404

> There is no environment {environment} in your account. (code: K17)

**When it happens.** A request named an environment that does not exist.

**How to fix it.** Check the environment in your list of environments.

**In the CLI.** Check environments with `kiste environment list`.

**Retry.** No. Retrying the same request gives the same answer.

## K18

`environment_name_taken` · HTTP 409

> You already have an environment named {environment}. (code: K18)

**When it happens.** A new environment used a name you already use.

**How to fix it.** Choose another name, or update the existing environment.

**Retry.** No. Retrying the same request gives the same answer.

## K19

`invalid_environment` · HTTP 400

> That environment isn't valid: {detail}. (code: K19)

**When it happens.** An environment had an invalid repository, variable, secret file or setup script, or was too large.

**How to fix it.** Correct the environment and send it again.

**Retry.** No. Retrying the same request gives the same answer.

## K20

`environment_setup_failed` · HTTP 422

> The environment setup on {name} failed. (code: K20)

**When it happens.** The setup script of the environment exited with an error inside the Kiste.

**How to fix it.** Check the setup script of the environment, then start the Kiste again.

**Retry.** No. Retrying the same request gives the same answer.

## K21

`command_not_found` · HTTP 404

> There is no command {command} on this Kiste. (code: K21)

**When it happens.** A request named a command that does not exist or has finished.

**How to fix it.** Check the command ID.

**Retry.** No. Retrying the same request gives the same answer.

## K22

`command_id_taken` · HTTP 409

> A command with the ID {command} already exists. (code: K22)

**When it happens.** A command was started with an ID that was already used.

**How to fix it.** Use a new command ID.

**Retry.** No. Retrying the same request gives the same answer.

## K23

`invalid_command` · HTTP 400

> That command request isn't valid: {detail}. (code: K23)

**When it happens.** A command had an invalid argument, working directory, environment or interrupt reason.

**How to fix it.** Correct the request and send it again.

**Retry.** No. Retrying the same request gives the same answer.

## K24

`command_interrupt_failed` · HTTP 409

> The command couldn't be interrupted. (code: K24)

**When it happens.** Interrupting a running command failed inside the Kiste.

**How to fix it.** It may have finished already. Check its status and try again.

**Retry.** No. Retrying the same request gives the same answer.

## K25

`metrics_unavailable` · HTTP 409

> The usage of {name} can't be read right now. (code: K25)

**When it happens.** The Kiste did not answer the usage probe in time, or its answer could not be read.

**How to fix it.** Try again in a few seconds.

**Retry.** Yes, with backoff: wait a moment and try again, waiting longer each time.

## K26

`guest_unresponsive` · HTTP 409

> This Kiste stopped responding and was stopped. Its disk is kept. (code: K26)

**When it happens.** The system inside the Kiste stopped answering (it halted or hung), so it was stopped hard to keep its status honest.

**How to fix it.** Start it again.

**Retry.** No. Retrying the same request gives the same answer.

## K27

`snapshot_unavailable` · HTTP 409

> Snapshots aren't available for this Kiste right now. (code: K27)

**When it happens.** The computer that runs this Kiste cannot take live snapshots at the moment.

**How to fix it.** Contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K28

`machine_stop_failed` · HTTP 500

> This Kiste couldn't be stopped cleanly. Its disk is kept. (code: K28)

**When it happens.** Stopping the Kiste failed on our side.

**How to fix it.** Try again. If it keeps failing, contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K29

`machine_restart_failed` · HTTP 500

> This Kiste couldn't restart. Its disk is kept. (code: K29)

**When it happens.** Restarting the Kiste failed on our side.

**How to fix it.** Try again. If it keeps failing, contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K30

`machine_delete_failed` · HTTP 500

> This Kiste couldn't be deleted. (code: K30)

**When it happens.** Deleting the Kiste failed on our side; it still exists.

**How to fix it.** Try again in a minute. If it keeps failing, contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K31

`snapshot_restore_failed` · HTTP 500

> The snapshot couldn't be restored. The snapshot is kept. (code: K31)

**When it happens.** Restoring a snapshot into a Kiste failed on our side.

**How to fix it.** Try again. If it keeps failing, contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K32

`machine_fork_failed` · HTTP 500

> This Kiste couldn't be copied. The original is unchanged. (code: K32)

**When it happens.** Forking (copying) a running Kiste failed on our side; the working snapshot was removed.

**How to fix it.** Try again. If it keeps failing, contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K33

`snapshot_delete_failed` · HTTP 500

> The snapshot couldn't be deleted. (code: K33)

**When it happens.** Deleting a snapshot's storage failed on our side; the snapshot still exists.

**How to fix it.** Try again in a minute. If it keeps failing, contact support with the request ID.

**Retry.** No. Retrying the same request gives the same answer.

## K34

`snapshot_name_taken` · HTTP 409

> You already have a snapshot named {snapshot}. (code: K34)

**When it happens.** A snapshot was taken with a name another snapshot in your account already has.

**How to fix it.** Choose another name, or delete the existing snapshot first.

**Retry.** No. Retrying the same request gives the same answer.

## K35

`command_failed` · HTTP 500

> The command couldn't be run in {name}. (code: K35)

**When it happens.** The connection to the system inside the Kiste broke while a command was starting or running.

**How to fix it.** Check the program's name and that the Kiste is running, then try again.

**Retry.** No. Retrying the same request gives the same answer.

## Related topics

- [Overview](https://docs.kiste.run/errors.md)
- [N: Network and connections](https://docs.kiste.run/errors/n.md)
- [D: Desktop and browser links](https://docs.kiste.run/errors/d.md)
- [S: Kiste Stream (published apps on kiste.stream)](https://docs.kiste.run/errors/s.md)
- [A: Account and sign-in](https://docs.kiste.run/errors/a.md)
- [B: Billing](https://docs.kiste.run/errors/b.md)
- [L: Limits and capacity](https://docs.kiste.run/errors/l.md)
- [C: The kiste command-line tool](https://docs.kiste.run/errors/c.md)
- [P: Platform](https://docs.kiste.run/errors/p.md)
- Previous: [Overview](https://docs.kiste.run/errors.md)
- Next: [N: Network and connections](https://docs.kiste.run/errors/n.md)