Hey deltashare,

Can you be a bit more specific? Which service are you trying to network? Which port is the service running on? How are you trying to connect to the service?

Hey echohack, Thanks for replying.

Railway Environment:

• So I have a FastAPI service running on port 8000. On that same service, I have activated a Railway auto generated domain attached to port 8000.

• On the same environment, I have my n8n service calling that FastAPI endpoint using an HTTP node.
  
  The issue is I can call the FastAPI service from outside of Railway environment perfectly fine. However, that same service is failing to respond from the n8n pipeline running on the same environment.
  
  Actions I took:
  I made sure all services running on on Metal Edge network.

Happy to explain more if needed.

Ah, are you trying to connect on Private networking? If so, is your n8n service calling over ipv6 and is the FastAPI endpoint binding to ipv6?

You might find this doc helpful: https://docs.railway.com/guides/private-networking#listen-on-ipv6

It is actually "Public Networking", Railway provided domain specifically. It does detect the port (8000) automatically once generated and the service is reachable from my local computer perfectly fine.

The issue is that existing n8n service - hosted within the same environment - as the FastAPI service listening on port 8000, IS NOT responding to HTTP calls from n8n interface.

I'm not sure if I'm missing something?

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Hey there! I'm not seeing where your FastAPI service is connected to n8n?

Could you link me directly to the Service where you're having an issue and/or provide detailed steps to reproduce your issue?

Hey there, thanks for replying.

I was under the assumption that when a service is publicly exposed (through Railway auto-generated domain), as the FastAPI service is, it will be available from within the environment (n8n) and outside such as postman access which appeared to be incorrect.

I solved it by providing RAILWAY_PRIVATE_DOMAIN variables to my n8n instance.

Thank you.

✅ The internal ticket Connect FastAPI to n8n? has been marked as completed.