# api_unavailable

> disko-master could not be reached, or cannot create test rooms right now.

| | |
| --- | --- |
| Kind | `disko` command error |
| `disko` exit code | 4 (unavailable) |

`disko dev` reports `api_unavailable` when its request to create a test room
cannot reach disko-master, times out after 30 seconds, answers with a
redirect (which `disko` never follows), or answers `404` or a `5xx` status.
Nothing is hosted, and the command exits with code 4.

## Fix

- Check the network connection and run `disko dev` again.
- If you set `--api`, `DISKO_API_URL` or `--profile local`, check that it
  points at a running disko-master. Without them, `disko` uses
  `https://api.disko.ooo`.
- If disko-master answered with a `5xx` status, wait and try again later.

When the room itself loses disko-master while `disko dev` runs, the session
stops with [registry_unavailable](/errors/registry_unavailable) instead.

## See also

- [Test rooms (disko dev)](/get-started/test-rooms)
- [CLI reference](/reference/cli)