15 days ago
I added the custom domain opbinder.app to my frontend service. Railway has been stuck on "Waiting for DNS update · Creating domain..." for over an hour. The operation remains locked ("Cannot delete while an operation is in progress"). DNS has propagated globally. Both the CNAME and _railway-verify TXT record match the values Railway provided, and nslookup plus DNSChecker confirm they resolve correctly. The deployment is healthy, but requests to the domain reach Railway Edge and return "The train has not arrived at the station."
Pinned Solution
15 days ago
Seems like you have an A record pointing to Railway's IP instead of a CNAME?
Delete it and add a CNAME targeting the exact value Railway gave you, I also suggest turning the CF proxy back on and set SSL/TLS to Full, not Full (Strict).
If that doesn't work, remove your domain from your service wait ~10-15min and add it again.
7 Replies
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
Custom domain opbinder.app has been stuck on
“Waiting for DNS update · Creating domain” for over an hour.
The CNAME and _railway-verify TXT records match Railway’s
instructions and are globally propagated.
Cloudflare proxy is disabled (DNS only).
The domain resolves directly to Railway at 69.46.46.28.
The frontend deployment is active and works through its Railway domain.
HTTPS currently fails with:
SEC_E_WRONG_PRINCIPAL
The target principal name is incorrect.
Railway will not allow me to edit or delete the custom domain because
it says an operation is still in progress.
15 days ago
Update: after disabling the Cloudflare proxy and allowing the apex CNAME to resolve directly to Railway, opbinder.app now reaches the Railway endpoint but HTTPS fails with NET::ERR_CERT_COMMON_NAME_INVALID. Since .app is HSTS-preloaded, the browser blocks the connection. This appears consistent with the custom domain certificate not having been provisioned/attached while the domain remains stuck on “Creating domain.”
Status changed to Awaiting Conductor Response brody • 15 days ago
15 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 15 days ago
15 days ago
Seems like you have an A record pointing to Railway's IP instead of a CNAME?
Delete it and add a CNAME targeting the exact value Railway gave you, I also suggest turning the CF proxy back on and set SSL/TLS to Full, not Full (Strict).
If that doesn't work, remove your domain from your service wait ~10-15min and add it again.
medim
Seems like you have an `A` record pointing to Railway's IP instead of a `CNAME`? Delete it and add a `CNAME` targeting the exact value Railway gave you, I also suggest turning the CF proxy back on and set SSL/TLS to Full, not Full (Strict). If that doesn't work, remove your domain from your service wait ~10-15min and add it again.
15 days ago
I checked the authoritative Cloudflare DNS configuration. There is no A record configured for opbinder.app. The apex record is currently a CNAME targeting n8zmdw0.up.railway.app, set to DNS Only, and the Railway verification TXT record is also present. Cloudflare is using CNAME flattening for the apex domain. I'm still receiving NET::ERR_CERT_COMMON_NAME_INVALID when visiting opbinder.app. Can you confirm whether n8zmdw0.up.railway.app is the correct current CNAME target for the custom domain and whether Railway has successfully provisioned the TLS certificate?
15 days ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
0x5b62656e5d
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.
14 days ago
I cannot perform their suggested remove/re-add troubleshooting because Railway itself has the domain locked in an operation-in-progress state
14 days ago
After 24 hours the lock released and I was able to delete and readd the custom domain and it worked immediately
Status changed to Open 0x5b62656e5d • 14 days ago
Status changed to Solved 0x5b62656e5d • 14 days ago