bad_gateway

{
  "meta": {
    "requestId": "req_3k2j1h0g9f8e7d6c"
  },
  "error": {
    "code": "err:frontline:upstream:bad_gateway",
    "message": "Unable to connect. Please try again in a few moments."
  }
}

​

If you’re calling an API hosted on Unkey

​

If you own this API

• The app crashed while handling the request.
• The instance was killed for running out of memory.
• The app closes idle connections too quickly.
• The app doesn’t speak the upstream protocol set for the deployment.

​

How to fix

1. Read the runtime logs around the time of the request. Look for a crash, an out-of-memory kill, or a panic on the failing route.
2. Make sure your app keeps connections open long enough for the gateway to reuse them.
3. Check that your app handles the upstream protocol set for the deployment.

​

Related errors

• err:frontline:upstream:service_unavailable: the instance refused the connection or couldn’t be reached.
• err:frontline:upstream:gateway_timeout: the instance didn’t answer in time.
• err:frontline:capacity:no_running_instances: there was no running instance to connect to.