Appearance
Tasks
Some VPS operations take longer than a page request. Where supported by your installed release, PteroCloud shows a task so you can follow progress and see whether the operation completed or needs attention.
Following an Operation
Submit an action once, then check the progress or task details shown for that VPS. Available views and controls depend on your release and account permissions.
- Confirm that the task refers to the correct VPS and action.
- Read its latest progress message and any displayed error.
- Wait for an in-progress operation to finish before requesting a conflicting action.
- Check the VPS status and access after the operation reports completion.
Closing or refreshing the browser does not necessarily cancel the operation. Avoid submitting the same request again simply because the page stopped updating.
Understanding Progress
A waiting operation may be queued or waiting for the hosting system. Large disk operations can take time even when the displayed progress does not change. There is no single expected duration for every workload.
An error does not prove that nothing changed. Before retrying, confirm whether the original VPS or requested change already exists. Use retry or cancel controls only if your release offers them and the host's instructions permit it.
For VPS Users
If progress stops or an action fails, contact your hosting provider with:
- The VPS name or reference shown in your account.
- The action requested and the time it started, including your time zone.
- The task reference and exact error message, if displayed.
- A reviewed screenshot and a short description of what still works.
Do not send passwords, private SSH keys, API tokens or console session links. Do not create a replacement VPS or delete the original as a troubleshooting shortcut.
For Panel Administrators
Check the task alongside the current VPS status before making changes. Use the Setup Assistant or Support Center where available to review service issues. Confirm that the required queue workers, scheduler, Redis and provider are healthy.
Follow Troubleshooting and the diagnostic CLI. Do not delete provider resources, edit task records or force an operation to appear complete without understanding its outcome. Preserve backups and seek support when the actual VPS state is unclear.