Browser SSH and files: prepare your cloud server
Browser tools reduce the need to switch applications, but they still connect to services inside your server. Prepare those services and credentials first, then choose the access method that fits the work. Availability depends on the server, deployment and your permissions.
Updated
01Choose between VNC, SSH and files
Use the remote VNC console to inspect the server screen or troubleshoot a guest network or SSH configuration. Use browser SSH for command-line work when the guest SSH service is ready. Use Files for supported file operations through SFTP. These tools do not install SSH, enable root login or add authorized keys for you.
02Check the server before connecting
Confirm that the server is running and you can access the intended resource. For SSH, check the guest SSH service and its port. Files also requires an SFTP subsystem. Keep a working system password or an OpenSSH private key, with its passphrase when required. Use an account with the permissions needed for your task.
03Verify the server identity
Open the selected server in Console and choose SSH or Files where available. Review the identity check before entering guest credentials. Where automatic verification is unavailable, compare the displayed fingerprint through a trusted connection such as VNC. A different or unexpected key needs investigation; do not treat it as a routine connection error.
04Make a small first check
After connecting, confirm the server identity and current directory before changing files or running commands. Start with a non-sensitive test file for file operations. Before replacing application configuration, keep the original and arrange a suitable recovery point. Use the least privileged account that can do the work.
05Recover access deliberately
If SSH or SFTP is unavailable, use VNC where possible to inspect the guest service, port and configuration. If your resource or action is missing, check organization permissions. For unresolved errors, contact support with the server reference, time and a safe description; do not include passwords, private keys or terminal secrets.
