📚 Browse docs

CLI basics

The web UI covers day-to-day work, but the asternodis binary is also a full CLI, handy for headless setup, automation, and recovery. Run asternodis help for the full list.

Running the daemon

asternodis serve [--listen ADDR]

serve runs the daemon and the web UI together (the single-binary model). Common flags:

FlagDefaultPurpose
--listen:8443Web UI / API address (HTTPS). The installer binds :443 in production.
--peer-listen:8444Peer-link (mTLS) address.
--peer-advertise(auto)host:port peers use to reach this instance. Defaults to the detected LAN IP + the peer-listen port.
--web-advertise(derived)This site’s web-console base URL, shared with peers.
--tlstrueServe HTTPS with a self-signed cert. Use --tls=false behind a TLS-terminating proxy.
--tls-cert / --tls-key(none)Supply your own certificate (e.g. your PKI or Let’s Encrypt).

Global: the data directory

--data-dir PATH     # env ASTERNODIS_DATA_DIR; default /var/lib/asternodis when installed, else ~/.asternodis

All Asternodis state (the controller database and keys) lives here. The systemd service installed by install.sh runs with --data-dir /var/lib/asternodis.

With neither the flag nor ASTERNODIS_DATA_DIR set, a command uses the installed store /var/lib/asternodis whenever /var/lib/asternodis/asternodis.db exists, so on an installed host the CLI works on the same database as the running service. Otherwise it falls back to ~/.asternodis. The flag wins over the environment variable, and both win over the default. The installed store is readable only by root, so run CLI commands as root there: a non-root user cannot see it and falls back to their own ~/.asternodis. Point every command at the same data dir.

Version

asternodis version

See CLI tasks for the quality-of-life commands: resetting the admin password, backup/restore, licensing, managing remotes and pairs, running DR operations, verifying a release and checking the audit log from the shell.