2 months ago
Can't issue TLS with CNAME set at cloudflare dashboard (it uses CNAME flattening on root domain). Railway is not verifying domain and not issuing TLS
Pinned Solution
2 months ago
Fastly has resolved the issue. Try removing the custom domain from Railway and add it back.
13 Replies
2 months ago
It only works with Cloudflare proxy. But I don't need it!
Status changed to Open Railway • 2 months ago
machka-pasla
 Cloudflare dashboard
2 months ago
You can ignore this message.
2 months ago
Make sure your CNAME record matches the record that Railway has provided in your dashboard. It should not be the same as your generated domain.
0x5b62656e5d
You can ignore this message.
2 months ago
and nothing after
because u can't set a CNAME on @ according to RFC 1034. Cloudflare allows it to set but using CNAME flattening
Attachments
2 months ago
You need to set the target to @, not your actual domain. Cloudflare tells you specifically to use @ for root domains.
Attachments
0x5b62656e5d
You need to set the target to `@`, not your actual domain. Cloudflare tells you specifically to use `@` for root domains. 
2 months ago
Have you ever used Cloudflare?
Attachments
2 months ago
Yes, I use Cloudflare. Sorry.
Is Railway displaying an internal error when issuing a TLS cert?
2 months ago
for more than a hour it is waiting for DNS update. Please fix your checker. It is trying to brake RFC 1034 (3.6.2, If a CNAME RR is present at a node, no other data should be present;) Because of this you CAN NOT set a real CNAME on root. Only CNAME flattening like cloudflare does. But you are not accepting this)
·Waiting for DNS update
2 months ago
I don't think that community can help, because it is issue on railway side
2 months ago
The team has identified the issue regarding the TLS certificate and is working on it.
2 months ago
Fastly has resolved the issue. Try removing the custom domain from Railway and add it back.
Status changed to Solved brody • 2 months ago