Skip to content

Troubleshooting

Common edge responses and how to debug them.

Status: skeleton

Full content lands in a follow-up pass.

Your site has been suspended under our abuse policy. The response body includes a link back to the policy. File an appeal from the portal.

502 Bad Gateway

The edge couldn't reach your origin. Common causes:

  • Origin is down or overloaded
  • Origin's TLS cert is expired or hostname-mismatched
  • Origin's firewall blocks our egress IPs (clearnet origins)
  • .onion origin's hidden service descriptor is stale (republish from your origin's tor)

503 Service Unavailable

  • Your prepaid balance reached zero. Top up to restore service.
  • Or the edge is rate-limiting you (rare; check Retry-After)

504 Gateway Timeout

Origin took too long to respond. Default origin timeout is 30 seconds.

How to debug at the edge

Every response carries an X-Viaduct-Site-ID header. If you contact support, include that header value — it's the fastest path to "what was the cache state when this happened" without needing your .onion address.