qlingen.docs

Managing servers

Every server page gives you the full picture of one machine: status, IPs, services, firewall, SSL, backups, metrics and an activity log of everything Qlingen ran on it.

The lifecycle

A server moves through three states on its way up:

  • Provisioning — the instance is being created at your cloud provider.
  • Installing — the PBX stack is compiling and configuring (the long step: 8–18 minutes).
  • Online — SSH is up, services are running, calls can flow.

If anything fails, the status turns to Error and the activity log holds the full installer output, so you can see exactly which step broke before retrying or destroying the server.

Public and private IPs

Both addresses are captured from the provider during provisioning and shown on the server page. The public IP is what SIP phones and the web UI reach; the private IP is useful when you pair the PBX with other machines (a database, an SBC) inside the same provider network. Both are also handed to the installer, so the PBX is configured with real addresses instead of guessing.

Deploys and rollbacks

Deploy pulls the latest PBX application release onto the server and migrates it; Rollback returns to the previous release if a deploy misbehaves. Both run detached on the server and report into the activity log — closing your browser doesn't interrupt them.

SSH access

Qlingen manages the machine with its own keypair, but it's your server: add your personal public key from the server page (Add SSH key) and log in as root whenever you like.

Day-two operations

  • Services — restart FreeSWITCH, nginx, PostgreSQL or Redis individually.
  • Firewall — manage allowed ports and sources without touching nftables by hand.
  • SSL — issue and renew Let's Encrypt certificates for your PBX domain.
  • Backups — schedule recurring backups and watch their run history.
  • Cron — manage scheduled jobs on the machine.
  • Metrics & logs — CPU, memory, disk and the installer/application logs.

Destroying a server

Destroying removes the instance from your cloud provider — and with it the machine's bill. This is the only operation that touches a running PBX, and only you can trigger it.