Give someone access to one website, not the whole server. This tour creates sites as a member, grants site-only SSH, and tries to reach another member's resources — which must be refused.
| Product version | build 81fce3de6 (Business bundle; every step above uses features that are in Free) |
|---|---|
| Date | 2026-11-03, 21:07–21:50 UTC |
| Environment | test lab: a master and five managed nodes (KVM and Proxmox VE test hosts); no production systems or customer data |
| How it was driven | as a user — member panel, WHMCS client area and SFTP. SSH and SQL were used only to check results. |
| Isolation check script | 72 checks passed, 0 failed |
| Cross-member access | refused in both directions for sites, files, site tasks, SSH grants, FTP, PHP pools and logs, backups, domains, website/WAF logs, reverse proxy and forwarding |
| Site SSH | a 24-hour grant could log in and stayed confined to its site; out-of-range durations were refused; after revoking, the live session was dropped in under 7 seconds |
| FTP password | shown once on create / regenerate; never returned again by lists or the API |
| Manual intervention | none in the steps above; steps that need an administrator’s step-up 2FA code (for example a member’s personal file manager) were not run in this pass |
| Known issue found | after regenerating an FTP password, the running FTP service keeps accepting the old one until it is restarted (tracked for the next release) |
Read more: Per-site SSH, FTP and isolation · Web hosting · Multi-user docs
The sandbox is invite-only and not open yet; there is no public live demo. Please do not send passwords, keys or customer data with a request.