GuidesTroubleshooting
The proxy answers with an error
When the proxy cannot send a request to your app, it answers with its own page and an x-ferry-error header.
What you see
Your app does not answer. The browser shows an error page with the status 404, 502 or 503. Read the headers of the answer:
curl -sI http://shop.localhost:8080/ | grep -i x-ferry-errorThe proxy adds the x-ferry-error header to its own error pages. Thus you can tell them apart from the errors of your app.
Why it occurs
404 not_found: no service has this hostname.
1 / 4
How to repair it
Status and x-ferry-error | Repair |
|---|---|
404 not_found | Get the URL with ferry open NAME. For custom domains, run ferry domains NAME. |
503 no_upstreams | Run ferry deploys NAME and ferry status NAME. Then read the log of the failed deploy. |
503 suspended | ferry resume NAME |
502 bad_gateway | Read the runtime logs: ferry logs NAME. |
No service has this hostname. The possible causes:
- An error in the name.
- A domain that is not a domain of the server, or that waits for its DNS (
ferry domains). - A request to an IP address.
- A worker or a private service: they have no public URL.
- A reverse proxy in front of Ferry that does not pass the Host header.
The service has no instance that runs: you did not deploy it, its last deploy failed, or its first deploy is in progress.
- For a domain that stays on Waiting for DNS, see If the verification fails.
- For certificates and custom domains, see Problems with a custom domain.