FerryDocs
GuidesCustom domains & HTTPS

Wait for the certificate

Ferry asks for the certificate some seconds after the proxy routes the domain. Follow the request, then test the site.

Edit on GitHub
Terminal
$

Ferry asks for the some seconds after the proxy routes the domain. The state issued tells you that the certificate is ready.

If a request failed, the command shows the cause and the time of the next attempt. The dashboard shows the same data in Server → Domains. See the states.

In the server log

journalctl -u ferryd
INFO requesting a TLS certificate for shop.example.com
INFO obtained a TLS certificate for shop.example.com (valid until 2026-12-26 07:12:03 UTC)

Test the site

Terminal
curl -I https://shop.example.com
curl -I http://shop.example.com     # 308 Permanent Redirect to https://shop.example.com/

The second command shows the from HTTP to HTTPS.

Add the domain to the service

Add the custom domain with the CLI, the API or a blueprint. The proxy routes it immediately.

How Ferry manages certificates

Ferry asks for one certificate for each hostname, keeps it on the disk and renews it.

On this page

In the server logTest the site