Connection and data recovery
Diagnose access first and review available backup restore points carefully.
Common symptoms
Cannot boot, Console error, recover files, backup missing, restore point, restore failed, reinstall, lost data
What to check
- Check the server's power state, pending operation and maintenance notices. When the original result is unresolved, follow the displayed recovery options instead of repeating lifecycle actions.
- Use Console when network access fails. Inspect networking, firewall, disk space and authentication. If an SSH key is missing, review the supported key installation flow before considering destructive recovery.
- If backups are enabled and available, select a successful restore point and read the action preview. Restoring overwrites newer guest data; reinstalling erases the OS disk. Save recoverable data before confirming either action.
Common questions
Why are there no backup restore points?
Backups depend on whether the feature is available and enabled and whether a backup completed successfully. The platform has no separate snapshot management entry; use the successful restore points in the server’s backup section.
Will restore or reinstall preserve my newest files?
A restore returns data to the selected point and can overwrite later changes. Reinstalling erases the OS disk. Review the target and preview, and copy any recoverable current data elsewhere before confirming.
Open the relevant page
Before contacting support
Include the server name, failure time with timezone, Console result, latest operation and available restore point details. Sanitize logs; never send passwords, private keys or recovery 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.
This opens an editable ticket draft. Nothing is sent automatically.