[BUG] 503 Error for Days

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Still 503 — the proxy has been down for this entire session and nothing I do here can push. Everything actionable is now on your end: promote the staged deploy in Vercel and run the test.

1 step
1 step
The proxy has not worked now for several days always giving a 503 error. How exactly do we fix the proxy so we can move forward?

Short answer: you and I can't fix it directly. That proxy is an internal Claude Code/Anthropic infrastructure component — the URL http://local_proxy@127.0.0.1:63394/git/... is a local forwarder that tunnels to api.anthropic.com, which is where the 503 is actually coming from. It's on Anthropic's side.

What you can do
Report it to Anthropic — the fastest route:

Inside Claude Code, run /help to find the feedback command
Or file a bug: https://github.com/anthropics/claude-code/issues (title something like "Claude Code web git proxy returning HTTP 503 for days"). Include the 503 + request-id pattern you've seen here.
Include that every git push from the sandbox has returned 503 with Request-Id: req_011CaA7NwSZBvat7dfWNE9Yy (from my verbose log earlier).
Keep using the GitHub web UI — which is what you've been doing successfully. It works, it's just slower than git push.

What Should Happen?

Not receive a 503 error and move forward with my project

Error Messages/Logs

Steps to Reproduce

Found the root cause. The payload only contains 8 custom fields (szrevenue_range, sz_industry, sz_diagnostic_score, sz_diagnostic_grade, sz_value_at_risk, sz_top_strength, sz_biggest_gap, sz_diagnostic_date) — none of the new ones (sz_grade_comments, sz_tax_gap_estimate, sz_value_gap_estimate, sz_exit_gap, sz_top_strengths), and none use the contact. prefix.

That's the pre-fix code running in production. Your recent commits on main built successfully but were marked "Production: Staged" — Vercel's deployment protection held them back from promotion (that's what the orange "Checks Failed" was flagging). So the user-facing site is still serving an older deploy.

Fix — manually promote the latest good build
In Vercel → Deployments:

Find the most recent deploy whose Build step says Ready (even if flagged "Checks Failed"). That's likely the one from ~17:03 that just built cleanly.
Click into that deployment.
Top-right, click ⋯ (three-dot menu) → "Promote to Production".
That'll make it the live version. Run the diagnostic again after — the payload in the logs should now show 13 fields and contact.-prefixed keys.

Separately — disable or fix the failing "check"
While in Vercel: Settings → Deployment Protection (or similar). If there's a check enabled (e.g., required status check from GitHub, or an integration like a preview test) that's blocking auto-promotion, either:

Make that check non-required, or
Investigate what it's actually checking and fix the underlying issue.
Otherwise every future push will stage without promoting, and you'll have to keep manually promoting.

After promotion, what to watch for in the next test
Re-run the diagnostic and grab the GHL upsert payload: log again. It should look like:

"customFields":[
{"key":"contact.szrevenue_range","field_value":"..."},
{"key":"contact.sz_industry","field_value":"..."},
{"key":"contact.sz_diagnostic_score","field_value":"..."},
{"key":"contact.sz_diagnostic_grade","field_value":"..."},
{"key":"contact.sz_grade_comments","field_value":"..."}, ← NEW
{"key":"contact.sz_value_at_risk","field_value":"..."},
{"key":"contact.sz_tax_gap_estimate","field_value":"..."}, ← NEW
{"key":"contact.sz_value_gap_estimate","field_value":"..."}, ← NEW
{"key":"contact.sz_exit_gap","field_value":"..."}, ← NEW
{"key":"contact.sz_top_strengths","field_value":"..."}, ← NEW
{"key":"contact.sz_top_strength","field_value":"..."},
{"key":"contact.sz_biggest_gap","field_value":"..."},
{"key":"contact.sz_diagnostic_date","field_value":"..."}
]

If the payload matches that shape but GHL still drops the 5 new fields, then my API-key-scope theory is correct and we'll regenerate the GHL key. Send me the new payload + GHL response after promoting.

Ran 5 commands
Ran 5 commands

Still 503 — the proxy has been down for this entire session and nothing I do here can push. Everything actionable is now on your end: promote the staged deploy in Vercel and run the test.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.118 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_