3 months ago
i followed the directions for adding a root domain with www to cloudflare. i added the 120710.art root domain in step 1 and copied the given railway url to cloudflare's CNAME DNS records in steps 2 and then followed step 3. i see the custom domain as being served by cloudflare in your dashboard for my custom domain as cloudflare proxy detected. i redeployed my web service. i am unable to get through to my website 120710.art . i can run it using web-production-7d4c4.up.railway.app but not using the root domain.
8 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
i did try doing what was said in the "Custom WWW Domain - Not Found Message" by adding another custom domain for www.1201710.art and a record in cloudflare pointing to it (even though the railway docs says to do it the way i did it). unfortunately that didn't work. i was able to add another custom domain shows.120710.art and a cloudflare CNAME record pointing to it, so i know cloudflare is working. i know that 120710.art is getting through to railway by running curl and seeing railway in the trace. also, when i open 120710.art in a browser i get a railways Not Found (train has not arrived at the station) error with request ID VInvZBFcSbW71U_k9I3ezw so again i know that it has gotten to railway. i'm still stumped and my site is down...
3 months ago
I'm getting the bad request error for 120710. This implies that your app is routing (not our train error) but it's serving something incorrect back
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Unfortunately we can't help with app errors, but I can leave this for the community to potentially help with!
3 months ago
yeah, but it's working fine with another custom domain on the same project/deployment ( shows.120710.art ) so it can't be an app error. it also works with the default domain that you guys generated: web-production-7d4c4.up.railway.app . how could it be an app error? why would the actual domain name matter to the app?
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
i've been running my website fine on railway for two years without a problem using shows.120710.art and http://web-production-7d4c4.up.railway.app/ and now after two years am trying to run it from www.120710.art instead and hit these problems... i shutdown my www.120710.art homepage / domain on squarespace and am trying to run completely from railway and cloudflare. i'm incurring downtime on my site and could really use any hints. i'm also willing to pay someone to help me figure this out.
3 months ago
OK, you were right. i needed to add www.120710.art and 120710.art to ALLOWED_HOSTS . i figured it out by typing my question into AI. it told me how it could fail even though shows.120710.art did work. your instructions for adding custom domains on cloudflare https://docs.railway.com/guides/public-networking#adding-a-root-domain-with-www-subdomain-to-cloudflare:~:text=your%20nameservers.-,Adding,-a%20Root%20Domain is incorrect. step 3 doesn't work. you actually do need to add a completely different custom domain and point www to that one instead of to @ as said in your docs. it would be good to change your docs to reflect that.
3 months ago
Thanks for the tip! I'll have a look at the docs and see if we can make it clearer.
Status changed to Awaiting User Response Railway • 3 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 months ago