Can you elaborate on "redeployments are not promoting a private URL to usable"?

This private URL will be functional after the next deployment of this service.... I redeployed the service, yet, the private (internal) URL is NOT accessible, the message persists.

Can you provide a screenshot of the error message?

I have deployed the service, the private networking does not work. It is in accessible/not warm. I have been trying to use a reverse proxy to access it, it won't work. This may sound technical, I have tried the exact same approach on other projects, and it worked, the issue is, the private url is not functional and does not update despite further deployments.

Have you tried deleting the service and re-adding it?

Of course, I have. The same issue persists of This private URL will be functional after the next deployment of this service. as shown above in the message before this.

runtime v2? where do i get this? or do we wait as it may be a pending feature?

This only happens when you first add a service and it hasn't finished the deployment process for the first time. Looking at the image you provided, all previous deployments were removed and you're currently building a new one (suggesting no deployment was fully finished).

Your service needs to finish deploying, then the private URL will be available.

no - it was built and deployed, it literally did not work.as you can see in the 3 screenshots attached, it is built/online/active and running but no internal private networking is being picked up.

It might be stuck for some reason then. Try to delete the whole service (not just remove the deployment), and add a new one from your github repo.

I'm also getting this issue with my clamav service. I've tried deleteing service and re-adding it and deployed again by changing adding an environment variable.When I try to connect through my nodejs app, ECONNREFUSED

I have the same problem, issue seems to have arisen in the last 48 hrs

this issue still persists btw

Hello, I’m having the same issue.

My service was deployed from a pull request, and it keeps getting stuck on the same message.

I’ve tried updating the URL and redeploying the service, as well as deleting it and redeploying it, but nothing worked.

Creating a fresh new service doesn’t work either.

bump, railway is becoming the bottleneck for my work. I need help please. I love railway but now its becoming a limitation; I have tried these, redeployments etc. NONE of it worked. HELP!

Got the same problem, im deploying a FastAPI service right now

Got same issue today! Deploying a nodejs service

Are you able to connect/use the private URL? I just checked and it works.

So, this seems like a UI bug,

did you find a solution?

Hi folks, we've shipped out a fix for the cosmetic UI bug here that was persisting the "This private URL will be functional after the next deployment of this service" incorrectly, so this should be sorted. Please let us know by opening a new thread if you are still running into any issues here