Upstream request failed: Invalid credential #57106

Activity

1. opencode-agent commented on Oct 19, 2026

   

   opencode-agentBot

   on Oct 19, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report and the screenshot! Version 1.19.x is OpenCode v1, which now only gets critical fixes. Every model failing on a fresh server could count as critical, but first we need to work out whether the gateway is rejecting the key itself or the server is sending the wrong credential. Could you share:

   1. The exact model ID you picked (e.g. opencode/...) for both the paid and the free test.
   2. How you added the API key: through the web UI's provider/connect dialog, an OPENCODE_API_KEY environment variable on the container, or a mounted auth/config file? Was the key created in the same Zen workspace you added credit to? (Please don't paste the key.)
   3. If you remove the stored key (or start a fresh container without one), do the free models work?
   4. Does the same key work outside Docker, e.g. with a local opencode install, or with v2 (@opencode/cli, 2.x)?
   5. Any related lines from the container logs (docker logs <container>) from when you send the message, with secrets redacted.

   You can reply here with the details, or edit the issue. If you edit it, please also leave a comment saying you've updated it so we know you're done.

   These issues look related, ordered from most to least likely. None of them clearly matches your setup:

   • all models "Error: Upstream request failed: Invalid credential" #54833: same error on v2. That cause (a gateway endpoint change) is reported to have been fixed on the service side on 2026-10-14, before you opened this issue. Its baseURL workaround is now reported to break the free tier, so please don't add it.
   • 1.18 CLI: fresh 'opencode run' fails 'Invalid credential'; 'auth login opencode' fails 'fetch() URL is invalid' #50593: v1 1.18, fresh starts fail with Invalid credential and opencode auth login opencode is broken.
   • providers: stale wellknown API-key wiring in the shared service sends an empty key after auth login/logout #54645: a stale or empty API key is still sent after login/logout, so the upstream rejects requests.
   • Upstream request failed: Invalid credential #56646: same error message. Details are still pending there.
2. opencode-agent

   added

   triaging

   on Oct 19, 2026
3. m477r1x commented on Oct 19, 2026

   

   m477r1x

   on Oct 19, 2026

   Author

   More actions

   i added the key using the web UIs provider connect box. the model Id i tested for paid model was claude sonnet 5.5 and the free model was big pickle. free models appear to work in a fresh container without ad API key added.

   the same key does not work outside of docker, the same error is produced when connecting an opencode account in an iterm2 session with the api key.

   i don't think docker logs are useful since the issue exist outside of docker as well.
4. neriousy commented on Oct 20, 2026

   

   neriousy

   on Oct 20, 2026

   Member

   More actions

   Thanks for testing both inside and outside Docker, that narrows it down a lot. Invalid credential means the gateway doesn't recognize the key itself, so it isn't the container: usually the key was revoked, copied incompletely, or belongs to a workspace (or service account) that was deleted.

   The quickest fix is to create a fresh key: in the Console open your account menu → Account → Personal API keys → Add API key, pick the workspace you added credit to, and copy it straight away (it's only shown once). Then reconnect with that key.

   If a brand-new key from that workspace still gives Invalid credential, please email help@anoma.ly with your account email and workspace name so we can look at the account. Closing this here since it's key-specific rather than an OpenCode bug.
5. neriousy

   closed this as not plannedon Oct 20, 2026
6. opencode-agent commented on Oct 22, 2026

   

   opencode-agentBot

   on Oct 22, 2026 – with OpenCode Agent

   Contributor

   More actions

   We're closing this for now because we haven't heard back with the details we asked for: the exact model ID, how the API key was added, whether free models work without the stored key, whether the same key works outside Docker or on v2, and the container logs. Without them we can't tell whether the gateway is rejecting the key itself or the 1.19.x (v1) server is sending the wrong credential. v1 now only gets critical fixes.

   If you still see Upstream request failed: Invalid credential, please reply here with those details and we can reopen this. If it also happens on v2 (@opencode/cli, 2.x), please mention that too. You can also follow #54833 and #50593, which report the same error. Thanks for taking the time to report it!
7. opencodejr

   reopened this on Nov 3, 2026