Your workspace subscription state is currently INACTIVE (trial), which may be preventing successful deployments. The private URL for a database service is only generated after it has a successful deployment. You can check your workspace subscription status in your billing settings and verify that the Postgres service has a successful (not failed or crashed) deployment in the environment you're working in.

No it's not that. I'm currently working on another PRO plan project so this should not be linked to that

it seems to me it's a UI problem only.

I have the same issue, this is the second thread on the subject. It's nothing to do with subscription it's a new issue that started in the last 48 hours.

We are experiencing the same issue on a Pro plan, which is affecting the ability of our PR environments to function because the services cannot communicate on the local names as expected. For example Failed to call Restate Admin API for deployment registration worker_url=http://restate-worker.railway.internal:9080 error=error sending request for url (http://restate.railway.internal:9070/deployments)

(obviously we already tried redeploying the services)

I'm having the exact same problem.

Repro:

1. Create a new empty environment,

2. Create a github repo node.

3. Select one of your repos.

4. Set the appropriate branch and path.

5. Deploy

The private networking will show the message: "This private URL will be functional after the next deployment of this service."

Same behavior can be observed when duplicating an environment.

This is a major issue currently blocking me.

Hey, I wonder if anyone has found a solution to this.

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

So, this seems like a UI bug,

Yes, I mentioned just before that it's a UI bug. But you have to "guess" the private URL as it's not provided in the UI.

Can you share a screenshot of what you're seeing? The message appears below the private URL

ooh now it seems to be fixed! I can preview the local URL successfully

Glad to hear it's working now! Going to resolve this - we'll fix the cosmetic UI bug. Sorry for the inconvenience here.

Hey there, just following up that we've just merged a fix for the cosmetic UI bug here as well. Happy Building 🚂!