# Troubleshooting on-boarding of edge devices

Use these checks when an edge device cannot connect to MK.IO or complete registration.

## Prerequisites

- All edge devices require a [network interface configured as Control with an IP address](https://docs.mediakind.com/beam/quick-start#set-control-ip-address).
- [DNS addresses that can resolve external domain names](https://docs.mediakind.com/beam/system-admin/network/configure-nics#set-dns-addresses) such as `https://api.mk.io/`.
- To register and manage an edge device, it must be able to connect to `https://api.mk.io/`. This requires either:
  - A default gateway that can route to the internet, and any customer-managed firewall MUST allow egress TCP port 443 to `https://api.mk.io/`.
  - _Or_, configuration to use an [HTTP proxy](https://docs.mediakind.com/mkio/how-to/managing-edge-devices/on-board-fleet-devices/common-workflow#configure-an-http-proxy-optional) that can reach `https://api.mk.io/`.
- The device must have connected at least once to `https://app.mk.io/` before it can be registered.

## Cannot add device

When manually adding a device via the MK.IO UI, you may see an error similar to:

`1000.4500.1500.1300 - Device is not recognised. A device with this ID has never connected to MK.IO. Connect the device to MK.IO and try again.`

Check that the device network settings are correctly configured. See [Network Configuration](https://docs.mediakind.com/beam/system-admin/network/configure-nics).

## Connected field shows No in the device web UI

**Diagnose via the device’s local web UI:**

1. Open the device’s local web UI: `http://<Control-IP-Address>`.
2. Go to **Appliance** \> **Fleet**. After a few seconds, additional information appears.
3. Click %27%3e%3cpath%20d=%27m%20384,64%20q%200,26%20-19,45%20-19,19%20-45,19%20-26,0%20-45,-19%20-19,-19%20-19,-45%200,-26%2019,-45%2019,-19%2045,-19%2026,0%2045,19%2019,19%2019,45%20z%20m%20644,420%20-682,-682%20q%20-37,-37%20-90,-37%20-52,0%20-91,37%20L%2059,-90%20Q%2021,-54%2021,0%2021,53%2059,91%20L%20740,772%20Q%20779,674%20854.5,598.5%20930,523%201028,484%20z%20m%20634,435%20q%200,-39%20-23,-106%20Q%201592,679%201474.5,595.5%201357,512%201216,512%201031,512%20899.5,643.5%20768,775%20768,960%20q%200,185%20131.5,316.5%20131.5,131.5%20316.5,131.5%2058,0%20121.5,-16.5%2063.5,-16.5%20107.5,-46.5%2016,-11%2016,-28%200,-17%20-16,-28%20L%201152,1120%20V%20896%20l%20193,-107%20q%205,3%2079,48.5%2074,45.5%20135.5,81%2061.5,35.5%2070.5,35.5%2015,0%2023.5,-10%208.5,-10%208.5,-25%20z%27/%3e%3c/g%3e%3c/svg%3e) next to the **Connected: No** field to run diagnostics.
4. Resolve the network problem or configuration issue, then try again.

**Diagnose via the device’s local terminal:**

1. Log in to the device’s terminal.
2. Run the `control-wizard` command.
3. MK.IO API connectivity is tested and results display on screen.
4. Press **Q** to quit.

## Short code not accepted

Short codes are short-lived. You can also use the **Device ID**.