Drıftstack docs
Docs

Cloud key on a self-hosted server (or vice-versa) never works

You might be here because: “a key from the cloud dashboard won’t work here” · “the key must be created in your own server’s dashboard” · “Authentication failed (401)” · “my key works on the website but not in the app” · “switched from cloud to my own server and now nothing signs in” · “self-hosted key on cloud” · “This server does not support secure browser sign-in” · “do I need a different key for self-hosted” · “wrong server”

Short answer

An API key only works on the server it was created on: a cloud key is refused by a self-hosted server and a self-hosted key by cloud. The desktop app is the same for both; the Cloud / Self-hosted choice in the setup wizard is the only switch. Create the key on the server the app points at — or, on cloud, skip keys and use Sign in with browser.

Check first

  • Which mode is the app in? Settings shows the server address: Cloud, or a Self-hosted address you pasted.
  • Where did the key come from? A self-hosted key is created in your own server’s dashboard, the same way as on cloud.
  • On cloud, prefer Sign in with browser: it stores the right credential, with nothing to copy.

Likely causes and fixes

  1. Self-hosted mode, cloud key pasted. The wizard says “This API key wasn’t accepted. For a self-hosted server the key must be created in your own server’s dashboard — a key from … won’t work here.” Fix: open your own server’s dashboard, create a key there, and paste that one.
  2. Cloud mode, self-hosted key pasted. The wizard says “This API key wasn’t accepted. Double-check it, or create a new one at app.driftstack.io/api-keys”. Fix: use Sign in with browser, or create a key in the cloud dashboard.
  3. You moved the app between deployments. Sign out (in Settings, the Connected panel; or the sidebar; or ⌘ Shift L) removes this deployment’s credential from the computer without revoking it; the wizard reappears — pick the other mode and sign in or paste the matching key.
  4. Browser sign-in refused on your own server. “This server does not support secure browser sign-in. Update the server and desktop app together, or paste an API key.” means the server is older than the app. “The server’s sign-in page address wasn’t one this app expects, so it wasn’t opened.” means the address in Settings is not what the server reports — check it, or paste a key.
  5. Refused later, elsewhere in the app. “Your sign-in or API key was not accepted. Check Settings and try again.” is the same refusal after setup; Settings re-checks the key with the same guidance.

If it still fails

Press Talk to a person in this chat (or open Help) and include: cloud or self-hosted, the server address (self-hosted only), where the key was created, and the app version. Never send the key itself. On a self-hosted server, Help has no composer — write to [email protected].