Documentation
CyberPanel
CyberPanel is an open-source control panel for web hosting. Provibr talks to its API with the login of your main administrator and manages the websites on it: creating them, suspending and resuming them, moving them to another package, and removing them.
Switch API access on
On a fresh CyberPanel the API is switched off, and that holds for your main administrator too. You turn it on in the panel under Users, API Access, for the user admin. Nothing else is needed: Provibr signs in with the login you already have.
The main administrator has to be called admin
Part of the CyberPanel API refuses every name other than admin, and that is the part which lists the websites on the panel and reports how far a new one has come. Provibr needs both, so the account you fill in below is the one called admin.
What Provibr asks for
Four fields. The agent keeps them in its own vault on your host; Provibr cannot read them back.
- The address of the panel including the port, for example https://panel.example.com:8090. Leave the port out and Provibr fills in 8090. Plain http is refused: that port speaks TLS and nothing else.
- The name of the main administrator, which is admin.
- The password of that administrator.
- The SHA-256 fingerprint of the certificate, as long as the panel uses the self-signed one.
The certificate
Every fresh CyberPanel presents the same self-signed certificate, made out to www.example.com and signed by CyberPanel itself. A browser therefore calls it wrong rather than self-signed, and the chain never verifies. Fill in the fingerprint and the agent trusts that one certificate instead of switching verification off. You read it from any machine that can reach the panel:
openssl s_client -connect <host>:8090 </dev/null 2>/dev/null | \
openssl x509 -noout -fingerprint -sha256Put a certificate of your own on the hostname of the panel and the chain verifies by itself; leave the field empty then. That is the better choice there, because such a certificate is replaced now and again and a pinned one would have to be filled in here every time.
Packages
CyberPanel describes what a website may use in a package. Provibr reads that list and refers to a package by name; the packages themselves are made and changed in CyberPanel, not here.
A web hosting plan in Provibr points at one package on one integration. That is what your customer orders, and you set the price yourself.
What an order sends along
A website on CyberPanel is addressed by its domain, and that is its identity in Provibr as well. An order carries four things:
- The domain. It has to be free on the panel, and everything Provibr does with this server afterwards points at it.
- A contact address for the website.
- The package the website goes on.
- A password for the panel login that CyberPanel creates underneath the website.
Suspending and resuming
Both work straight away: the panel reports the new state and its own list shows it immediately. Provibr suspends a website when you ask for it, and when your capacity is exceeded.
Disk space and bandwidth
CyberPanel is the only control panel in Provibr without usage graphs, and that is not something the integration leaves out: the panel does not measure it. Bandwidth usage is calculated and then thrown away, and disk usage comes out of a cache that stayed empty on a new website, so the zero it reports cannot be told apart from nothing at all.
Websites that already exist
Websites made outside Provibr can be imported on the integration page: the agent lists what is on the panel, and you pick which of them should become a server in Provibr.
What this does not do
Provibr manages websites, not the panel: it does not install CyberPanel, does not update it and does not change server settings. There is no console, and DNS, mailboxes and databases stay untouched. CyberPanel can do all of that itself, and Provibr does not drive it.