Custom domains SSL not provisioning — CNAME valid for 20+ hours
andersurroca-max
HOBBYOP

4 months ago

Hi, I have two custom domains on a Railway service with CNAME status VALID for over 20 hours but SSL certificates have never been provisioned.

CNAME status: VALID ("Full steam ahead!")

Error in browser: NET::ERR_CERT_COMMON_NAME_INVALID — server responds with *.up.railway.app cert instead of the custom domain cert

CAA records include letsencrypt.org (confirmed via Google DNS). I have redeployed the service and deleted/re-added the domains multiple times with no change.

Could you please advise why SSL provisioning is not triggering?

Thank you

$10 Bounty

1 Replies

Railway
BOT

4 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 4 months ago

0x5b62656e5d
MODERATOR

4 months ago

Can you share the domains you’re trying to add?

Welcome!

Sign in to your Railway account to join the conversation.

Login
Loading...