502 on every target
Likely causes
- - Endpoint temporarily unhealthy
- - Wrong port maps to a dead service
Verified remedy
Re-copy endpoint values, test with curl -x, and swap to a spare endpoint if the failure persists.
Proxy troubleshooting
Ranked causes, ordered diagnostics, and a verified remedy for 502 bad gateway from proxy - ending with a final connection check.
Quick answer
Fix: 502 Bad Gateway from the proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Ranked causes, ordered diagnostics, and a verified remedy for 502 bad gateway from proxy - ending with a final connection check.
Fix: 502 Bad Gateway from the proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Likely causes
Verified remedy
Re-copy endpoint values, test with curl -x, and swap to a spare endpoint if the failure persists.
Likely causes
Verified remedy
Reduce concurrency and increase client timeout; dedicated endpoints fail predictably under load you control.
The original action completes and the exit IP matches the endpoint.
If curl through the endpoint also fails, the problem is endpoint-level: check dashboard status or swap to a spare endpoint.
Facts last reviewed 2026-09-01.
A 502 from the proxy means the proxy could not reach or finish the upstream request; separate proxy health from target health with a direct curl test.
Work the diagnosis tree top to bottom: confirm endpoint values, test with curl through the endpoint, apply the remedy, then run the final connection check.
Recurring proxy failures usually trace to an unstable mapping - rotating endpoints or shared addresses. A dedicated static endpoint per profile makes behavior predictable.
Buy self-serve now, or talk with us about a larger agency inventory.