Claude connector guide: what to do about Bad Gateway errors (#323)
* Claude connector guide: what to do about Bad Gateway errors
- CI / Typecheck and bundlesuccess
- CI / Unit tests (1/2)success
- CI / Unit tests (2/2)success
- Deploy / Deploy to Cloudflaresuccess
- Deploy / Main's current tipsuccess
- End-to-end / End-to-end (agent reviews, tasks, Today)success
- End-to-end / End-to-end (git, PRs, Actions)success
- End-to-end / End-to-end (large pushes)success
- End-to-end / End-to-end (passkeys, registry, email)success
- End-to-end / End-to-end (real histories)success
- End-to-end / End-to-end (runner Docker)success
- End-to-end / End-to-end (security)success
- GitHub community setup / Labels, welcome discussion and roadmap issuesuccess
- Live test / Containers, registry, sandboxes, webhooks, schedules, LFS and pull requestssuccess
- Mirror to GitHub / Push main to the GitHub mirrorsuccess
1 file changed+1−0
modifiedapps/diffinery/docs/connect/claude.md+1−0View file
| @@ -58,5 +58,6 @@ | ||
| 58 | 58 | | Claude says a tool needs the write scope | You connected with **Read** access. Disconnect Claude on Diffinery and connect again with **Write**. | |
| 59 | 59 | | A tool fails with "agents may not push to protected or default branches" | Claude acts as an agent, which works on branches and opens pull requests. Ask it to open a pull request instead. | |
| 60 | 60 | | Claude asks you to connect again | The connection lapsed after 30 days without use, or it was disconnected. Choose **Connect** again. | |
| 61 | +| Some tool calls fail with "Error POSTing to endpoint: Bad Gateway" | Look for those calls among your instance's requests, such as `POST /mcp` in the Cloudflare zone's analytics for your Diffinery domain. If they aren't there, they failed on Claude's side before reaching Diffinery, and asking Claude to try again usually gets through. If they are there, check your Worker's logs for errors. | | |
| 61 | 62 | |
| 62 | 63 | More detail on the consent page and what the tokens can do: [How sign-in works](/docs/connect/how-sign-in-works). |