Static Outbound IP feature not working for n8n service (ENOTFOUND error persists)

nik1125
PRO

4 days ago

Hello Railway Team,

I have upgraded to the Pro plan specifically to use the Static Outbound IP feature for my n8n service, but the feature does not seem to be working correctly.

Here is the situation:

  1. My n8n service (Project ID:, Service Name: Primary) was unable to make outbound requests, resulting in a getaddrinfo ENOTFOUND error.

  2. I upgraded to the Pro plan and enabled "Static Outbound IPs" for the service. The assigned IP is 208.77.244.15.

  3. I have performed a full redeployment of the service after enabling the feature.

  4. Despite this, the HTTP Request node in n8n still fails with the exact same getaddrinfo ENOTFOUND error.

  5. The deployment logs show that the service starts with n8n ready on :: port 5678, indicating it is still bound to the IPv6 private network.

It appears that DNS requests from my service's IPv6 environment are not being routed through the static IPv4 outbound gateway. Could you please investigate why this paid feature is not functioning as expected for this setup?

Thank you.

Awaiting User Response

1 Replies

itsrems
EMPLOYEE

3 days ago

Could you give more details as to:

  • What the full error giving you getaddrinfo ENOTFOUND is ?

  • What HTTP Request you're running ?

  • What you expected to do with static outbound IPs ?

Status changed to Awaiting User Response railway[bot] • 3 days ago

Static Outbound IP feature not working for n8n service (ENOTFOUND error persists) - Railway Help Station