N: Network and connections
Every N error code: what it means, when it happens and how to fix it.
8 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: N01). Words in braces, such as {name}, are filled in with the actual value.
N01
compute_unreachable · HTTP 503
kiste.run can't reach the compute service right now. Your Kisten are safe. (code: N01)
When it happens. kiste.run could not connect to the computer that runs your Kisten. Nothing is lost; the connection usually returns within a minute.
How to fix it. Try again in a minute.
Retry. Yes, after 30 seconds. The answer carries Retry-After.
N02
compute_bad_response · HTTP 502
The compute service sent an answer kiste.run didn't expect. (code: N02)
When it happens. The computer that runs your Kisten answered with something kiste.run could not use.
How to fix it. Try again. If it keeps happening, contact support with the request ID.
Retry. No. Retrying the same request gives the same answer.
N03
request_timeout · HTTP 503
That took too long and was stopped. (code: N03)
When it happens. The request did not finish within its time limit.
How to fix it. Try again in a moment.
Retry. Yes, with backoff: wait a moment and try again, waiting longer each time.
N04
edge_unreachable · HTTP 0 · CLI exit code 7
Can't reach kiste.run. (code: N04)
When it happens. The command-line tool could not open a connection to kiste.run (no network, DNS, proxy or firewall).
How to fix it. Check your internet connection, then try again.
In the CLI. Check your internet connection, or run kiste doctor.
Retry. Yes, with backoff: wait a moment and try again, waiting longer each time.
N05
connection_interrupted · HTTP 0 · CLI exit code 7
The connection to kiste.run was interrupted. (code: N05)
When it happens. The connection broke while an answer or a command's output was still arriving.
How to fix it. Try again.
Retry. Yes, with backoff: wait a moment and try again, waiting longer each time.
N06
client_timeout · HTTP 0 · CLI exit code 8
kiste.run didn't answer in time. (code: N06)
When it happens. The command-line tool gave up waiting for an answer.
How to fix it. Try again in a moment.
In the CLI. Try again in a moment, or run kiste doctor.
Retry. Yes, with backoff: wait a moment and try again, waiting longer each time.
N07
ssh_connection_failed · HTTP 0 · CLI exit code 7
Couldn't open an SSH connection to {name}. (code: N07)
When it happens. The SSH connection through kiste.run could not be opened or closed unexpectedly.
How to fix it. Try again. If it keeps failing, restart the Kiste.
Retry. No. Retrying the same request gives the same answer.
N08
ssh_key_not_accepted · HTTP 0 · CLI exit code 3
{name} didn't accept this computer's key. (code: N08)
When it happens. The Kiste does not know this computer's SSH key yet.
How to fix it. Sign in on this computer so its key is added to your account.
In the CLI. Run kiste login on this computer so its key is added to your account.
Retry. No. Retrying the same request gives the same answer.