2 months ago
Hi Community, I need Support ASAP..
I need to escalate an urgent routing and deployment issue with my frontend service (yourway-fe).
While support recently helped me attach my custom domains (yourwaycorp.com and www.yourwaycorp.com) to this service, the application is still not functioning correctly despite my latest commits on GitHub and successful redeploys on Railway.
Here are the exact symptoms we are experiencing right now:
Custom Domain (yourwaycorp.com): It is completely unresponsive. It does not react, load the application, or execute the code properly, despite the DNS being fully propagated and attached to the correct service.
Railway Default Domain (.up.railway.app): If I access the frontend via the Railway-provided URL, the site opens but only "halfway" (loads partially, but encounters issues, likely due to a routing conflict or the backend yourway-be not fully communicating with the frontend environment).
I have already verified that both services (Frontend and Backend) show as "Online", and I have pushed the latest updates via GitHub to ensure the code is up to date, but the block persists exclusively on the custom domain.
Could a technical specialist please review the internal routing, port configuration, and logs for yourway-fe and yourway-be to determine why yourwaycorp.com is failing to serve the app while the Railway domain partially works?
Thank you for your immediate assistance.
Best regards,
Pinned Solution
2 months ago
After selecting your domain in https://railway.com/workspace/domains, there should be a way for you manage the DNS records for that domain.
4 Replies
2 months ago
Your custom domain yourwaycorp.com currently resolves to an A record (91.195.240.94) instead of a CNAME pointing to zwbczl5g.up.railway.app, which is why the SSL certificate is stuck in "issuing" state and the domain is unresponsive. You need to remove the existing A record at your DNS provider (name.com) and add a CNAME record for yourwaycorp.com pointing to zwbczl5g.up.railway.app. Also, www.yourwaycorp.com is not attached to any service on our side, so you would need to add it as a custom domain in your service settings if you want it to work.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
Your custom domain `yourwaycorp.com` currently resolves to an A record (91.195.240.94) instead of a CNAME pointing to `zwbczl5g.up.railway.app`, which is why the SSL certificate is stuck in "issuing" state and the domain is unresponsive. You need to remove the existing A record at your DNS provider (name.com) and add a CNAME record for `yourwaycorp.com` pointing to `zwbczl5g.up.railway.app`. Also, `www.yourwaycorp.com` is not attached to any service on our side, so you would need to add it as a custom domain in your service settings if you want it to work.
2 months ago
Hi,
Thank you so much for looking into this and finding the issue with the A record (91.195.240.94).
I just wanted to clarify that I didn't purchase the domain externally. I bought yourwaycorp.com directly through Railway's own domain registration feature, so I don't actually have a Name.com account to manage those specific DNS records.
Since it's fully managed within Railway, could you please help me remove that default A record on your end so the SSL certificate can finally issue? Alternatively, if there's a specific section in my Railway dashboard where I can delete it myself, just point me in the right direction and I'll gladly do it.
I've also just added www.yourwaycorp.com to my frontend service settings as you suggested.
Thanks again for your help!
Best regards!!!
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved yourway-marc • about 2 months ago
2 months ago
Hi,
Thank you so much for looking into this and finding the issue with the A record (91.195.240.94).
I just wanted to clarify that I didn't purchase the domain externally. I bought yourwaycorp.com directly through Railway's own domain registration feature, so I don't actually have a Name.com account to manage those specific DNS records.
Since it's fully managed within Railway, could you please help me remove that default A record on your end so the SSL certificate can finally issue? Alternatively, if there's a specific section in my Railway dashboard where I can delete it myself, just point me in the right direction and I'll gladly do it.
I've also just added www.yourwaycorp.com to my frontend service settings as you suggested.
Thanks again for your help!
Best regards!!!
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open Railway • about 2 months ago
2 months ago
After selecting your domain in https://railway.com/workspace/domains, there should be a way for you manage the DNS records for that domain.
Status changed to Solved 0x5b62656e5d • 9 days ago