Error from provider (Console Go): Upstream request failed

Description

Good afternoon, the service on all Go models has started returning the error “Error from provider (Console Go): Upstream request failed.” It doesn’t matter which program is being used—whether it’s the CLI, the desktop app, or OpenChamber in VSCode.
The limits are within normal ranges: 40% weekly and 60% monthly.

Changing the API key did not help. The requests appear in the statistics and have even been processed.

Plugins

No response

OpenCode version

1.18.1

Steps to reproduce

Open news session
Send "hello world"
Retrive Error from provider (Console Go): Upstream request failed

Screenshot and/or share link

Version: 1.18.1 (latest)
Date: 2026-07-16T08:07:27.236Z
OS: macOS 25.5.0 (arm64)
Terminal: iTerm.app 3.6.11
Session ID: ses_09613b23dffeFwvXELe43GRNMk
Model: opencode-go/deepseek-v4-flash

This issue might be a duplicate of existing issues. Please check:

opencode-go (Console Go) provider returns 400/401/500 for subscribed models #37056: opencode-go (Console Go) provider returns 400/401/500 for subscribed models — same provider, same error message
OpenCode Go service (zen/go/v1) frequent intermittent outages — HTTP 000 / 503 / Cloudflare 524 #36889: OpenCode Go service (zen/go/v1) frequent intermittent outages — reports the same upstream failures (503/000) on the Console Go backend
All paid OpenCode Zen models fail with 'Upstream request failed' — free models work #36506: All paid OpenCode Zen models fail with 'Upstream request failed' — same error on a related backend

If your issue is the same as one of the above, consider adding a comment there instead.

I went to check if requests to OpenCode were being blocked—maybe they ended up on some blacklist and the DNS started blocking them. But no, everything is fine; even proxying requests to OpenCode through a random country didn't help. Still, all Go models return “Error from provider (Console Go): Upstream request failed.”

Same issue. The same model on Opencode Zen works however!

@gwynnbleiidd

HI @gwynnbleiidd, thanks for reporting. We can see the errors in our system. Is it possible that you overwrite the model parameter in your opencode config? We see the following provider error

Invalid top_p value, the valid range of top_p is (0, 1.0]

Thanks. For some reason, the values in all the agents had become zero; after changing top_p and temperature to null, it started working.

The comments contain the resolution. The issue was about "Upstream request failed" errors on Go models.

The comments contain the resolution. The issue was about "Upstream request failed" errors on Go models.

i dont find the solution, can you wrap up please?

It happens to me when sending a request contains Chinese leader's name or political language to Kimi models provided through OpenCode Go.

Happened today to me

same, happening to e also from last 12 hours. Error from provider (Console Go): Upstream request failed: [invalid_request_error] The request contains invalid parameters. Check the request body for any errors or inconsistencies.

happening to me too, with meta muse 1.3 free on opencode zen

Yeah for me too, right now

yeah, me too. even in go models, i think this is a global issue.

Haha seems like I'm not alone I'm also getting the same error.

Issue persists still.

I had same issue in one session. When I compress my session it has works again . maybe it will be a solution for others

I am also facing the same issue.

same bug...
Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller

After Opencode Desktop was updated.

ANY update ?

Does someone has a clue by which part of Opencode the message Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller gets created? Started opencode with --log-level DEBUG, but no hint about from where this message is coming from.

This is still happening on 1.18.27.

Still persists.

Same problem here, on Muse Spark 1.2 and 1.3

@goainwo0

@goainwo0 this detailed report about the situation is very highly appreciated! Thank you 👍🏼

Same issue here, with DeekSeek V4.1 Flash:

Internal error: Error from provider (Console Go): Upstream request failed: [insufficient_user_quota] You’re out of credits — this request needs $0.02. Add credits to keep going: https://www.orcarouter.ai/console/billing?ref=err_credit_gate#add-credits (request id: <redacted-id): {
“service”: “session”,
“errorName”: “APIError”
}

I'm very far from running out of credits:

No top_p value or other config has been changed. It was working up until 5 minutes ago, then suddenly stopped with the error in question.

Cross-linking a focused report for the same DeepSeek V4.1 Flash / OrcaRouter insufficient_user_quota route: #49936. Same symptom with a healthy OpenCode Go quota (rolling 8%, weekly 52%, monthly 26%); deepseek-v4-flash, deepseek-v4-pro, glm-5.3, and kimi-k3 all return 200 with the same key/session.

Update for the DeepSeek V4.1 Flash / OrcaRouter path tracked in #49936: the same request started returning 200 again after roughly an hour with no client-side changes (success response ID 00f43eb9-0605-4934-adc8-b703f9bffc95). This still looks like an intermittent upstream quota/routing failure; keeping #49936 open for a root-cause/failover fix.

For me, the error appeared after the /compress command

Navigation Menu

Repository navigation

Error from provider (Console Go): Upstream request failed #37231

Description

Plugins

OpenCode version

Steps to reproduce

Screenshot and/or share link

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Error from provider (Console Go): Upstream request failed #37231

Description

Description

Plugins

OpenCode version

Steps to reproduce

Screenshot and/or share link

Activity

github-actions commented on Jul 16, 2026

gwynnbleiidd commented on Jul 16, 2026

kaka-ruto commented on Jul 16, 2026

StarpTech commented on Jul 16, 2026

gwynnbleiidd commented on Jul 17, 2026

trywalker commented on Jul 24, 2026

daum3ns commented on Jul 29, 2026

waynezhao12 commented on Jul 29, 2026

VictorZakharov commented on Sep 11, 2026

ankur-paan commented on Sep 12, 2026

Project516 commented on Sep 13, 2026

timootten commented on Sep 13, 2026

ltdcorporation commented on Sep 13, 2026

MrAlaminH commented on Sep 13, 2026

nxck2005 commented on Sep 13, 2026

yougis commented on Sep 14, 2026

wadud75 commented on Sep 14, 2026

Eyefinitys commented on Sep 14, 2026

Atanub707 commented on Sep 15, 2026

tmeckel commented on Sep 15, 2026

fmcardoso commented on Sep 16, 2026

JackBasford commented on Sep 17, 2026

zonaro commented on Sep 18, 2026

tmeckel commented on Sep 18, 2026

hyuri commented on Sep 19, 2026

zfei2080 commented on Sep 19, 2026

zfei2080 commented on Sep 19, 2026

Ashu11-A commented on Sep 19, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions