Skip to content

Nimbus Direct v1.3.0

Choose a tag to compare

View all tags
@eurosatofficial eurosatofficial released this 26 Jul 20:16
· 24 commits to main since this release
v1.3.0
0867a1e

Nimbus Direct v1.3.0 — Operations, Support & Public Demo

Nimbus Direct 1.3.0 expands the panel beyond individual VPS management with infrastructure monitoring, maintenance communication, customer support, improved security visibility, and a safe public demonstration mode.

This release continues to use only the official Proxmox VE API. It requires no software on Proxmox nodes and does not use Proxmox resource pools for customer assignments.

Highlights

Operations Center

Administrators now have a central overview of their Proxmox infrastructure, including:

  • Cluster and node health
  • CPU and memory pressure
  • Available and unavailable nodes
  • Storage capacity and utilization
  • Enabled storage paths such as local, local-zfs, and local-lvm
  • Automatically detected operational incidents
  • Incident acknowledgement and resolution
  • Last-known-good information during temporary Proxmox API failures

Storage entries unavailable or disabled on a particular node are no longer displayed as usable storage paths.

Maintenance System

Administrators can now create and publish scheduled maintenance windows.

  • Define maintenance title, description, schedule, and affected resources
  • Automatically determine affected customers from direct assignments
  • Notify affected customers by email
  • Preserve the original recipient list after publication
  • Keep maintenance information isolated between customers

Customer Support Center

Nimbus Direct now includes a complete customer-scoped support ticket system.

Customers can:

  • Create support tickets
  • View their own ticket history
  • Reply to open tickets
  • Follow ticket status and administrator responses

Administrators can:

  • View and manage all tickets
  • Assign tickets
  • Change status and priority
  • Send customer-visible replies
  • Add private internal notes

Customers can never access tickets belonging to another customer.

Secure Account Invitations and Recovery

Customer onboarding and account recovery have been improved with:

  • Single-use email invitation links
  • Pending accounts until the invitation is accepted
  • Secure password creation by the invited user
  • Expiring and hashed invitation tokens
  • Single-use password recovery links
  • Automatic session revocation after password recovery
  • Correct customer and user names in invitation emails

Existing two-factor authentication remains enabled after a password reset.

Security Monitoring

The Security Center now provides more complete authentication visibility.

  • Failed login attempts are recorded as audit events
  • Security email alerts can notify administrators
  • Authentication events include useful request information
  • Existing 2FA status and active-session management remain available
  • Security information is stored centrally and displayed in the administrator panel

Public Read-Only Demo Mode

Nimbus Direct can now be operated as a safe public demo.

Enable it with:

ALLOW_DEMO_DATA=true
DEMO_READ_ONLY=true

When public demo mode is active:

  • Visitors can explore the interface using simulated data
  • All infrastructure and account mutations are blocked by the backend
  • Buttons for unavailable actions are clearly disabled
  • Real Proxmox clusters, SMTP credentials, and MFA configuration are rejected at startup
  • Background synchronization and notification jobs are disabled
  • Shared demo sessions are limited
  • Sensitive internal addresses are hidden

Turning both options off restores normal panel operation.

Improved Guest Address Discovery

VM and LXC addresses are now more reliable throughout the interface.

  • Addresses are discovered automatically on the Instances page
  • Opening the Network tab is no longer required
  • Discovered addresses survive dashboard refreshes
  • Address information refreshes automatically in the background
  • The last successful result is retained during temporary API failures
  • A clear “Discovering…” state is shown while information is loading

A QEMU guest may still show “Unavailable” when the Proxmox guest agent is not installed or running and no address can be obtained through the official API.

Additional Fixes

  • Fixed the Security Center occasionally rendering undefined
  • Fixed invitation acceptance errors in some browsers
  • Corrected invitation email greeting and account-owner wording
  • Improved primary address detection for QEMU and LXC guests
  • Improved storage discovery across multiple nodes
  • Filtered disabled and node-incompatible storage entries
  • Improved handling of temporary Proxmox API failures
  • Preserved locally managed assignments throughout synchronization
  • Added additional authorization and tenant-isolation tests

Security

All new operations continue to be validated by the backend against Nimbus Direct’s local role, customer, assignment, and permission database.

Customers never receive:

  • Proxmox credentials
  • API tokens
  • Direct Proxmox access
  • Raw internal API responses
  • Access to another customer’s resources or tickets

Upgrade Instructions

  1. Back up your Nimbus Direct Docker data volume and configuration.
  2. Extract nimbus-direct-1.3.0.zip over the existing application files.
  3. Keep your existing .env, data, and secrets directories.
  4. Rebuild the panel using both Compose files:
docker compose \
  -f compose.yaml \
  -f compose.internal.yaml \
  up -d --build --force-recreate panel

Database migrations are applied automatically during startup.

The included compose.yaml exposes only:

ports:
  - "4173:4173"

Installations using an internal Proxmox address or private CA must continue loading compose.internal.yaml.

Release Asset

nimbus-direct-1.3.0.zip

Assets 2
Loading