Docs / Getting Started / First-time Setup

First-time Setup

Create your superadmin

  1. Open http://<server-ip>:8000 in a browser.
  2. You're redirected to the Setup page automatically — it only appears on first run, when no admin users exist yet.
  3. Enter a username and password for your superadmin account.
  4. Submit. You're logged in and taken to the Dashboard.

Setup is a one-time page

The setup page is only reachable while the database has zero admin users. After you create the first account it is permanently disabled — there is no public sign-up.

Connect FreeRADIUS

MonsterOps reads and writes the standard FreeRADIUS SQL schema: radcheck, radreply, radusergroup, radpostauth, radacct, radippool, and nas. It does not manage FreeRADIUS config files directly (except proxy.conf, and only when you use Realms).

  • FreeRADIUS on the same host — the installer configures the SQL module for you.
  • FreeRADIUS on a separate host — point its rlm_sql at the same PostgreSQL database MonsterOps uses. Once both sides share the database, users you create in MonsterOps authenticate immediately.

Add your first NAS

Nothing can authenticate until the device is a known RADIUS client. Go to NAS, add your access server's IP and shared secret, and make sure the same secret is set on the device.

Enable GeoIP (optional)

The Logs and Sessions views can show a flag + city per client IP:

  1. Go to Integrations → Data Sources → MaxMind GeoIP2.
  2. Create a free MaxMind account and download GeoLite2-City.mmdb.
  3. Upload it through the guided modal — MonsterOps validates the file and hot-reloads the reader without a restart.

Problems you may hit

Setup page won't appear / redirects to login

That means an admin user already exists. Log in with those credentials instead. If you've lost the only account, create a new admin from the CLI on the server.

  • Users created in MonsterOps don't authenticate — FreeRADIUS isn't pointed at the same database, or its SQL module isn't enabled. Check Logs and the FreeRADIUS log.
  • Can reach the login page but auth always rejects — confirm the device is registered under NAS with a matching shared secret.

Next: Upgrading.