Skip to content

Use a browser console for recovery

A console is a recovery path, not a reason to expose a public VNC port.

Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page

When a console helps

Use the connection section of your service when SSH or RDP is not reachable. A supported browser console can show boot errors, firewall lockouts, or the operating-system sign-in screen.

Keep the session private

Open it from your signed-in service page on a trusted device. Do not share console URLs, tokens, cookies, or screenshots containing credentials. Close the session when finished, especially on a shared computer.

Unavailable console

Console availability depends on infrastructure support and a secure endpoint. If the panel says no secure console is available, use SSH/RDP if possible or ask support for the service-specific recovery route. Do not replace HTTPS with HTTP, publish VNC to the internet, or use an unrelated VM's console.

Before changes

Read the boot message and preserve useful errors. Console access does not make reinstalling or changing disk partitions safe; both still require a verified backup and careful review.

Was this not enough?Include the service number, exact error, and time of the problem. Never send a password or private key.
Contact support