10 months ago
Cloudflare DNS with proxy enabled, SSL mode set to Full (not strict), CNAME record set that matches Railway console. Getting the Railway 404 page. Is this just a matter of waiting longer? I dont remember much of a wait in the past doing this on other services with same set up.
project ID fc88b587-5e80-4df4-8e41-de36a2e6a502
service ID 552be1f1-5754-405d-aba8-d7c03a83b107
18 Replies
10 months ago
Can you share the domain?
10 months ago
Have you tried deleting both the CNAME record and custom domain and just starting over?
10 months ago
Can you screenshot your cname rule if that doesn’t work?
in my experience railway never changes from "Record not detected" - assume because its proxied behind CF. Have apps running for months on Railway with custom domains that still say that
10 months ago
Yeah that's what I was going to suggest
10 months ago
If that still doesn't work then honestly I would just give it some time, there's a billion places that could have cached the cname
10 months ago
Getting an SSL error now
10 months ago
Come back in 15
completely deleted the service and recraeted everything and it seems to be working now
10 months ago
🌠
10 months ago
No idea why.


