This private URL will be functional after the next deployment of this service.
ignatij
FREEOP

a month ago

Hi Railway team,

Currently I'm stuck on the following message for my postgres instance:

This private URL will be functional after the next deployment of this service.

Here's a link to the service:

https://railway.com/project/1c673b86-19f5-4a0a-b38c-03fa55511046/service/d71acdea-1e45-4f9a-91ae-a4e8d2824f57/settings?environmentId=19071988-1b20-4e7b-9fdb-27dca0b3f29c

No matter how many times I redeploy the service, it's no use. It's still not generating the private url

Solved

13 Replies

Railway
BOT

a month ago

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.


Status changed to Awaiting User Response Railway about 1 month ago


ignatij
FREEOP

a month ago

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


Status changed to Awaiting Railway Response Railway about 1 month ago


ignatij
FREEOP

a month ago

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


jossm-zilo
PRO

a month ago

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.


Anonymous
PRO

a month ago

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)

Attachments


dev-futuros
HOBBY

a month ago

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.


dev-futuros
HOBBY

a month ago

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


a month ago

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

So, this seems like a UI bug,


Status changed to Awaiting User Response Railway 26 days ago


ignatij
FREEOP

a month ago

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.


Status changed to Awaiting Railway Response Railway 26 days ago


a month ago

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


Status changed to Awaiting User Response Railway 26 days ago


ignatij
FREEOP

a month ago

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


Status changed to Awaiting Railway Response Railway 26 days ago


a month ago

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


Status changed to Awaiting User Response Railway 26 days ago


Status changed to Solved ray-chen 26 days ago


chandrika
EMPLOYEE

24 days ago

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


Status changed to Awaiting User Response Railway 24 days ago


Railway
BOT

17 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...