**Subject:** Custom Domain SSL Validation Stuck - CNAME Mismatch in API **Project ID:** 4b9bdbc7-63cf-47b7-ac9e-5176e0c45300 **Service:** web **Issue:** I've configured a custom domain `www.pipeline-drillers.co.uk` for my web service. I've set the CNAME record at my domain registrar to point to `web-production-6a87.up.railway.app`. However, the Railway API is still showing: * **requiredValue:**`qk8e8ppi.up.railway.app` (old domain) * **currentValue:**`qk8e8ppi.up.railway.app`(old domain) * **certificateStatus:**`VALIDATING_OWNERSHIP` My actual CNAME is correctly set to `web-production-6a87.up.railway.app`, but Railway's system isn't recognizing the update. This is preventing SSL validation from completing. **What I need:** Please investigate why the Railway API is still referencing the old domain and refresh the DNS validation so my custom domain can go live.

Custom Domain SSL Validation Stuck - CNAME Mismatch in API

pipelinedrillers

HOBBYOP

2 months ago

Subject: Custom Domain SSL Validation Stuck - CNAME Mismatch in API

Project ID: 4b9bdbc7-63cf-47b7-ac9e-5176e0c45300

Service: web

Issue: I've configured a custom domain www.pipeline-drillers.co.uk for my web service. I've set the CNAME record at my domain registrar to point to web-production-6a87.up.railway.app.

However, the Railway API is still showing:

requiredValue:qk8e8ppi.up.railway.app (old domain)
currentValue:qk8e8ppi.up.railway.app(old domain)
certificateStatus:VALIDATING_OWNERSHIP

My actual CNAME is correctly set to web-production-6a87.up.railway.app, but Railway's system isn't recognizing the update. This is preventing SSL validation from completing.

What I need: Please investigate why the Railway API is still referencing the old domain and refresh the DNS validation so my custom domain can go live.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • about 2 months ago

sam-a

EMPLOYEE

2 months ago

Your CNAME record is propagated, but the SSL certificate is stuck on ownership validation because a TXT verification record is missing. You need to add a TXT record in your Wix DNS with host _railway-verify.www and value railway-verify=aaf3239036861f5c417ff619af526d569c2dd84cc9306ec136e4b347e7ff61ea. The certificate will not issue until both the CNAME and this TXT record are present.

Status changed to Awaiting User Response Railway • about 2 months ago

pipelinedrillers

HOBBYOP

2 months ago

I hVW saws raw TXT record TXT (Text)

Host name

Value

TTL

_railway-verify.pipeline-drillers.co.uk

railway-verify=e73fadda90eceee91e11b77b855112ee0fced5a540113f046503eef35d2aa23d

1 Hour

Status changed to Awaiting Railway Response Railway • about 2 months ago

sam-a

EMPLOYEE

2 months ago

Your TXT verification record for pipeline-drillers.co.uk is verified. However, the domain currently configured on your service is the root domain pipeline-drillers.co.uk (not www.pipeline-drillers.co.uk), and Railway still needs a CNAME record pointing to mgedmvt9.up.railway.app for it. Root/apex domains cannot use standard CNAME records per DNS standards, and Wix DNS does not support CNAME flattening. You have two options: either switch your domain's nameservers to Cloudflare (which supports CNAME flattening at the apex, see our docs), or remove the root domain from your Railway service and re-add www.pipeline-drillers.co.uk as your custom domain instead, which works with a standard CNAME record on any DNS provider.

Status changed to Awaiting User Response Railway • about 2 months ago

Railway

BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago

Welcome!