Railway deployment Cloudflare proxy detected issue
After applying Cloudflare on the web app domain (provided also by Cloudflare) reached a problem when the proxy status for DNS records was on (view image 1).
App deployed on Railway can't be reached (image 3). Also, the railway custom domain is hanging on the "Cloudflare proxy detected" status (image 2).
But when the proxy is off everything works as supposed. As we researched proxy could not be turned off if we wanted to use a whitelist IP firewall and captcha.
Hope to see your answer soon, thanks for your attention to my issue.
20 Replies
Project ID:
2355a60c-fb4a-435c-b599-002301157e412355a60c-fb4a-435c-b599-002301157e41
do you have your ssl/tls set to full with cloudflare?https://docs.railway.app/deploy/exposing-your-app
@jonbeau No, it wasn't) Thank you, now it works! The web app works as supposed to be, but seems the problem with the Railway status (image 2) is not gone. Suppose it doesn't matters but maybe it can leak to issues in the future?
it would just simply be a UI issue, keep an eye on it and if it doesn't turn into a check mark, report back here so I can elevate it to the team
@Brody Ok, then I will report it here tomorrow.
sounds good, thanks, also no need for the pings #🛂｜readme #5 🙂
The problem with the deploy status display hasn't gone away(
but everything still does work as it should right?
right
okay will let the team know, it's just a UI bug though
thanks
Thread has been flagged to Railway team by @brody192.
How trustworthy this kind of website is https://dnschecker.org/#CNAME when it comes to check DNS propagation?
I am in the same situation where I enabled the proxy for the subdomain added through Railway, but it always comes back as "not resolved" for every location (and no checkmark on Railway dashboard). However, I can access the proxied endpoint without problem and any curl on the subdomain
curl -IL https://api.domain.tld returns the correct headers and data.
In opposite, as soon as I turn off the orange-cloud, I instantly get "resolved" on most of the location through the dnschecker website (and the green checkmark also appears instantly on Railway dashboard)
Maybe the fact that Railway can't show a green checkmark, is the same issue as this website that can't show the "resolved" locations? Or because of the Cloudflare proxy it takes way more time to propagate, and we should trust the process ™️ and wait the recommended ~48hours before seeing correct info?that website if it's legit, will never be able to give you a super accurate understanding of actual propagation, for example there are many ISP dns servers that have very long cache / update frequency times, so while Google's or cloudflare's DNS servers will have the correct value, you or your clients specific DNS server could have no value or a value that's 12 hours old, many people have opened help threads saying "my domain doesn't resolve" they sent me the domain, and it resolves for me (I use a nextdns)
also, the grey question mark is really only a UI bug, it is not always indicative of an improper domain setup, so with what I said in mind, of you want me to take a look at your domain setup to make sure you have everything setup properly on your end, open a new help thread please
What grey checkmark are you talking about?
sorry my bad, i meant grey question mark
https://discord.com/channels/713503345364697088/1142166190345687140/1142447661048414338
Ah yeah. If the domain is setup with Cloudflare proxying we can't see some details so are unable to fully determine if it is setup correctly (unlike if the request is not proxied. i.e. grey cloud).
makes sense, maybe add a tooltip or something?
Yes that is a good idea