22d2217f-5502-4174-951e-7e64cbde52d2

In this particular question I was wondering mainly for things such as Redis and PostgreSQL

When changing to using the private URL instead of the public, it appears to solve my bottleneck issues from scaling (large userbase). But it would be neat to get this fact confirmed as well

Yeah, services using the private network will have reduced latency.

Getting

php_network_getaddresses: getaddrinfo for redis.railway.internal failed: nodename nor servname provided, or not known

and

SQLSTATE[08006] [7] could not translate host name "postgres.railway.internal" to address: nodename nor servname provided, or not known (Connection: pgsql, SQL: select "email", "id" from "licenses" where "email"::text ilike %w%)

from using the private network URL's in my Laravel project. Any ideas how to approach this?

Maybe I should create a separate issues for this, guessing I somehow have to bind it?

By bind it do you mean the ports?

If so, yes you need to bind the port as according to the private networking docs

Getting these errors when doing railway run

Did bind using php artisan serve --host "[::]" --port $PORT, still getting the errors

Is there something special with the railway run environment that could be causing this?

railway run runs the given command locally, and you cannot connect to the private network from outside of the Railway environment as is.

For local development only, you would need to connect to the database over the public network.

Ok splendid, thanks

Shame but I can work around it

!s