a month ago
Hi,
We configured a custom domain assessment.ultracar.com.br for our project. Both DNS records are set up and propagated correctly:
- CNAME: assessment → d4gq7091.up.railway.app (verified with green check in Railway dashboard)
- TXT: _railway-verify.assessment → correctly configured (still showing yellow warning in dashboard)
The CNAME is resolving correctly, but the SSL certificate being served is still the wildcard *.up.railway.app instead of one for our custom domain. This causes
NET::ERR_CERT_COMMON_NAME_INVALID when accessing:
https://assessment.ultracar.com.br/quiz/diagnostico-rapido-oficina
Could you help us get the TXT verification completed and the SSL certificate issued for this domain?
Thanks!
Pinned Solution
a month ago
If you are using Cloudflare, ensure the CNAME record for assessment is set to DNS Only (grey cloud), not proxied (orange cloud). If that doesn't work, try deleting your custom domain and all related DNS records, wait for some time, and reconfigure it again.
3 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
If you are using Cloudflare, ensure the CNAME record for assessment is set to DNS Only (grey cloud), not proxied (orange cloud). If that doesn't work, try deleting your custom domain and all related DNS records, wait for some time, and reconfigure it again.
darseen
If you are using Cloudflare, ensure the CNAME record for `assessment` is set to **DNS Only** (grey cloud), not proxied (orange cloud). If that doesn't work, try deleting your custom domain and all related DNS records, wait for some time, and reconfigure it again.
a month ago
We're not using Cloudflare — our DNS is hosted on AWS Route 53. The CNAME is resolving correctly (confirmed via dig) and shows a green check in the Railway dashboard. However, the TXT verification record still shows a yellow warning, even though it's also resolving correctly externally.
a month ago
I'd just try removing all associated records from your DNS provider and Railway, waiting for ~10-15 min, then readding them back.
Status changed to Solved 0x5b62656e5d • 16 days ago