12 days ago
I think there's some network issues between my core-api service and my cadence service. The way I have everything configured worked previously.
I can't ssh into the service itself to debug because its crashed, because it can't connect.
I have a vpn into my production environment, and i can ping it just fine.
2 Replies
12 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 12 days ago
12 days ago
This looks like it's related to Railway's GCP outage on May 19th which affected internal networking between services. A few things to try:
Go to each service → three dots → Restart both services, starting with the one being connected TO
If that doesn't work, Redeploy both services from the latest deployment
Check that your internal Railway reference variable (e.g. ${{service.RAILWAY_PRIVATE_DOMAIN}}) is still correctly set sometimes these reset after infrastructure incidents
If it was working before the outage and nothing in your config changed, a full redeploy of both services should restore the internal network connection.
12 days ago
One thing to check beyond the outage: make sure both services are in the same environment (e.g. both in production), private networking only works within the same environment.
Also confirm you're using the private domain (${{cadence.RAILWAY_PRIVATE_DOMAIN}}) not the public URL for internal connections.
After the May 19 outage some reference variables lost their values, check Variables tab on both services.
Status changed to Solved dyc3 • 12 days ago