Security1
- Customer home folders are now private to their owner, readable only by the web server and the panel
Features8
- SSH access is now a package setting: customers on a package that allows SSH can log in with their keys (OpenSSH and PuTTY formats); others are refused cleanly
- Per-customer resource limits: set CPU, memory and process caps on a package; they apply to apps, workers, the Terminal, builds, SSH and cron jobs
- Website Pages: edit and preview the server address page, new site and subdomain placeholders, error pages, maintenance and suspended pages, all using your branding
- Node and Python apps: set the port your app listens on, or detect it with one click, so the proxy reaches the right process
- Subdomains can use a web template
- Real logos for app templates, the app installer and web templates
- Emails use the new design
- Live preview in the customer Error Pages editor
Fixes5
- SSH keys added in the customer panel were refused by the server (PuTTY: Server refused our key)
- Web templates lost their name and description, and saving one could fail with Failed to save template
- A Node site behind the Node.js Proxy template could serve the wrong process and return HTML instead of JSON
- Modals in the new design were off-centre
- Web server installs no longer fail because of a broken third-party apt source or an interrupted package install; the broken source is set aside and the admin is told
Infrastructure2
- Hiding the Powered by credit on website pages requires Pro or Developer
- Behaviour change: SSH keys a customer added themselves stop working unless their package allows SSH. Cron jobs now run inside the customer's resource limits