Verified
Troubleshooting
Real error strings from sign-in, sign-up, deploys and API keys, matched to what fixes them.
Every entry below quotes the string Xuda actually returns, so you can match it against what you are looking at.
Signing in
| You see | What it means | What to do |
|---|---|---|
account not found | No account matches that email. | Check the email, or sign up instead. |
wrong password | The email exists, the password does not match. | Try again, or use Forgot your password?. |
User not found (on the forgot-password form) | No account matches the email you asked to reset. | Check the email, or sign up instead. |
| "Your session expired. Sign in again." | The session timed out, or an operator ended it. HTTP 408. | Sign in again. |
gtp_token doc not found / gtp_token expired | The session token behind a signed-in call is gone or stale. | Sign in again; the client normally redirects to /dashboard/login for you. |
| "Too many sign ups from this network. Please wait a while and try again." | The signup rate limit for your network tripped. See Limits and quotas. | Wait for the window to reset. |
No lockout on a wrong password
Xuda removed the failed-attempt counter and account lock that used to sit behind a wrong password. A wrong password is just a wrong password, there is no attempts-remaining countdown and no temporary lock to wait out.
Signing up
| You see | What it means | What to do |
|---|---|---|
| "Your password needs all four below, at least 8 characters, a number, an uppercase letter, and a special character." | The password checklist (8 characters, a number, an uppercase letter, a special character) is not fully met. | Meet all four before submitting; the Sign Up button stays disabled until you do. |
Missing email | The email field was empty. | Fill in an email address. |
Email malformed | The email failed format validation. | Provide a valid email address. |
| "We couldn't create your account. Please check your details and password, then try again." | The signup call came back with a field-level problem. | Recheck every field, including the password rules, and resubmit. |
| "Something went wrong creating your account. Please try again." | An unexpected error during account creation. | Retry. If it keeps happening, contact support. |
| "This app does not accept new sign ups. Ask the app administrator for an invitation." | You tried to join an app deployment whose signup is closed. | Ask the app's administrator for an invite instead. |
Deploy failures
| You see | What it means | What to do |
|---|---|---|
vps region not found | The region or datacenter id in a deploy request does not resolve. | Verify the region/datacenter id you are deploying to. |
| "xuda Farm is not available in <region> yet. Pick another region, or choose a DigitalOcean datacenter under more options." | You picked Latin America or Africa. Xuda Farm owns no locations there. | Pick North America, Europe or Asia-Pacific for a Farm server, or continue with an explicit DigitalOcean datacenter (not physically in that region). See Region. |
| "The shared server type is not available for a Full Stack VPS. Choose an optimized type (or a larger plan)." | The Shared size tier was picked for a Full Stack VPS, which needs more than that tier gives. | Choose an optimized size, or a larger plan. |
| HTTP 423, Site Locked | A build or deploy for this app is already in progress. | Wait for it to finish, then refresh. |
| HTTP 425, Site not ready | The deployment has not finished provisioning. | Wait, then refresh. |
| HTTP 503, Site Off | The app is turned off, or the account is suspended. | Turn the app back on, or resolve the account hold. |
API 401/403-style errors
| You see | What it means | What to do |
|---|---|---|
| HTTP 401, missing/invalid/expired token | No session, or an expired gtp_token/app token, on a method that needs one. | Sign in (dashboard) or send a valid api_key (API). See API key. |
| HTTP 403, Access Denied | Authenticated, but not authorized: a missing role, team membership, or plan entitlement. | Request access from the resource owner, or check your plan. |
unauthorized api_key for <method>: <reason> | The key you sent cannot call that method: it is not on a custom key's allowlist, the method is private: true, or the key itself failed validation. | Check the key's access mode and allowed methods; private methods stay out of reach of every key. See Clearance. |
{ "jsonrpc": "2.0", "error": { "code": -32000, "message": "Bad Request: No authorization found" } } | The MCP request carried no Authorization header at all. | Send the key as Authorization: Bearer <key>. See MCP. |
{ "jsonrpc": "2.0", "error": { "code": -32000, "message": "Bad Request: Invalid Api key" } } | The Authorization header was present but the key does not resolve to an active key document. | Check the key value, or mint a fresh one. See MCP. |
Key access
Creating an API key needs identity verification first, the same level 2 check Xuda asks for before handing out a phone number, a mailbox, or a portable IP.
| You see | What it means | What to do |
|---|---|---|
code: -412, error: "verification_required" | The account has not cleared the identity check API keys require. data carries required_level, level and missing_claims. | Complete the identity verification prompt, then create the key. |
| A method never appears as reachable even on a full-access key | The method carries private: true. This is absolute, no access mode overrides it. | Call it from a signed-in dashboard session instead. |
| A method you expect to call with a custom key is refused | Custom access is an explicit allowlist; a method added after the key was created is not included until you tick it. | Open the key in Account > Developers > Keys and add the method. |