24 days ago
Hello,
I’m trying to connect my custom domain:
to my Railway service.
DNS is correctly configured and resolves to:
I have confirmed via DNSChecker that the CNAME record is properly pointing to Railway.
The Railway default domain (artifexwebsite-production.up.railway.app) works correctly.
However, when accessing https://www.artifextechnology.com, the certificate being served is:
and not a certificate for my custom domain.
This results in a browser error:
ERR_CERT_COMMON_NAME_INVALID
The domain shows as added in Railway, but SSL certificate is not being issued for the custom domain.
When running:
curl -v https://www.artifextechnology.com
The server is still serving:
CN=*.up.railway.app
subjectAltName does not match host name.
So SSL certificate for the custom domain has not been attached on the edge.
Could you please check if SSL provisioning is stuck or needs to be reset on your side?
Thank you.
3 Replies
23 days ago
You need to also configure your domain in railway, otherwise it doesn't know that you want that behavior.
23 days ago
Adding onto above: You need to add both the root and www in Railway AND your DNS provider.
Certain DNS providers may not support CNAME flattening (using a CNAME record for root), so in that case, I’d suggest using Cloudflare’s DNS service.
22 days ago
Okay, thanks!