Managing SolusVM console credentials and VNC access

Identify your installed platform and the console method provided for the VPS. Do not assume that a persistent VNC Password tab from an old tutorial exists in SolusVM 2. Keep the panel account secure because it can grant access to powerful VPS controls.

1. Open the correct VPS and test its supported browser console from the trusted HTTPS panel. Authenticate to the guest separately when its login screen appears.
2. If your service explicitly exposes a separate VNC password-change control, enter a unique value that meets the displayed requirements and save it.
3. Follow the panel instructions for applying that change, including an orderly restart or stop/start only if required. Keep an existing recovery route until the new connection has been tested.
4. Open a fresh console connection and confirm it works. Update any authorized external client that uses the separate credential and close obsolete sessions.
5. For a current installation without a VNC password control, manage panel password, two-factor authentication and project/role permissions instead, and ask support about revoking an exposed console connection.

Confirm you can reach the intended screen and then log in to the guest. Changing a VNC credential does not change the Linux root or Windows Administrator password.

If access fails, check panel permissions, server state and the console error before changing unrelated passwords. Never expose a raw VNC port or revive a Java browser plugin to bypass the supported method. Treat console links and temporary connection details as sensitive and share only the error text with support.

• Using the SolusVM browser console for VPS recovery
• Changing your SolusVM control-panel password
• Managing SolusVM login alerts and account security
• Resetting a VPS root or Administrator password in SolusVM

• SolusVM: Customers
• SolusVM: User Access Control
• SolusVM: Enabling Two Factor Authentication