Certificates and VPN
This page covers two networking pages in the admin panel:
- SSL Queue — every HTTPS certificate on the platform, and the requests users make to delete or reissue one
- VPN Interfaces — extra private networks that chosen teams can put their labs on
SSL Queue
Admin Panel → Platform → SSL Queue (/admin/ssl), headed "SSL Manager".
Certificates are issued automatically when a user publishes a domain; nothing here is needed for that. This page is for the exceptions: a certificate that is stuck, expired, orphaned, or that a user has asked to be removed or reissued from their own HTTPS page. See HTTPS for the user's side.
How a request flows
Nothing is deleted until someone clicks Apply Approved.
Tabs
| Tab | What it is for |
|---|---|
| All Certificates | Every certificate. Search by domain, alternative name or owner; filter by status (valid, expiring soon, expired, renewal failing), by issuer, or Orphaned only. |
| Residue Cleanup | Expired certificates that still carry stale domains. Queue all sends them all for deletion (with confirmation). |
| Pending Review | Users' requests, with their reason and verification state. Tick rows, then Approve Selected or Reject Selected (with confirmation). |
| Approved | Deletions waiting to be applied, and the Apply Approved button |
| History | Past requests and who reviewed them |
Badges in All Certificates mark extra names on a certificate, protected and orphaned certificates, a pending deletion, and the last error. Details shows the full certificate.
Queue Deletion on any certificate sends it straight to Approved, skipping review, because you are the reviewer. The confirmation warns that deleting a valid certificate forces it to be reissued.
Applying approved deletions
- Open the Approved tab and check the list.
- Click Apply Approved.
- Read the confirmation and confirm.
Applying deletions restarts the platform's web proxy once. For a few seconds every lab and service on the platform is unreachable over HTTPS. A backup is taken first. Apply in a quiet period, and batch deletions so you apply once rather than several times.
While a batch runs, a banner shows and the button is disabled. When it finishes, a result banner shows how many were applied and skipped, the backup taken and how long the interruption lasted.
The requesting user is not notified when you approve or reject. Tell them if they are waiting on you.

VPN Interfaces
Admin Panel → Platform → VPN Interfaces (/admin/vpn)
Every user's devices connect to the platform's default VPN network. This page lets you add extra WireGuard networks and give them to chosen teams, so the people building labs in those teams can put their labs on a separate network. How users connect devices is covered in Devices.
Creating an interface
Creating an interface only makes a record. Nothing changes on the VPN server until you provision it.
- Fill in Display name and, optionally, the interface name (leave blank to pick the next free one).
- Choose the Node.
- Enter the address range. It must not overlap any existing range.
- Enter a Listen port. It must be free and different from the default network's port.
- Enter the endpoint host and port that devices will connect to.
- Click Create record.
Managing interfaces
The table shows each interface's name, address range, port, endpoint, node, status, peers and teams. Refresh reloads it. The default network is read-only.
| Action | What it does | Confirmation |
|---|---|---|
| Provision | Brings the interface live on the VPN server, without a restart | Yes |
| Teams | Chooses which teams may use it | — |
| Edit | Changes Display name, endpoint, node and Available. The address range, port and keys are fixed once provisioned. | — |
| Deprovision | Takes the interface down and deletes its address pool. The record stays. Refused while any device still uses it. | Yes |
| Delete | Removes the record and revokes every team's access. Only possible once deprovisioned and unused. Cannot be undone. | Yes |
If the platform's VPN provisioning is not set up yet, records still save and you can provision them later.
VPN interface actions are not recorded in the audit log.
Next
- Access control — who has access to which interface
- Labs and instances
- Platform settings