Read only: this is network configuration, not a panel setting, and a mistake here cuts the machine off entirely.
Routeswhere traffic leaves this machine
Destination
Through
Interface
Addresses
Address
Goes out through
Interface
Kind
A panel runs on every node and manages only its own machine.
Whatever it learns about the others, it only reads: if a peer is
unreachable, this panel keeps working.
Nodes
Node
Link
Version
Deployed
Components
Memory
Clock
Panel usersseparate from the Pulu database
Login
Role
Access
Last seen
These are accounts of the server itself, not of the panel.
Membership in sudo or docker is equivalent to root: docker
mounts the whole disk. Hand them out as carefully as the root password.
Host accounts of the machine
Login
Access
Shell
Rights
Which user runs which serviceread only
Service
Kind
User
Where it is set
The panel keeps the intent and rebuilds the nginx configuration from it. Editing the generated file by hand is pointless — the next save from the panel overwrites it.
Sites
Domain
Target
Certificate
Pulu routes
Running now
Server components
Component
State
Version
Ports
Needed for wildcard certificates: they can only be validated through DNS, so every renewal has to put a TXT record into the zone and take it out again. For ordinary names the panel manages without a provider.
DNS providers
Zone
Provider
A certificate is an object of its own, not a property of a domain. One pool for the whole machine — the same certificate can serve several services.
Unfinished orderswaiting for DNS records
Domains
Started
SSL certificatesone pool for the whole machine
Name
Kind
Primary domain
Alternative names
Valid until
Two different locks. The interface decides which socket the panel
binds to; an allowed name decides which Host it agrees to answer.
While no name is listed the panel answers on anything — that is the window to close.