When a command on your server fails

A failed command means strackt tried to run an operation on your server — a provisioning step, a health check, or a management task — and it didn't complete. Your server and any running applications are unaffected. The failed step is recorded in the operation so you can see exactly where it stopped.

What to do

1. Open the operation and read what it reports. The failure message tells you which step didn't finish. That's usually enough to tell whether the problem is with the server's state or a transient connection issue.
2. Check that your server is reachable. Go to the server page and confirm it shows as online. If the server appears offline or unreachable, address that first — strackt can't run commands on a server it can't connect to.
3. Retry the operation. Most command failures are transient — a brief network interruption or the server being busy at that moment. A second attempt often succeeds without any other change on your part.
4. Check your server's resources if the problem persists. A server that is consistently out of disk space, memory, or CPU can cause commands to fail or time out. Your server's monitoring page shows current resource usage.

When the outcome is unknown

Sometimes strackt loses contact with your server while a command is running, or the command runs longer than strackt waits for it. Then strackt can't tell whether the command finished, and the operation says the outcome is unknown rather than that it failed.

1. Check the result first. For a deploy or rollback, open your site and see which version is live. For anything else, check whether the change took effect.
2. Run it again only if it didn't take effect. If the new version isn't live, deploy again.

If the failure keeps happening after retries and your server looks healthy, reach out and we'll dig into the operation details with you.