PufferPanel

PufferPanel authenticates with an OAuth2 client rather than an API key: a client ID and a client secret. Create one in the panel under your account, then paste both into Provibr along with the panel URL.

• Host: the full panel URL, for example http://panel.example.com:8080. Port 8080 is a fresh install's default; a panel behind a reverse proxy runs on 443, and there is no port Provibr can add without guessing.
• Client ID: the OAuth2 client identifier.
• Client secret: the secret that belongs to that client.
• TLS fingerprint (optional): only for an https:// host, to pin the certificate.

What the client may do follows the account it belongs to. Give it an administrator account so it can create and remove servers.

A fresh PufferPanel serves plain HTTP on port 8080. If the panel is behind TLS with a self-signed certificate, fill in its fingerprint; the agent then trusts that one certificate instead of turning verification off. Read it with:

openssl s_client -connect <host>:443 </dev/null 2>/dev/null | \
  openssl x509 -noout -fingerprint -sha256

Leave the field empty for a certificate from a public authority, and also when the panel is reachable over http only. A fingerprint next to an http address is refused, because there is no certificate to pin. A panel on plain http does work, but the client secret and everything the integration does then travel unencrypted.

PufferPanel builds a server from a community template, such as minecraft or factorio, rather than a numbered egg. Provibr lists the templates by name; the full definition, with its variables, is fetched when you order, so the plan's variable editor falls back to the template's defaults.

A game plan carries the template name and the resource limits. Ordering is plan-driven and there is no manual path: PufferPanel needs the full template definition inline, which is exactly what a catalogue does for you.

PufferPanel exposes its nodes but not their memory, disk or CPU. Provibr still reports the node, but with unknown capacity, because a game panel with no node at all cannot be ordered.

Create, start, stop, restart, kill, reinstall and delete all work. Deleting stops the server first, because the daemon refuses to remove a running container.

PufferPanel has no suspend of its own. When Provibr suspends a game server to enforce a licence limit, it stops the container and blocks access to it in the Provibr panel.

There is no console: PufferPanel's is poll-based rather than a live terminal. Usage graphs stop at CPU and memory, because that is all the panel's stats endpoint reports. Provibr does not manage the panel, its nodes, files, backups or users; a game server on the panel is the integration.