2 years ago
During the first try to add a custom domain to my project using "www" prefix, a problem occurred, due to the "Go Daddy" incompatibilities and the process was canceled. After bypassing the domain with Cloud Flare, the webpage can only be accessed without using "www" because Railway seems to be expecting the first attempt and redirects to the "Nothing here… yet" screen.
How can I kill this pending process from Railway to release the use of the prefix in my custom domain?
Thanks for understanding ☺
5 Replies
2 years ago
It's likely something is missconfigured somewhere, please send a screenshot of your domains in railway and your cloudflare DNS settings.
2 years ago
Nice
The domain is without "www", but I think it is possible to re-route using the configuration, the thing is, Railway claims it first. Here are the screenshots:
Attachments
Status changed to Solved Railway • almost 2 years ago
2 years ago
Oh, basically the 2 ways must be added. I did what you suggest and it seems to be working now, it makes sense.
Thanks a lot for your help @brody ☺