Post-Installation

The installer finished and printed a green summary. Before you hand the dashboard to your team, take five minutes to confirm every service is healthy, that call data is flowing in, and that you know where everything lives on disk. This page walks through that checklist and your first few configuration steps.

Open the dashboard

The final screen of the installer shows everything you need to log in:

✓ Installation complete

Dashboard: https://192.168.1.100:8443
Username:  admin
Password:  aB3xYz9wQ1mK

Astervis is exposed on a single HTTPS port — 8443 — at https://<server>:8443, where <server> is your server's IP or the domain you chose during install. Every other service binds to 127.0.0.1 and is never reachable from outside the host.

Log in with the admin username and the generated password. Save that password in your password manager now — the installer does not store it in plain text anywhere, and resetting it later takes a few extra steps (covered below).

Verify services

From the server shell, ask the installer for a health report:

sudo astervis-installer status

It runs docker compose ps against /opt/astervis and prints a per-service table with a roll-up line at the bottom:

Astervis Status — /opt/astervis
────────────────────────────────────────────────────────────
SERVICE         CONTAINER               STATUS        HEALTH
────────────────────────────────────────────────────────────
timescaledb     astervis-timescaledb    Up 6m         healthy
redis           astervis-redis          Up 6m         healthy
migrate         astervis-migrate        Exited (0)    —
app             astervis-app            Up 6m         healthy
nextjs          astervis-nextjs         Up 6m         healthy
queue           astervis-queue          Up 6m         —
litcdc          astervis-litcdc         Up 6m         running
replication     astervis-replication    Up 6m         —
nginx           astervis-nginx          Up 6m         healthy
────────────────────────────────────────────────────────────
Services: 8/8 running  ·  migrate: completed (one-shot)

If any service is restarting or unhealthy, jump to viewing logs to see why, and check the Troubleshooting guide — most first-run issues are host networking quirks that the installer's logs pinpoint immediately.

What each service does

Astervis runs as a small set of Docker containers, all orchestrated by Docker Compose and managed through the installer. Here's what each one is responsible for:

View logs

When you need to see what a service is doing, use the installer's logs command.

sudo astervis-installer logs --follow

The full installation log — invaluable when something failed during setup — is written under the install directory and its path is printed at install time. If you ever open a support ticket, this single file contains the per-container diagnostics the team needs.

First steps

With the dashboard open and services healthy, here's the recommended order to get a useful first view of your call center.

Directory structure

Everything Astervis writes lives under /opt/astervis. Knowing this layout makes backups, log digging, and the occasional manual edit straightforward.

Reset the admin password

Lost the generated admin password? You can set a new one directly in the database. Connect to the TimescaleDB container with psql, then update the user's password hash.

docker exec -it astervis-timescaledb psql -U astervis -d astervis

UPDATE "user"
SET password = crypt('NewStrongPass1', gen_salt('bf'))
WHERE email = 'admin@example.com';

Next: Troubleshooting — common first-run issues and the one-command fixes the installer applies for them.