getStaticProps runs at build time (ie npm run build) - this is isolated in build so Railway doesn't know what your private network address is, it'll fail and fallback to the public one. This is a pretty standard workaround tbf and its gated by a strong password so not as risky as you might be thinking. The other option is to switch to server side props - https://nextjs.org/docs/pages/building-your-application/data-fetching/get-server-side-props

Where does it say this in the railway docs? I've read through them but found no mention of it, and get server side props is pointless as it's slower and I will have to have my db constantly up instead of serverless

i would assume it executed on client-side (.next/server/chunks/ssr/_c9e176d6._.js is looks like a bundled result of client-side code) and because private url means to be used by service in the same environment as your database service, you can't use it outside of railway services

ssr is server-side rendered

does that error come from your deploy logs?

Build logs, it fails getstaticprops on build, due to not being able to access the db through private networking

Services don’t have access to private networking during the build process.

I understand but where are the docs that say this please?

Thank you!

ohh, i didnt know about this, i think moving the build step to pre-deploy command will help, or just keep going with the database public url