Bind and manage

Binding connects a Box to your OneDux account. Do it once after installing, and again after a reflash or a factory reset.

Bind

Make sure the Box’s WAN port has internet access.
From a computer on the Box’s LAN, open a terminal and run:
Terminal window
```
ssh root@192.168.1.1
```

Update the OneDux components:

apk update && apk upgrade onebox-agent onebox-core

Start the bind:
Terminal window
```
onebox-agent bind
```
It checks the clock, then prints a link and a code.
Open the link on any device, sign in to your OneDux account, and approve the request.
Within about a minute, the Box appears on console.onedux.com/box as Online. If it doesn’t, run /etc/init.d/onebox-agent restart.

What you see in the console

Field	Meaning
Online / Offline	Whether the Box is connected to OneDux right now
Heartbeat late	The Box is connected but has stopped reporting. Usually it recovers on its own.
Status unknown	We couldn’t check just now. This doesn’t mean the Box is offline.
DDNS	The Box’s own name, `<device-id>.ddns.onedux.net`. It’s ready about 5 minutes after binding and follows your public IP.
City	Optional. Choose it to show the Box on your resource map.

Update

OneDux components: apk update && apk upgrade onebox-agent onebox-core. Your settings and binding are kept.
Firmware: download the new image from the console and flash it with Keep settings checked. The binding is kept, but the OneDux components go back to the versions in the image, so run the command above again afterwards.

Unbind

In the console, open the device card and click Unbind this device. Its credentials are revoked right away and its DDNS name is released. To use the Box again, bind it again; it gets a new device ID.