# registry_unavailable

> The registry or disko-master could not be reached, or is temporarily unavailable.

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

The command exits with code 4.

- `disko publish` reports `registry_unavailable` when the registry cannot be
  reached, answers with a `5xx` status, or answers with a redirect, which
  `disko` never follows. Nothing was published, so no version was used up.
- `disko dev` reports it when the room it hosts cannot reach disko-master or
  the registry, for example to register its lease; the session stops. When
  the test room cannot be created in the first place, `disko dev` reports
  [api_unavailable](/errors/api_unavailable).

## Fix

- Check the network connection and run the command again.
- If you set `--registry`, `--api`, `DISKO_REGISTRY_URL`, `DISKO_API_URL` or
  `--profile local`, check that they point at running services. Without
  them, `disko` uses `https://registry.disko.ooo` and `https://api.disko.ooo`.
- If the service answered with a `5xx` status, wait and try again later.

## See also

- [CLI reference](/reference/cli)
- [Publish a release](/get-started/publish)