Help me please our ip is blocked

Questions
1

Hi,

We’re experiencing persistent timeout errors when our workflow tries to make HTTP requests to a specific external API server at IP 178.250.246.39 (domain: wb.apisystem.name, port 80).

All requests from our n8n Cloud instance (IP 51.116.119.77) to this server result in timeout of 15000ms exceeded (ECONNABORTED). This has been happening since March 10, ~14:00 UTC.

At the same time, requests from the same workflow to other external APIs (e.g., Yandex Market via the same API provider but different server IP) work fine.

The API provider confirmed there is no block on their side and suggested we check if outbound traffic from our n8n instance to 178.250.246.39 might be blocked at the network/firewall level.

Could you please check if there are any network restrictions blocking outbound connections from our instance to IP 178.250.246.39?

Our instance: ingalove.app.n8n.cloud Workflow ID: 2e2Bpkhlvm69cIzs Recent failed execution: #741

Thank you!

2

hello @azakami8713 have you check to try the same API request from postman to compare if result is the same or not ?

Are you using cloud or self hosted n8n instance?

3

We use n8n Cloud (ingalove.app.n8n.cloud). The API works fine from browser and Postman (tested from Russian IP). But from n8n Cloud (IP 51.116.119.77, Azure EU) requests to wb.apisystem.name (IP 178.250.246.39) timeout. Requests to other APIs from the same n8n instance work fine. It seems the API server is only reachable from Russian networks.

4

Hi @azakami8713 Welcome!
The possible workaround that i can think of is route the request through a russian proxy server by adding a proxy option in the HTTP request node, so that if there is some blockage by that 3rd service you can tackle it.