Provisioning and unfinished operations
Find progress and failure details before repeating an order or server action.
Common symptoms
Paid but no VM, provisioning stuck, creating server, task failed, operation pending, retry, start or reinstall unfinished
What to check
- Open the relevant order to check payment, provisioning or failure status. If the VM exists, open Servers or server details for its current power state and operation progress.
- Read the latest operation message and any displayed recovery or retry instructions. Check maintenance, then refresh the same order or server rather than issuing repeated actions.
- If progress remains unresolved or the page asks for support, open a ticket from the relevant order or server. Describe the original action and latest visible state before attempting another operation.
Common questions
Why is my paid order visible before the server exists?
Payment and provisioning are separate stages. The order can be paid, provisioning or failed before a VM is created. Its detail page is the place to check progress and report the original order.
Should I repeat a start, reinstall or paid order when progress stops?
Check the existing operation and follow its displayed recovery instructions first. Repeating a lifecycle action or purchasing again can complicate recovery while the original result is unresolved.
Open the relevant page
Before contacting support
Include the order or server name, original action, start time with timezone, latest status and sanitized failure message. Never send credentials, tokens or verification 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.