Skip to content

Server Info

Server Info is the admin dashboard for Engine runtime health. Use it to inspect service state, resources, public edge certificates, live operators, WireGuard, Aegis, release channels, worker state, timezone, and Ansible concurrency.

Borealis Server Overview
Server Overview summarizes Engine runtime state, services, access, resources, WireGuard, and Aegis status.

Read Overview

  1. Open Admin Settings > Server Info.
  2. Start with summary cards.
  3. Review runtime, service, resource, access, and security rows.
  4. Check public certificate health before blaming browser or agent trust.
  5. Check WireGuard state before troubleshooting shell, desktop, SSH, or WinRM.

Run Service Actions

Server Info can queue supported Engine service actions through the job scheduler. These are the same targeted operations as Engine.sh --service ....

Use service actions for focused restart, rebuild, reload, or WireGuard reconcile work. Use full Engine deploy when more than one component changed.

Tune Runtime Settings

Admins can adjust:

  • Engine timezone.
  • Scheduled Ansible per-job concurrency.
  • Scheduled Ansible global concurrency.
  • Agent release channel targets.

Warning

Service actions affect live Engine components. Prefer targeted actions only after identifying affected service.

Detailed Codex Breakdown

API endpoints

  • GET /api/server/overview - dashboard snapshot.
  • GET /api/server/time - server clock.
  • GET /api/server/timezones - timezone options.
  • POST /api/server/timezone - change host timezone.
  • GET /api/server/workers - active/recent worker state.
  • GET /api/server/ansible-runner-settings - read Ansible runner limits.
  • PUT /api/server/ansible-runner-settings - update Ansible runner limits.
  • POST /api/server/services/<service_key>/action - queue container service action.
  • POST /api/server/services/<service_key>/restart - queue systemd restart path.
  • POST /api/server/wireguard/recover - recover WireGuard listener.

Source map

  • Server API: Data/Engine/Containers/api-backend/data/services/API/server/info.py
  • Log API: Data/Engine/Containers/api-backend/data/services/API/server/log_management.py
  • Server Info UI: Data/Engine/Containers/webui-frontend/data/web-interface/src/Admin/Server_Info.jsx
  • Service actions: Data/Engine/Containers/api-backend/data/services/job_scheduler/

Runtime behavior

  • Container mode reads Docker state through docker-proxy and job-scheduler snapshots.
  • Service actions queue work items so API request can return before service changes interrupt runtime.
  • Server Info is informational first; raw log inspection belongs in Engine Log Management.