# UNKNOWN_CHAIN

> For the complete documentation index, see [llms.txt](https://ensforge.com/llms.txt).

What UNKNOWN_CHAIN means, why ConfigError throws it, what to show users and how to fix it in ensforge. Also covers retry safety and the actions that throw it.

Source: https://ensforge.com/docs/reference/errors/UNKNOWN_CHAIN

<ErrorMeta errorClass="ConfigError" href="/docs/reference/errors/config-error" package="@ensforge/sdk" />

## What happened [#what-happened]

ensforge has no ENS deployment for this chain.

## What to show users [#what-to-show-users]

| Title | Message | Action |
| --- | --- | --- |
| Network not supported | ENS is not available on this network. | Switch to Ethereum mainnet or Sepolia. |

## How to fix [#how-to-fix]

Pass `deployment` to Ensforge.create, e.g. Deployments.define(\{ name, chainId, v2 \}).

## Retry safety [#retry-safety]

Retrying the same call fails the same way until the cause is fixed (`retryable: false`).

## Actions that throw it [#actions-that-throw-it]

No action names this code in its documented errors.

Any action can fail with `ConfigError`: it is part of `Errors.CommonError`.

## Catch it [#catch-it]

`Errors.hasCode("UNKNOWN_CHAIN")` narrows to this error. See [Handle errors](/docs/sdk/handle-errors).