Skip to content
Custom Domain SSL Certificate Mismatch – multicakes.com
Anonymous
OP

10 days ago

Hello Railway Support,

My custom domain multicakes.com is connected to my frontend service, and both required DNS records (CNAME and TXT verification) show green/verified in Railway.

However, the domain is still serving Railway's wildcard SSL certificate (*.up.railway.app) instead of a certificate for multicakes.com.

I have verified:

  • Correct Railway ALIAS/CNAME target in Namecheap
  • TXT verification record is present and verified
  • DNSSEC is disabled
  • No CAA records exist
  • The service is deployed and online

iPhone Safari displays a "This Connection Is Not Private" warning due to the certificate hostname mismatch. Some requests also return Railway's "Not Found – The train has not arrived at the station" page.

Could you please investigate the custom-domain SSL provisioning and trigger certificate re-issuance for multicakes.com?

Please do not delete or recreate the domain, change the service configuration, or trigger a deployment without my approval.

Thank you.

Solved

1 Reply

Railway
BOT

10 days ago

The certificate for your root domain has been issued and is valid, and requests to it are reaching your service normally, so a re-issue would not change anything there.

The certificate warning and the "train has not arrived" page come from the www version of your domain. At your DNS provider, www points to your root domain, but www itself has not been added as a custom domain on your service. That means we have no certificate or route for it, so browsers on that hostname get the generic certificate and the not-found page.

To fix it, add the www hostname as a second custom domain in your frontend service's Settings, under Networking, then create the CNAME and TXT records it shows for that new entry at Namecheap, replacing the existing www record. Once that domain verifies, its own certificate is issued automatically. This does not touch your existing domain, your service configuration, or your deployments.


Status changed to Awaiting User Response Railway • 10 days ago


Status changed to Solved Anonymous • 10 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...