First connection
Find your server and make your first SSH connection after provisioning.
Common symptoms
New server, first login, no server yet, SSH address, username, Console
What to check
- Check Orders for payment and provisioning progress. Once a server appears, check its status in Servers or server details. Follow displayed failure or recovery instructions instead of placing another paid order.
- Open the server's connection section. Confirm its assigned address, username and SSH port, then copy the SSH command. Check that your own network can reach its IPv4 or IPv6 address.
- Use the matching private key locally if you selected a public key. Confirm any installation result for an existing server. If SSH fails, check the exact error and use Console to inspect the guest.
Common questions
My order is paid, but no server is listed. What should I check?
Open the order first: a paid, provisioning or failed order can exist before the VM is created. Read its current progress or failure instructions and send that order reference to support if it remains unresolved.
The SSH command is correct, but the connection fails. What next?
Confirm the server is running, the address family is reachable from your network and the username matches the guest. Use the SSH errors guide to distinguish timeout, refused and authentication failures.
Open the relevant page
Before contacting support
Include the server or order name, failure time with timezone, exact sanitized SSH error and whether Console works. Never attach passwords, private keys or sign-in codes.
Keep secrets out of support requests · Remove passwords, private keys, access tokens, TOTP codes, backup codes and full payment details from screenshots and logs. Share the server or order name, time with timezone and exact sanitized error.
Official reference documentation
This opens an editable ticket draft. Nothing is sent automatically.