Private networking URLs are structured as .railway.internal.

Thats what I used

Do I need to specify the port or something else?

Yes.

^

Backend is called backend and react is called dashboard

You used https.

Also, you can’t use private networking for frontend code.

Clients (machines that access your website) do not have access to private networking.

The dashboard domain is using http

I am calling it through a proxy on the server

So it is not directly called from the client, the client calls the internal proxy and the proxy calls the backend

I see the https let me fix that

Do I have to add the port too?

Yes.

is it 8080 be default?

This depends on what port your application is listening to.

Thats right

With all that I get the timeout error

What could be the cause of a timeout?

Either the application didn’t respond (wrong port?) or your proxy couldn’t resolve it.

I assume the frontend is able to reach the proxy successfully?

Yes, when using the public domain everything works

the simple swap to private doesnt work

Try SSH-ing into your proxy service and curl -I your private networking URL and see if it can get a OK head response.

Right click on your service and Copy SSH Command to get the SSH command. You’ll need Railway CLI installed to use this.

root@d4c0178c0e9c:/app# curl

bash: curl: command not found

getting this, tried installing with apt but

root@d4c0178c0e9c:/app# apt install curl
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package curl

okay tried node

root@d4c0178c0e9c:/app# node -e "require('http').get('http://backend.railway.internal:8080', (res) => console.log(res.statusCode))"
301

got a 301

Right. Sorry.

Are you able to see where it’s trying to redirect you to?

(I assume you redeployed your service after updating variables?)

I did update them

I think it could be redirecting to https

full response

Might be django doing it

Ill update the force ssl bool in django

Okay that was it

The issue was SECURE_SSL_REDIRECT defaulting to True in the django settings

Good to know for anyone trying to use the internal network with django