Domains and HTTPS

Every app gets https://<name>.<server-ip>.sslip.io with a certificate. To add your own domain, open Domains on the app, add the hostname and create the DNS record shown (an A record to the server’s IP, or a CNAME for subdomains).

Ownership check

Adding a domain also shows a TXT record: _railyard-verify.<domain> → railyard-verify=<token>. Railyard checks it every 30 seconds (or press Check now); the certificate and routing only start once it’s found, so no one can point a domain they don’t control at your app and intercept traffic meant for it. Tick Also add the www/bare-domain version to add the pair at the same time, redirecting to this one until you pick a primary.

Wildcard domains

Adding *.example.com routes every subdomain of example.com to the app on one certificate, instead of adding each one. It can’t be a redirect, and the ownership check probes railyard-check.example.com.

Status

Each domain shows one of: unverified (TXT not found yet), pending (verified, certificate not issued yet), live (serving traffic), unrouted (verified, but the app hasn’t redeployed since — redeploy to route it) or misconfigured (certificate issuing failed — Check now shows why).

The certificate is issued automatically once DNS and the TXT record are in place; redirects (e.g. www → apex) are supported, and Make primary switches the app’s main address, redirecting the old one.