2 years ago
Why custom domains for PR environments redirect to Railway generated domains? For manually created environments everything works fine.
7 Replies
2 years ago
Hey! We don't support custom domains for PR environments yet.
Feel free to upvote this if you'd like the feature, it will help us prioritize what to build :)
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Well, but it does allow adding custom domains and for some PRs it did work before.
Status changed to Awaiting Railway Response Railway • over 1 year ago
2 years ago
You can add custom domains to a service in a PR environment after the fact, but there's currently no way to specify a root domain to use for services within PR environments.
As for the being redirected thing, I would recommend re-deploying the service after adding a custom domain to it so it can be "aware" of the new domain.
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Thanks, redeployment helped
Status changed to Awaiting Railway Response Railway • over 1 year ago
Status changed to Awaiting User Response Railway • over 1 year ago
2 months ago
Is there a way to workaround this? We need our PR environments to run on a custom domain. Is there any way to get around this? Maybe some CLI command or config that allows us to set it after?
atjain03
Is there a way to workaround this? We need our PR environments to run on a custom domain. Is there any way to get around this? Maybe some CLI command or config that allows us to set it after?
a month ago
did you find any workarounds? I'm facing this problem too