I dug into the OpenCode Go 500s and I’m pretty sure people are collapsing 2 different failures into 1
I went deeper on this today because the Reddit threads were starting to blur together, and I had a feeling people were describing the same symptom but not the same cause.
After testing across multiple request shapes and multiple accounts, I’m pretty confident there are 2 separate problems getting lumped together:
1. Client fingerprint / header issue
If you hit OpenCode Go with a generic OpenAI-compatible client, you can trigger Cloudflare 1010 / access denied type failures.
So yes, there is a client-side layer here. Some requests are getting blocked before they even meaningfully reach the model backend.
2. Actual upstream/provider 500 issue
Once I adjusted the request shape to look like real OpenCode traffic, I could get some models to work normally.
But that’s the important part: some other models still returned 500 Internal Server Error on the same accounts.
That means the “just fix the headers” explanation is incomplete.
If headers were the whole story, then once the request fingerprint was corrected, everything should have recovered. That’s not what I saw.
Why this matters
Because right now a lot of people are probably talking past each other:
- one group is hitting the client/header/Cloudflare problem
- another group is hitting the real server-side 500 problem
- both groups report “OpenCode Go is broken”
- then everyone starts arguing over fixes that only solve one layer
What I don’t think it is
At this point I don’t think this is just:
- bad key
- bad account
- bad local setup
- random user misconfiguration
Not when you can make one class of models respond normally and another class keep throwing 500s under the same general conditions.
That points much more strongly to an upstream/provider routing issue inside OpenCode Go for certain model paths.