frontline/upstream/service_unavailable

{
  "meta": {
    "requestId": "req_3k2j1h0g9f8e7d6c"
  },
  "error": {
    "code": "err:frontline:upstream:service_unavailable",
    "message": "The service is temporarily unavailable. Please try again later."
  }
}

​

If you’re calling an API hosted on Unkey

​

If you own this API

• The process hasn’t finished starting yet.
• The process exited.
• The process listens on a different port than your runtime settings say.
• The process listens only on localhost instead of all interfaces.

​

How to fix

1. Check the runtime logs to see whether the process starts and stays up.
2. Make sure the port in the runtime settings matches the port your process listens on, and that it listens on all interfaces.
3. If the process is slow to start, check the health check settings so we can tell when it’s ready.

​

Related errors

• err:frontline:upstream:bad_gateway: the connection opened and then failed.
• err:frontline:upstream:gateway_timeout: the instance didn’t answer in time.
• err:frontline:capacity:no_running_instances: no instance was running at all.
• err:unkey:application:service_unavailable: the Unkey API failed on our side.