First run & sign-in
Open the URL the installer printed (HTTPS on port 443). Your browser will warn about the self-signed certificate on first visit. That’s expected. In Chrome or Edge click Advanced → Proceed to … (unsafe); in Firefox, Advanced → Accept the Risk and Continue; in Safari, Show Details → visit this website.
That exception is stored per browser profile, and browsers drop it from time to
time. After a profile reset or a long gap, the warning simply comes back and you
click through once more. If that is disruptive (a shared browser, a kiosk, or
anything automated that drives the UI), give the controller a certificate your
browser already trusts with --tls-cert / --tls-key, or terminate TLS at a
proxy in front of it. See the CLI reference.
1. Set the admin password (required)
On a fresh install the first screen is Set an admin password. This creates the administrator account for the web UI and API.
- Username defaults to
admin(you can change it). - Password must be at least 8 characters.
This step is mandatory: it’s the minimum needed to secure the console. If you
ever forget the password, reset it from the host with
asternodis auth set-password (see the CLI reference).
2. Onboarding wizard (optional)
Right after you set the password, Asternodis shows a one-time optional setup screen. Everything here can also be changed later, so skip it if you’d rather dive straight in.
- Site name: a friendly name for this site, shown to paired recovery sites
(e.g.
HQ-Primary). Defaults to the host’s name.
Set the web console URL (the address other sites use to deep-link back to this console) afterwards, in Settings.
You can also jump straight to setting up your first DR Site Pair from here, or choose Skip for now. The wizard only appears once.
Next steps
With the admin account in place, Asternodis is ready to use. Continue to: