FerryDocs
Guides

Troubleshooting

Find the message that you see. Each page gives its cause and the repair.

Edit on GitHub

Start ferryd. ferryd stops with an Error: line and its cause.

1 / 6
Where the problem shows

Each page shows a message as Ferry prints it. A … replaces the parts that change with your setup.

For a failed deploy, the full story is in its . The page of the deploy in the dashboard shows the same log.

Terminal
ferry logs --deploy DEPLOY_ID

Find your problem

When ferryd starts. ferryd tests its data directory, its addresses and Docker before it starts.

What you seePage
cannot connect to Dockerferryd cannot connect to Docker
Address already in useA port is in use
Permission denied (os error 13)Permission denied on port 80 or 443
another ferryd is already runningAnother ferryd uses the data directory
belong to another Ferry serverThe Docker prefix belongs to another server

When you sign in to the dashboard.

What you seePage
This is not the setup code of this server.The dashboard asks for a setup code
You do not know the passwordI forgot the password
too many failed attemptsToo many failed attempts

When you use the CLI.

What you seePage
cannot reach Ferry serverThe CLI cannot reach the server
not logged in, invalid API tokenNot logged in, or the token is wrong
the login request expiredferry login does not finish

During a build. The live deploy continues to answer.

What you seePage
could not detect the runtimeFerry cannot detect the runtime
secret env mounts need Docker Engine 27.3Builds fail on an old Docker Engine
the docker CLI ('docker') was not foundferryd cannot find the docker CLI
not enough free disk spaceThe disk is almost full

During a deploy. The previous deploy continues to answer. See Health checks.

What you seePage
nothing accepts connections on container portThe health check times out
GET /healthz returned HTTP 404The health check path answers with an error
crashed (exit code 1)The app crashes
exited with code 0The app exits immediately
ran out of memoryThe app runs out of memory

When you open your app.

What you seePage
404, 502 or 503 with an x-ferry-error headerThe proxy answers with an error
A domain stays on Waiting for DNSIf the verification fails
No certificate for a custom domainProblems with a custom domain

The most frequent problems

On this page