Feel free to ping me if you reply.

did you remove the old domain after creating the new domain?

I replaced it. The networking tab in settings only displays one domain.

fcsbeta.up.railway.app is the new domain

For the service variable PUBLIC_DOMAIN you need to redeploy, did you redeploy since provisioning the new domain?

yes

this is the deploy ui for the same service as the previous screenshot

as you can see, it shows the same unchanged domain

alright let me see if I can reproduce

I created a next.js service, added a postgres database (at which point the next.js service disappeared from the ui completely until i reloaded -- im assuming a bug), added environmental variables to the next.js service, then deployed all changes and the services started deploying for the first time (the postgresql db was provisioned when I added the service -- but not deployed).

After both services were deployed, I modified the given public url and redeployed. It updated in the settings/networking UI but not in the deployment UI or the ${{RAILWAY_PUBLIC_DOMAIN}} env var

I deployed a service, with a default domain provisioned, and then I visited that domain

after I changed the domain name to something else, and deployed changes, which resulted in both the variable and the domain on the ui changing

meaning to say I can't reproduce this

can you check if the site is still running on the old domain / not running on the new domain? trying to see if this is a UI issue or not

The site is successfully running on the new domain.

When I visit the old domain (as displayed in the deployment ui), I am met with this page:

interesting, so it's just a UI bug then, weird

what browser are you using?

I'm using Zen - a firefox based browser. I'll check in a different browser

alright, sounds good, thank you for checking

I just tried in Arc and its still showing the wrong URL

I don't believe that its solely ui as the ${{RAILWAY_PUBLIC_DOMAIN}} environmental variable resolves to the incorrect domain.

even in the running deployment?

yes

meaning the deployment sees it as being the old domain and not the new domain?

I believe so. I'll double check

thank you 🙏

Yes. I just confirmed.

I'm stepping away from my laptop and won't be able to respond for a while. Let me know if theres anything I can do to help.

Alright, I'll share this thread around and see if we're maybe overlooking something, otherwise I'll inform the team of this issue

when you're back, can you try changing the domain again? maybe the previous change didn't propagate or something