Skip to main content
When something fails in the dashboard, you see a toast like:
Could not launch — Stripe is not configured on this deployment.
This page maps toast text to root cause. For the raw API error codes, see API errors.

Authentication

ToastCauseFix
Code is incorrect or expiredOTP wrong / older than 10 minutesClick Resend code
Too many attempts. Request a new code5 wrong code guessesNew code arrives in your inbox
Sign-in was cancelled or failedOAuth flow interruptedRetry from /login
We couldn’t read a verified email from that accountOAuth returned no verified emailUse a different sign-in option

Billing

ToastCauseFix
Your available balance is below the 1-hour reserveWallet too low for the picked GPUTop up
Stripe is not configured on this deploymentServer’s STRIPE_SECRET_KEY is emptyContact your admin
Card declinedStripe rejectedTry a different card; check expiry
Top-up failed. Try againNetwork blip during Checkout returnRetry

Rentals

ToastCauseFix
No provider available for this configAll upstreams are out of stock for this specWait 30s, try a different region, or pick a different family
Provision failed: <provider error>Provider-side allocation errorWe refunded automatically; try again
This rental is already in a terminal stateYou clicked Stop twiceNo action needed

SSH keys

ToastCauseFix
Keys must be at least RSA 2048 or Ed25519Pasted a weak keyssh-keygen -t ed25519 and retry
This public key is already on your accountSame fingerprint already savedNo action needed
Couldn’t parse that as a public keyPasted private key by mistake, or garbled the lineRe-copy ~/.ssh/id_ed25519.pub

Network / transient

ToastCauseFix
Network error, try againBrowser couldn’t reach the serverCheck connection; retry
Too many requestsRate-limitedSlow down; wait for Retry-After
All systems run normalStatus indicator, not an error
MaintenancePlanned downtime windowCheck status.gpuoutlet.ai for ETA

Reporting

If a toast doesn’t match anything above and you’ve retried twice, screenshot it and email help@gpuoutlet.ai with:
  • The toast text
  • What you were doing
  • Approximate time (UTC)
We can correlate to the server logs via the timestamp.