2 months ago
Custom domain design219.com will not go live on my web service.
Project: design219-site
Project ID: f227d029-3289-4276-89f0-2fdc512ae67a
Environment: production
Service: web
Railway-provided domain: web-production-fa43.up.railway.app
Custom domain: design219.com
CNAME target Railway gave me: 419aeasc.up.railway.app
What I see:
Public Networking still shows Waiting for DNS / yellow warning, or the cert never issues for design219.com
TLS certificate is CN=*.up.railway.app (SAN does not include design219.com)
HTTPS to https://design219.com fails the certificate hostname check
Requesting the custom domain returns: 404 Application not found
DNS is at Namecheap, nameservers Namecheap BasicDNS. These records are publicly live:
ALIAS @ -> 419aeasc.up.railway.app
CNAME www -> design219.com
TXT _railway-verify -> railway-verify=76ce60aa2ea1ba7dda54bbce92638ae2271824b2b8229a7225e0b69696e35147
This domain also has iCloud MX/email records. Those are separate and should not be changed.
Please bind design219.com to the web service and issue the SSL certificate. I can remove and re-add the custom domain if needed. I have not changed the Namecheap records since they went public.
4 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your DNS records are correct and fully propagated, but the certificate workflow stalled before it could pick up the verification TXT record you published. We've re-triggered certificate issuance for the domain, which should complete verification and issue the TLS certificate within a few minutes. Once that finishes, the 404 should resolve as routing activates for the verified domain. Reply here if it hasn't come through after about 10 minutes.
Status changed to Awaiting User Response brody • about 2 months ago
2 months ago
Root design219.com is live. Thank you. www.design219.com still fails (old railway.app cert / no routing). Please issue and bind www.design219.com as well. I have not changed DNS. www already CNAMEs to design219.com. Tell me if you need anything else from me.
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
www.design219.com is not registered as a custom domain on your service, which is why it has no certificate or routing. Your DNS is already correct (www CNAMEs to design219.com, which reaches our edge), so you just need to add www.design219.com as a second custom domain on the web service in your project's networking settings. Once added, the certificate and routing should provision automatically since the DNS is already in place.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved Railway • about 2 months ago