9 months ago
Hi guys,
I am trying to setup a wildcard subdomain on railway with cloudflare. So far I am experiencing a 525 error whenever I access the subdomain. I followed the guides and turned off proxying for the _acme-challenge DNS record. I also used Full SSL/TLS encryption mode and I made sure that the universal SSL is enabled. I did these according to this guide (https://docs.railway.com/guides/public-networking#wildcard-domains)
It seems that cloudflare cannot complete a SSL handshake with the origin server.
All I can see on the railway networking tab is "Cloudflare proxy detected". There are no logs for this service as It's not being served at all through the wildcard subdomain.
So far the suggestions I've been offered by the team was that there were stale TXT records being issued by Cloudflare. As suggested, I tried to remove the wildcard domain from Cloudflare and it's corresponding DNS records, turning of Universal SSL and waiting a minimum of 10 mins before setting it up again with Universal SSL but didn't succeed.
Here's a link also referencing a Cloudflare issue that was sent by the Railway team https://community.cloudflare.com/t/stale-dns-records-being-served-by-cloudflare/619916
I would really appreciate any help figuring this issue out.
Thanks
1 Replies
9 months ago
Hey colin. I've got your other issue and we've escalated it internally. I'm closing this thread in favor of our other one.
Status changed to Awaiting User Response Railway • 10 months ago
Status changed to Closed echohack • 10 months ago
