You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Zen: gpt-5.6-luna / gpt-5.6-terra fail with "Error from provider (Console): Upstream request failed" #39831
Zen: gpt-5.6-luna / gpt-5.6-terra fail with "Error from provider (Console): Upstream request failed"
Description
Using Zen (opencode provider), gpt-5.6-luna and gpt-5.6-terra consistently fail with HTTP 403 Error from provider (Console): Upstream request failed, while gpt-5.4-nano, gemini-3.6-flash and claude-sonnet-5 work fine with the same API key. Both models are listed in GET https://opencode.ai/zen/v1/models, so access appears enabled. The error string matches #39293 (gemini-3.6-flash), suggesting the "Console" upstream is failing for these models.
I am also experiencing the same issue. When making an API request using the curl command, the server returns an invalid_prompt error indicating an upstream request failure.
To Reproduce
Send a request to the API using curl.
Target the gpt-5.6-luna model.
Expected behavior
The request should be processed successfully and return a valid response.
Reproduced from a Hong Kong production server via the documented Zen API endpoint. Additional comparison details from #40162:
gpt-5.6-luna: HTTP 403
gpt-5.6-terra: HTTP 403
gpt-5.4-mini: HTTP 200 with the same Zen API key and host
claude-haiku-4-5: HTTP 200 with the same Zen API key and host
Both IPv4 and IPv6 reproduce the GPT-5.6 failure
The more specific upstream error is:
Error from provider (Console): Upstream request failed: [unsupported_country_region_territory] Country, region, or territory not supported
This model-level comparison suggests the Zen credential and general connectivity are valid, and the failure is specific to the current GPT-5.6 upstream route rather than all Zen traffic from the host.
Independent reproduction from a Windows 11 Go subscriber:
OpenCode Desktop 1.18.15: opencode-go/gpt-5.6-luna fails on a normal prompt with Upstream request failed: [403] This model is not available in your region.
OpenCode CLI 1.18.15: the same model and prompt reproduce the same 403, which rules out the Desktop UI layer.
Direct connectivity and an explicit local HTTP proxy both reproduce the error; changing the client egress does not change the result.
Grok works from the same Go subscription/workspace, so authentication and general Go connectivity are valid.
A separate Desktop local-backend CORS issue was fixed locally; the Luna 403 persisted and also reproduces in the CLI.
This is consistent with a server-side upstream routing or forwarded geographic-header issue, rather than a local installation or proxy configuration problem. It also appears relevant to the still-open PR #40180.
Could a maintainer confirm:
whether this is an expected Go model availability restriction for affected accounts/regions;
Activity
github-actions commentedon Jul 31, 2026
This issue might be a duplicate of existing issues. Please check:
ltceu6o5fu commentedon Jul 31, 2026
I am also experiencing the same issue. When making an API request using the curl command, the server returns an invalid_prompt error indicating an upstream request failure.
To Reproduce
Send a request to the API using curl.
Target the gpt-5.6-luna model.
Expected behavior
The request should be processed successfully and return a valid response.
Actual behavior
The request(https://opencode.ai/zen/go/v1/responses) fails and returns the following JSON error message:
{"model":"gpt-5.6-luna","error":{"code":"invalid_prompt","message":"Error from provider (Console Go): Upstream request failed"}}
xxxxchaos commentedon Aug 2, 2026
Reproduced from a Hong Kong production server via the documented Zen API endpoint. Additional comparison details from #40162:
gpt-5.6-luna: HTTP 403gpt-5.6-terra: HTTP 403gpt-5.4-mini: HTTP 200 with the same Zen API key and hostclaude-haiku-4-5: HTTP 200 with the same Zen API key and hostThe more specific upstream error is:
This model-level comparison suggests the Zen credential and general connectivity are valid, and the failure is specific to the current GPT-5.6 upstream route rather than all Zen traffic from the host.
1138069580qq-create commentedon Aug 7, 2026
Independent reproduction from a Windows 11 Go subscriber:
opencode-go/gpt-5.6-lunafails on a normal prompt withUpstream request failed: [403] This model is not available in your region.This is consistent with a server-side upstream routing or forwarded geographic-header issue, rather than a local installation or proxy configuration problem. It also appears relevant to the still-open PR #40180.
Could a maintainer confirm:
FractalMind commentedon Aug 11, 2026