Web console reference
Getting in
Two addresses, the same console: the LAN address given during installation, and https://192.168.77.1/ on the service port, which works whatever the LAN is doing. Sessions expire after 30 minutes of inactivity and there is no “remember me”.
Five failed sign-ins from one address earn a fifteen-minute lockout for that address. The service port is exempt, deliberately — being locked out of a unit you are standing next to helps nobody.
Page map
| Console page | Shows | Changes | Minimum role |
|---|---|---|---|
| Overview | Device count, last collection pass, open alerts, queue depth, disk | Nothing | Viewer |
| Devices | Inventory: address, model, serial, profile match, last reading | Labels, location, profile, exclusion | Operator |
| Devices › Detail | One device: counters, supplies, history, alert log | Per-device thresholds and offsets | Operator |
| Discovery | Ranges, schedule, last scan result | Ranges, credentials, schedule | Administrator |
| Meters | Readings by day and month, flags | Schedule, reset acceptance | Operator |
| Supplies | Levels, estimates, what is due | Thresholds, hidden supplies | Operator |
| Release | Pools, held jobs, released history | Pools, limits, user list | Administrator |
| Alerts | Open and closed alerts, rules, quiet hours | Rules, recipients, suppression | Operator |
| Exports | Scheduled and past exports | Schedules, formats, recipients | Administrator |
| System › Network | Interfaces, DNS, NTP, current offset | Addressing, DNS, NTP | Administrator |
| System › Users | Console accounts and roles | Accounts, roles, passwords | Administrator |
| System › Backup | Backup history and destinations | Create, restore, schedule | Administrator |
| System › Software | Version, update source, history | Update, rollback | Administrator |
| System › Diagnostics | Live log, service status, self-test | Bundle collection, service restart | Administrator |
Roles
| Role | Can | Cannot |
|---|---|---|
| Viewer | Read every page except System | Change anything, see held job names |
| Operator | Day-to-day: labels, thresholds, acknowledging alerts, running a scan | Touch networking, users, software or release pools |
| Administrator | Everything on the unit | Read the content of a held job — nobody can |
| Service | Everything, plus shell access and diagnostic bundles | — |
Settings that interrupt collection
Most changes take effect immediately. These five restart a service, which means a gap of under a minute in collection and, for two of them, a broken print at exactly the wrong moment.
| Change | Effect | Severity |
|---|---|---|
| LAN addressing | Console and queue drop; every workstation pointing at the old address fails | disruptive |
| Release enable / disable | Queue service restarts; a job printing at that second is lost | disruptive |
| SNMP credential change | Collection restarts; one pass may be missed | minor gap |
| Time zone | Day boundaries move; today’s report may double-count an hour | minor gap |
| Software update | Everything stops for 3–6 minutes | disruptive |
Certificates
A new unit serves a self-signed certificate for its own address, valid for five years. That is adequate for a box reached by three people, and it is what most sites leave in place.
Where the site would rather not train people to click through a warning, install its own certificate for the unit’s DNS name under System › Network › Certificate. Requirements are ordinary: PEM, the full chain, a key without a passphrase, and a subject alternative name that matches the name people actually type. Replacing the certificate restarts the console only — collection and the release queue keep running.