10 days ago
My Node app has deployed successfully and is ACTIVE, but after renaming the Railway-generated domain from parade-manager-production.up.railway.app to band-parade-manager.up.railway.app, Public Networking has remained stuck showing “Updating to band-parade-manager.up.railway.app”.
The old domain currently returns Railway’s “Not Found / check your network settings to confirm that your domain has provisioned” page.
The deployment itself is healthy and Postgres is online.
Could you please check whether the generated domain provisioning/rename is stuck on Railway’s side?
3 Replies
Status changed to Awaiting Railway Response Railway • 10 days ago
10 days ago
10 days ago
Hi, thanks for the detail, that helped pin this down quickly.
Good news: the rename actually finished on our side. band-parade-manager.up.railway.app is live and serving your app right now, and the old parade-manager-production.up.railway.app has been released, which is why it now shows our fallback "not found" page. Your deployment and Postgres are both healthy.
What got stuck was only the Public Networking panel's view. It was holding a cached copy of the old name and hadn't picked up the completed rename, so it kept showing "Updating". I've cleared that on our end. Please give the page a hard refresh (Cmd/Ctrl+Shift+R) and you should see band-parade-manager.up.railway.app as the active domain, with the "Updating" state gone.
If it still looks stuck after a refresh, let me know and I'll take another look. You're safe to keep using band-parade-manager.up.railway.app in the meantime.
Status changed to Awaiting User Response Railway • 10 days ago
Status changed to Solved dizzydes90 • 10 days ago
10 days ago
Thanks for the prompt response. Will check this out and confirm when working. I think this is resolved but I may have other issues at my end
Status changed to Awaiting Railway Response Railway • 10 days ago
Status changed to Solved Railway • 10 days ago