FerryDocs

Error pages of the proxy

If the proxy cannot send a request to your app, it answers with its own page and an x-ferry-error header.

Edit on GitHub
Terminal
$ 

If the cannot send a request to your app, it answers with its own HTML page. The answer has an x-ferry-error .

Thus you can tell an error of the proxy from an error of your app.

The errors

x-ferry-errorCause
400bad_requestThe request has no Host header, has two, or has a bad one.
404not_foundNo service owns this host. The page says "No service is configured for …".
405method_not_allowedThe request is a CONNECT request.
408request_timeoutThe client sent no part of its request body for 60 seconds.
503suspendedYou suspended the service.
503no_upstreamsThe service has no instance that runs. See below.
502bad_gatewayThe instance refused the connection, or failed in the middle of the request.

The causes of no_upstreams

  • You never deployed the service.
  • Its last deploy failed.
  • A deploy is in progress.

The answer has the header Retry-After: 5.

On this page