Hey there! We've found the following might help you get unblocked faster:

• 🧵 Error: Invalid value for '--port': '$PORT' is not a valid integer.

• 🧵 redis connection error in judge0 template

• 🧵 "lost+found" folder on volume cause unexpected behaviour

If you find the answer from one of these, please let us know by solving the thread!

Hey! This is related to https://status.railway.com/cmfv2ciuy00krz1jvwfghr4gz. Apologies for the inconvenience!

We're also having this problem. Our services can't seem to resolve the internal network domain of our kafka deployment.

Hi, please has this issue been fixed as I am having a similar issue - or is there a walk around it?

There's no workaround at the moment until we fix the underlying issue. Sorry.

hey you guys having issues to about railway its said mine that invalid database url

Hey! Could you try again?

I am also getting invalid database URL. Since the outage from railway supplied env vars to the connected database

For those of you getting "Invalid database URL" could you share a link to your service please?

S

Hey, I have the same problem with my mongodb and redis instances

It seems the private networking vanished

What URL can I share for you to check that?

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Hey team! We've found an issue with database private network caching that precipitated out of our last incident. We've got a fix in flight already. The ticket will update as we make progress. Thank you for your patience!

Just jumping in here from another thread. I was able to get this working again after re-enabling private networking.

We also did this, but for some reason, doing that messes with some of the service level environment variables, but that is due to the fact that we were consuming the variable internally in the service in order to advertise it. If anyone is also having that problem, i recommend you using the service's name directly instead of "${{service.RAILWAY_PRIVATE_DOMAIN}}".

Reference variables ("${{service.RAILWAY_PRIVATE_DOMAIN}}") should still work after re-enabling private networking. Are you seeing differently?

✅ The ticket Database Connection Issue has been marked as completed.