What exactly is the issue?

It seems like all you posted was a response from an AI...

Are you trying to access your frontend service from your local machine?

Getting a blank white page on accessing my url

What URL are you trying to access? And are you accessing it from your local machine?

Drivemcr.com and no not local

How do you know your service is serving content correctly?

Before treating this as purely a Railway infrastructure issue, there are a couple of things worth confirming from inside the containers:

1. Check how the frontend is binding Even if Nginx is on port 80, it must be listening on 0.0.0.0, not 127.0.0.1.

Run inside the frontend service:

netstat -tulnp | grep 80

or

ss -tulnp | grep 80

You should see:

0.0.0.0:80

If it is bound to 127.0.0.1, the gateway will not be able to reach it over the private network.

1. Test from inside the gateway Open a shell in the gateway service and run:

curl -v http://frontend.railway.internal:80

If this times out, it confirms either a binding issue or a private network routing issue.

1. Try hostname variations Sometimes Railway resolves slightly differently, so also try:

http://frontend.railway.internal
http://frontend:80

1. Redeploy both services in order Stop both services, deploy frontend first, then deploy gateway. This can refresh internal service discovery.
2. Temporary workaround If this is blocking you right now, expose the frontend publicly and point the gateway to its public URL. That bypasses the private network entirely.

Based on everything you shared, if the frontend is correctly bound to 0.0.0.0 and internal curl still times out, then it does look like a Railway private networking issue.

In that case, your ticket is valid, but it will help to include:

• Output of the curl test from gateway
• Output of netstat or ss from frontend
• Whether the timeout is consistent or intermittent

That should give Railway enough to investigate faster.