Connect a custom domain to your app

Before you start

• Deploy the app first and confirm the default Shiprr hostname works.
• Decide whether you want a subdomain like app.example.com or a root domain like example.com.
• Open the DNS provider for the domain.

Use the Shiprr custom-domain target

Every app gets a default hostname such as my-app.shiprr.dev. For custom domains, point DNS to the Shiprr custom-domain target instead:

edge.shiprr.dev

The same target appears in the app's Domains page. Use that target rather than the app's default hostname or a temporary IP address.

Connect a subdomain

For a subdomain such as app.example.com, create a CNAME record.

type: CNAME
name: app
target: edge.shiprr.dev

After DNS is saved, add the same domain in Shiprr under App → Domains.

Connect a root domain

For a root domain such as example.com, use your DNS provider's ALIAS, ANAME, or flattened CNAME support.

type: ALIAS, ANAME, or flattened CNAME
name: @
target: edge.shiprr.dev

If your DNS provider does not support root-domain flattening, use a subdomain such as www.example.com or app.example.com.

Cloudflare setup

1. Create the DNS record in Cloudflare.
2. Point it to the Shiprr target.
3. Keep the record DNS only while setting it up.
4. Add the domain in Shiprr and wait until it works over https://.

If you later enable Cloudflare proxying, use Full (strict) SSL mode. Flexible SSL can cause redirect loops or certificate errors.

HTTPS provisioning

Shiprr provisions HTTPS automatically after the domain is attached and DNS points to the Shiprr target. New domains usually finish within a minute or two after DNS is visible.

If your domain uses CAA records, make sure they allow sectigo.com so certificate issuance and renewal can complete.

Troubleshooting

• Test the default Shiprr hostname first to confirm the app itself is healthy.
• Confirm the domain is attached to the correct app.
• Confirm DNS points to edge.shiprr.dev.
• For Cloudflare, switch back to DNS only during setup.
• Make sure /.well-known/* is not blocked by security rules.
• Open the domain over https:// after DNS has propagated.