doona
First sign-in
Demo
English
First sign-in

First sign-in

This page opens doona in a browser, creates the administrator account and checks that doona shows the running honk. honk must be running, as Service management leaves it.

Before you start

  • A computer or phone on the LAN, or the gateway itself. honk accepts the administrator setup only from loopback, private or link-local addresses.
  • The listen address from Minimal configuration, such as 192.168.1.1:9527.

1. Open doona

Open this address in the browser, with your address in place of 192.168.1.1:

http://192.168.1.1:9527/ui/

doona finds honk’s API at the same address and saves it as its backend. Because no administrator exists yet, it shows a page titled Create the administrator with the fields Username, Password and Confirm password. The page also has language, palette and theme controls.

2. Create the administrator

  1. Enter a Username: letters, digits, _, . and -, 1 to 64 characters.
  2. Enter a Password of 8 to 128 characters, and the same password under Confirm password.
  3. Select Create and sign in.

doona signs you in and opens the Activity page. honk keeps the account in its state database, /var/lib/honk/state/honk.db (/etc/honk/data/state/honk.db on OpenWrt). From now on the page is titled Sign in and asks for this username and password.

3. Check the overview

Select Overview in the side navigation. With honk running, it shows:

  • Running at the top of the page.
  • The Engine card: under Engine, honk and the version honk-core --version printed, such as honk debug.2026.9.30.native-api.5; under API, dae/honk-native v1 (draft); under Build, the honk commit and the build target you installed.
  • The Backend features card, listing what this honk provides, such as Connections, Logs and Configuration.

The bottom of the side navigation shows the same honk version. Traffic counters stay at 0 until traffic passes through honk.

Setup is complete. To route LAN devices, add nodes and rules, see Configuration and Features.

If it doesn’t work

You see Cause and fix
The browser cannot connect honk is not running, or the address differs from listen. Check step 3 of Service management and curl http://192.168.1.1:9527/api on the gateway. A firewall on the gateway can also block port 9527.
This honk build has no native API The installed honk-core lacks the native API. Install the build from the doona release; see honk version.
The backend accepts administrator setup only from loopback, private or link-local addresses. The browser reached honk from a public address. Open doona from a device on the LAN, or on the gateway itself.
The username or password is incorrect. Enter them again. To replace a forgotten administrator, stop honk, run sudo /usr/local/bin/honk-core admin reset (without sudo in a root shell; on OpenWrt, /usr/bin/honk-core --data-dir /etc/honk/data admin reset), then start honk; the setup page opens again.
Token required instead of the setup page api.dae sets secret instead of password_auth: true. Enter that secret as the token, or change api.dae as in Minimal configuration and restart honk.

For more, see Sign-in problems.

doona

doona documentation

English
doona documentationdoona is a static web UI for the native API that the daeuniverse engines share: honk today, dae once it implements the same contract. Requirements Install on Debian or UbuntuThis page installs doona from its .deb package and honk-core from the same doona release on Debian, Ubuntu and other APT-based systems. Install on Fedora or RHELThis page installs doona from its .rpm package and honk-core from the same doona release on Fedora, RHEL and other DNF-based systems. Install on Arch LinuxThis page installs doona from its .pkg.tar.zst package and honk-core from the same doona release on Arch Linux and other pacman-based systems. Install on GentooThis page installs doona with Portage from the ebuild in doona’s repository, and honk-core from the same doona release. Install on OpenWrtThis page installs doona and honk-core on OpenWrt 25.12 from the release archives. Install on other systemsThis page installs doona and honk-core from the release archives on a Linux system without a doona package, such as Alpine Linux. Installation detailsInstall honk, write its configuration, then install doona and start honk. Minimal configurationThis page writes the smallest honk configuration that starts honk and serves doona, then checks it by starting honk by hand. Service managementThis page runs honk as a systemd or OpenWrt procd service: it creates the service once, then lists the commands that start, stop, restart and reload honk and read its log. First sign-inThis page opens doona in a browser, creates the administrator account and checks that doona shows the running honk. Interface tourThis page shows where things are in doona after you sign in: the four navigation sections, the top bar, and the tabs, detail panels and action menus inside a page. Watching trafficThis page covers the Activity hub (Activity and System status) and the Monitor hub (Connections, Routing log, DNS, Logs and Events). Routing, nodes and rulesThis page covers the Routing hub: the Policies, Nodes and Rules pages. Config and settingsThis page covers the Configuration page, where you read, validate and apply honk's configuration files. Common tasksThis page collects short procedures for frequent changes to routing, traffic inspection and honk maintenance. ConfigurationThe configuration is two files. FeaturesFirst confirm that the gateway carries traffic. Troubleshooting DevelopmentRead CONTRIBUTING.md before opening a pull request.