Skip to main content

The management console

The console is at https://<your-server>:5220/. This page is a map: what each part is for, and where in this manual it is covered.

Instances

PageCovered in
InstancesCreating an instance
Instance detailLifecycle
ConfigurationConfiguration and changes
TuningTuning
Git, RevisionsGit addons
CertificateCertificates
Backup configurationTargets
ChangesConfiguration and changes

Databases

PageCovered in
Databases, database detailManaging databases
Modules, module detailModules
GroupsModules

Server

PageCovered in
ServerConfiguration files
SMTPMail
Intrusion preventionFail2Ban
MaintenanceMaintenance
Images, Disk usageStatistics and disk
StatisticsStatistics and disk
Updates, Release notesUpdates
LicenceInstalling a licence
EnvironmentsEnvironments

Operations and account

PageCovered in
JobsJobs
LogsLogs
UsersUsers and roles
Account, Trust this deviceMFA and passkeys

Things worth knowing on day one

Nothing happens instantly. Every change you make is queued as a job and the page shows queued → running → completed. That is not slowness, it is the product refusing to claim success before the work is done. See Jobs.

The bell is the notification centre. Completed and failed jobs surface there, so you can start something long and go elsewhere.

Lists have a copy button. Tables can be copied as tab-separated values, which pastes straight into a spreadsheet.

What you can see depends on your role. Operators and Viewers are scoped to particular instances, and that scoping is enforced by the API rather than by hiding things in the browser. See Users and roles.

A padlock warning on first visit is expected. The console serves HTTPS with a self-signed certificate so that passkeys work at all. Accept it once, and reach the console by name rather than by address.