When a server order fails

A failed order means strackt asked your connected cloud provider to create a new server and the request didn't go through. This is almost always something on the provider's side — an account limit, a billing issue, or a region or size that's temporarily unavailable — not a problem with strackt or with a server you already run. Your other servers and applications are unaffected.

If the provider did create a server before the order stopped, strackt keeps track of it rather than abandoning it, so you're never left paying for a server you can't see. It also never deletes it automatically — that's your call.

What to do

1. Check your cloud account. Sign in to your provider and look for the usual causes: you've hit the account's limit on how many servers you can run, a payment or billing problem, or the region or size you picked being out of stock right now.
2. For Vultr authorized-IP errors, update the API token. In the Vultr Customer Portal, open Account → API and check the token's Authorized IPs. Add the IP shown in the failed order, or reconnect the cloud account with a token that is allowed from the current Strackt workspace and can create SSH keys and instances.
3. Confirm the connection still works. In strackt, open Settings → Cloud accounts and use Verify on the account you ordered with. If verification fails, your provider credentials may have expired or been revoked — reconnect the account and try again.
4. Retry the order. Once the underlying cause is cleared, order again. If a server was partially created, strackt picks up where it left off rather than ordering a second one.
5. Or connect a server you already have. If you'd rather not wait on the provider, you can connect an existing server instead.

If orders keep failing and your cloud account looks healthy, reach out and we'll look into it with you.