VirtConsole 3.2.3.4 is a patch release for both the management server and the hypervisor agent. It focuses on the platform as seen end to end through the API, and every item was measured on a real panel before it shipped.
Keys-only machines and reinstalls
A deploy or reinstall with SSH keys and no password keeps password login off and root locked. A password you choose is used as given instead of being replaced. A customer’s own ssh_pwauth, disable_root and root lock_passwd in the cloud-config always win, also on a password deploy. A reinstall builds a fresh cloud-init from the reinstall call itself rather than reusing the original deploy’s document, and the cloud-config limit of 65,536 characters is enforced and published in the API description.
Consoles
A console session now comes with a link your customer can open in a browser without any admin token: the session itself is the key, it works once, and it expires. Opening the WebSocket address by mistake no longer spends the session. A panel that does not know its own public address now says so, with a warning in the admin panel and a clear error from the console calls, instead of handing out console links that could never connect.
Webhooks, regions and metering
Instances now emit outbound webhook events (deployed, reinstalled, status changes, suspensions, deletions), signed and delivered within seconds. A region an administrator has switched off refuses new resources on every create path. Managed database and load balancer bandwidth is metered against the plan’s allowance.
Images and operations
Images show the publisher’s own version and build date, and every refreshed catalog image carries a clean machine identity and a working guest agent. Statistics shown for a machine no longer depend on its guest agent, and a guest agent that hangs no longer freezes the statistics of every other machine on the node. The task log in the admin panel reads as wrapped, syntax-coloured JSON.
This release needs the Slave agent 3.2.3.4 on every hypervisor for the cloud-init and statistics fixes. Update it from the panel’s Update agent action.
API changes
The admin API’s deploy and reinstall answers keep task_id (and the password, when one was generated) inside a data object in every case, instance notes are readable and writable on both APIs, several validation and state failures now answer 422, 409 or 503 instead of a generic error, and console sessions return a token-free console_url. Every change, with before and after examples, is listed at docs.virtconsole.com/api/changelog.
Thanks for building on VirtConsole. Questions or trouble along the way, reach us any time.