Apologies but this looks like an issue with the application level code. Due to volume, we can only answer platform level issues.

I've made this thread public so that the community might be able to help with you query.

I understand, but if I had visibility of the logging, I could fix it. The railway logs are not helful.

This is not giving me enough to find the issue. How do I get more visibility in the logs?

These logs are coming from your app, not railway. you'll want to add more logs on your end to figure the error out.

Try to add several logs at different places when your application starts or where the code is that is producing these logs

They have a good start up guide on NextJs may help you out https://docs.railway.com/quick-start#deploying-your-project---with-the-cli

Thanks @sim, but the issue is with the internal networking. The app is working fine. it works fine on localhost and it works find on railway when I use the public address for the api server, but I need the internal one to work so I dont get hit with egress fees.

I've had nothing but positive things to say about railway so far and have been steadily moving more to the platform, but this issue with internal vs public has been the most frustrating experience so far.

Hello,

Please see our guide on the private network -

https://docs.railway.com/guides/private-networking#communicating-over-the-private-network

Best,

Brody

You guys keep copy + pasting this doc, but it is not helping me. I've already tried with no success.

It's because the logs you posted is not at all helpful. The actual referenced js file in the stack trace is just a minified file which even in itself isn't helpful when reviewed

So there is actually no meaningful information you have provided other than "an error has occurred".

If you want help then you need to provide more information about your app and in this case you entire app because with the limited info provided i don't even know what to ask

Add me to your github repo or make it public and post it here so we can review and suggest solutions.

Yes, I agree, the initial logs I provided were not enough. I've been able to isolate it the issue to the private networking settings - which I am not getting any help from railway support except for them copy + pasting the link to their docs.

Is the service you are trying to fetch listening on IPv6?

Are you using http:// in the URL you are trying to fetch?

Are you specifying the port in the URL you are trying to fetch? (the private port such as 8080 or 3000)

I have a nestjs application running in my project.

I am trying to get my nextjs application (different service in the same railway project) to access the the nestjs application using the internal networking.

Ive tried setting my env variable in railway for the nextjs application to:

- gridlq

- http://gridlq - http://gridlq.railway.internal

none of these are working. Do i need to specify port as well?

when i set the env variable to the public address, it works fine.

Yes, when using internal networks you need to specify the port as well.

The public endpoint works because it is configured with the port already, private endpoint isn't

So it would be something like http://gridlq.railway.internal:3000

Thanks,

I tried this and still not working. Works fine with public address, but private one just wont work.

NestJS Application (Same railway project)

NextJS Application (same railway project)

gridlq.railway.internal is not listening on port 3000, it is listening on port 8080.

Where am I supposed to see that setting?

My nestjs app defaults to port 3000 if no port is specified in the env file.

  const port = process.env.PORT ?? 3000;
  await app.listen(port, '::');

If you are able to access your nestjs api on public url then check your railway deployment for public endpoint and see if it's listening on port 3000 or 8080. You can do this by going into your nestjs app -> Settings -> Networking, then click the edit button and check what port is being used. If it's other than 3000 then use that port for the internal url

I did that. There is no information on port there.

Ok, that is confusing because I am trying to use the internal network, not the public. Are you saying that both use the same port and I can reference the public to know what the private one is using?

I am assuming you got the port wrong. So if the public endpoint is working then check what port the public endpoint is using then use that for the private endpoint

in your nextjs env variable

That worked. Thank you! The fix was getting the port from the public networking.

just curious, what was it set to, 8080 ?

yes, it was using the magic port. I think they should add better visibility on this information.