Support
Troubleshooting
Resolve sign-in, SSH key, quote, balance and instance-state problems in the local workflow.
4 min read · UpdatedI cannot sign in
Use the username you registered, not an email address. Usernames are case-insensitive. If you have forgotten the password, use one unused recovery code on the recovery page. The reset invalidates previous browser sessions; sign in again with the new password.
A 401 response after using an API key can mean the key was revoked. Create another key from an authenticated account session.
Recover your accountMy deposit did not change the balance
Creating a sandbox quote is not a deposit. In the local Wallet, use Simulate confirmation before it expires. If it has expired, create a new quote and confirm that one.
Refresh the wallet and check Deposits and Billing. Retrying an already confirmed quote must not increase the balance again. The dashboard reads persisted account data, not a browser-only balance.
Deployment is unavailable or rejected
Check that you are signed in, have an active saved SSH key, and have enough balance for the GPU allocation plus options. A malformed-key error usually means the public key line is incomplete or a private key was pasted.
If a direct API request reports an image mismatch, choose an image supporting the GPU vendor. If it reports a price change, request a fresh instance quote. A capacity conflict means the modeled allocation pool is full; try another region or configuration.
Start or renewal fails
Refresh the instance list after a state conflict. Start works only for a stopped node within its paid term. An expired node needs renewal first. A released instance cannot be restarted; configure a new node instead.
There is no SSH hostname in the local demo because no remote hardware has been allocated. The running label tests the account and billing lifecycle, not a network connection.