Railway · infra · fg-0077

Railway custom domain never gets a certificate after the CNAME was set

Certificate warning on the custom domain

Verified 2026-07-31 · Confirmed by 0 builders · Trust 50/100

Cause

Each custom domain gets its own CNAME target, which can change, and Railway also requires a TXT verification record. A CNAME pointing at an old target with no TXT never issues a certificate. Some plans cap custom domains at two.

Fix

Copy the current CNAME target and the TXT record from the service's domain settings into DNS, and remove unused custom domains if you hit the cap.

Apply

DNS: CNAME <sub> -> <hash>.up.railway.app and TXT _railway-verify.<sub> = railway-verify=<value>, both copied from the custom domain panel of the service

Affects: Railway, July 2026

claude mcp add --transport http footgun https://getfootgun.com/api/mcp