Get started

Set up the panel

Panel admins run Nebla from the admin area. After the first admin account is created, the admin area opens on Get Nebla ready:

  1. Connect Proxmox. Done when a location has an online node.
  2. Turn on OS images. Done when an image is ready somewhere.
  3. Add server types. Done when one type exists.
  4. Add an IP pool. Done when a pool has a free address.

Once all four are done, anyone in a project can create servers and the checklist leaves the menu. The rest of this page covers each part of the admin area.

Locations and nodes

A location is a Proxmox cluster or standalone node. Choose Connect a location, give it a name such as home or rack-2, and either Get setup command for the one-line setup or Connect manually to enter the Proxmox URL, API token, certificate fingerprint and storages yourself.

A location's page shows its nodes with their status, cores and memory.

  • Sync nodes reads the cluster's nodes again, for example after you add one.
  • Turn a node's Enabled switch off to keep new servers off it.
  • Disk storage override puts one node's server disks on a different storage.
  • Edit connection changes the URL, token or storages. Re-run setup runs the setup command again, for example after a certificate renewal.
  • The page warns when the datacenter firewall is off, and when volumes need one more permission on a storage, with the command to run.

Nebla places new servers only on enabled, online nodes. A location can't be deleted while it still has servers, IP pools, images or server types tied to it.

OS images

OS images shows a grid of images against locations. Choose Enable in a cell and Nebla downloads the official cloud image to the location's nodes through the Proxmox API and builds a template from it. That takes a few minutes. The catalog has:

FamilyImages
Debiandebian-12, debian-13
Ubuntuubuntu-24.04, ubuntu-26.04
Rocky Linuxrocky-9, rocky-10
AlmaLinuxalma-9, alma-10
Fedorafedora-45

rocky-10 and alma-10 run with the x86-64-v3 CPU type, so the hosts' CPUs must support it.

Built-in images need Proxmox VE 8.4 or later, an import storage on the location, and outbound HTTPS from the nodes. A cell says why when it can't be enabled. Refresh rebuilds a ready image from the newest download, and the old template keeps working until the new one replaces it. Disable stops new servers from using the image in that location and removes its templates.

Your own images

Under Your own images, choose Add image to register a cloud-init template you built yourself. This works on every supported Proxmox version. Give it a name, an OS flavor and version, and one template per location: the VMID, plus the node that holds it, or Shared storage when the template sits on storage every node can reach. The Proxmox setup reference shows how to build one.

Deleting an image leaves its template in Proxmox alone.

Server types

A server type is a size that users pick: cores, memory and disk. Choose New server type, then either pick a size under Start from a template or fill in the fields yourself: a name such as small-2, the cores, memory in GB and disk in GB. Under Available in you can limit a type to some locations.

TemplateCoresMemoryDisk
Nano10.5 GB10 GB
Small11 GB25 GB
Medium24 GB50 GB
Large48 GB100 GB
XL816 GB200 GB
XXL1632 GB400 GB

A template only fills in the form, so you can change any value before you save. Templates whose name is already taken are marked Already added.

Tick Deprecated to hide a type from new servers. Servers that already use it keep running.

Keep each template's disk no larger than your smallest server type, because Nebla grows the cloned disk to the type's size and disks never shrink.

IP pools

An IP pool hands out public addresses in one location. Choose New IP pool and fill in:

FieldExample
FamilyIPv4 or IPv6
Bridgevmbr0
VLAN tagOptional, 1 to 4094
CIDR203.0.113.0/24
Gateway203.0.113.1
Range start and end203.0.113.20 to 203.0.113.200
DNS servers1.1.1.1, 9.9.9.9

Each server gets the lowest free address from the location's pools and keeps it until it's deleted. Cloud-init sets it as a static address. Ranges in one location can't overlap, and a pool can't be deleted while addresses from it are in use. The list shows how many addresses each pool has in use.

Every server's network card runs the Proxmox firewall with IP and MAC filtering, so a server can't take an address it wasn't given.

Users

Users lists every account with its two-factor and passkey status. New user creates an account with a name, email, password and an optional Panel admin tick. Nebla sends no email from here, so give people their password yourself.

From a user's menu you can edit them, reset their password, turn off two-factor login, remove their passkeys or delete them. The panel always keeps at least one admin, and you can't run these actions on your own account.

Sign-up

Settings has one switch: Let anyone create an account. It's off by default, and then people join only through an invite from a project or an account you create. With it on, the login page links to a sign-up page.

Projects and quotas

Projects lists every project with its owner, servers and members. A project's page shows its usage against its quota, its members and its activity.

Quotas limit servers, vCPU, memory, disk, IPs, volumes and total volume size. Leave a limit empty or set it to 0 for no limit. Lowering a limit below current use removes nothing, it only refuses new servers.

Projects a non-admin creates start with PANEL_DEFAULT_QUOTA, and projects an admin creates start unlimited. See Install.

Activity

The admin Activity page lists every action in every project, newest first, filtered by project and status. Admins see the technical detail of failed actions here.