7 hours ago
Hello Railway Support,
I'm experiencing an issue connecting my custom domain to my Railway application.
Project: bimskills-ai
Custom domain: bimskillsai.com
Railway URL: https://bimskills-ai-production.up.railway.app
The custom domain has been configured in Cloudflare, but Railway continues to display:
"Waiting for DNS update"
Here's what I've already verified:
- The domain is active in Cloudflare.
- The CNAME record points to the exact Railway target provided in the dashboard.
- The TXT verification record has been successfully verified by Railway.
- Cloudflare proxy is disabled (DNS only).
- The Cloudflare Universal SSL certificate is active.
- The application works through the Railway-provided URL.
When accessing https://bimskillsai.com, the browser displays:
NET::ERR_CERT_COMMON_NAME_INVALID
The certificate being presented belongs to *.up.railway.app, not bimskillsai.com.
Could you please investigate why the domain verification is still pending and whether SSL certificate provisioning needs to be retriggered on your side?
This is a production educational platform, and we cannot launch it while visitors receive browser security warnings.
Thank you for your assistance.
1 Replies
Status changed to Awaiting Railway Response Railway • about 6 hours ago
4 hours ago
The certificate for your domain has now been issued, and ownership verification is complete. An HTTPS request to the domain now completes and returns your application from our edge.
Your Cloudflare setup did not need any changes. With the proxy off, Cloudflare serves a root-domain CNAME as flattened A records, and that works with our routing. If a browser still shows the old *.up.railway.app certificate warning, it is holding a cached connection. A hard refresh or a new private window will load the new certificate.
Status changed to Awaiting User Response Railway • about 4 hours ago