3 months ago
Hi, I just started using Railway and am having problems with custom domains. I was on your Hobby plan, but now upgraded to your Pro plan just to get Railway technical support. I am deploying an app at custom domain TreasureStudio.art, with a redirect from www.TreasureStudio.art.
There are 2 issues, both confirmed by your Railway AI Agent:
- Custom domain removals are being blocked by limit validation (first defect)
- Custom domain additions are not persisting across deployments (second defect)
AI Summary:
Service: honest-curiosity
Project: empathetic-gratitude
You're trying to configure 2 custom domains (treasurestudio.art, www.treasurestudio.art)
Custom domains keep reverting to service domains after deployment.
This follows an earlier issue where domain removal was blocked by limit validation.
My goal was to complete my deployment hours ago, instead I have been debugging this issue for 3 hours now - I need to have my app running ASAP.
Regards,
James D.
Pinned Solution
3 months ago
You need to add a TXT record for _railway-verify.www.treasurestudio.art. If you are using the API to add your custom domain, you can find it in verificationToken under status.
As there are two custom domains mentioned,you'll need to add a TXT record for both domains to get everything working properly.
It might take up to 24 hours to verify custom domains if your DNS records (CNAME & TXT) have successfully propagated.
Avoid rapid removal and re-addition of domains, as it can hit rate limits with Let's Encrypt.
9 Replies
3 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 3 months ago
3 months ago
You need to add a TXT record for _railway-verify.www.treasurestudio.art. If you are using the API to add your custom domain, you can find it in verificationToken under status.
As there are two custom domains mentioned,you'll need to add a TXT record for both domains to get everything working properly.
It might take up to 24 hours to verify custom domains if your DNS records (CNAME & TXT) have successfully propagated.
Avoid rapid removal and re-addition of domains, as it can hit rate limits with Let's Encrypt.
3 months ago
Addressing issues confirmed by railway agent:
- Limit validation: as you upgrades to pro recently, wait 15-20 mins for limits to refresh or manually refresh billing page.
- Custom domains reverting to railway.app mean that railway.json or environment variables override the settings. If you have (RAILWAY_PUBLIC_DOMAIN) variable set in your service, remove it and manage domains strictly via railway dashboard
3 months ago
What value to use for the new TXT records? I am not using the API. When I go to workspace/domains, NO domains are listed.
3 months ago
Note, I do not have RAILWAY_PUBLIC_DOMAIN defined.
jrdaugherty
What value to use for the new TXT records? I am not using the API. When I go to workspace/domains, NO domains are listed.
3 months ago
workspace/domains only shows domains bought through Railway directly, not domains you own elsewhere.
Navigate to service → Settings → Networking → Public Networking → Custom Domain
If any custom domain is listed there, you'll see the CNAME and TXT values If it's not listed there either, re-add the domains and Railway will generate a fresh pair.
jrdaugherty
What value to use for the new TXT records? I am not using the API. When I go to workspace/domains, NO domains are listed.
3 months ago
Did you see any domains in your service networking settings? If yes, then send the screenshot here.
3 months ago
I added the 2 custom domains in Railway, added 4 DNS records to Namecheap; all is working now!
h701h
workspace/domains only shows domains bought through Railway directly, not domains you own elsewhere. Navigate to service → Settings → Networking → Public Networking → Custom Domain If any custom domain is listed there, you'll see the CNAME and TXT values If it's not listed there either, re-add the domains and Railway will generate a fresh pair.
3 months ago
You mind marking this as accepted solution? And the thread as solved.
Status changed to Open 0x5b62656e5d • 3 months ago
Status changed to Solved 0x5b62656e5d • 3 months ago