2 months ago
Hi, there is some problem with connection between my two services. The connections was working fine for some time but its down. I don't know for how long.
Project name gallant-acceptance
Service n8n cant not send request to service fa_server.
fa_server is working if I enable public networking, I tested it 5 minutes ago. But private networking is not working. I tried restart and redeploy and nothing.
[
{
"error": {
"message": "connect ETIMEDOUT 10.149.121.101:8000",
"name": "Error",
"stack": "Error: connect ETIMEDOUT 10.149.121.101:8000\n at Function.AxiosError.from (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/axios@1.8.3/node_modules/axios/lib/core/AxiosError.js:92:14)\n at RedirectableRequest.handleRequestError (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/axios@1.8.3/node_modules/axios/lib/adapters/http.js:620:25)\n at RedirectableRequest.emit (node:events:530:35)\n at ClientRequest.eventHandlers. (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/follow-redirects@1.15.9/node_modules/follow-redirects/index.js:49:24)\n at ClientRequest.emit (node:events:518:28)\n at emitErrorEvent (node:_http_client:104:11)\n at Socket.socketErrorListener (node:_http_client:518:5)\n at Socket.emit (node:events:518:28)\n at emitErrorNT (node:internal/streams/destroy:170:8)\n at emitErrorCloseNT (node:internal/streams/destroy:129:3)\n at processTicksAndRejections (node:internal/process/task_queues:90:21)\n at Axios.request (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/axios@1.8.3/node_modules/axios/lib/core/Axios.js:45:41)\n at processTicksAndRejections (node:internal/process/task_queues:105:5)\n at invokeAxios (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.103.0_encoding@0.1.13_ws@8.17.1_zod@3.25.67_/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:315:10)\n at proxyRequestToAxios (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.103.0_encoding@0.1.13_ws@8.17.1_zod@3.25.67_/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:707:20)\n at Object.request (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.103.0_encoding@0.1.13_ws@8.17.1_zod@3.25.67_/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1753:4)",
"code": "ETIMEDOUT"
}
}
]
6 Replies
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 2 months ago
2 months ago
Are you hard-coding the IP Address? If so, you need to swap the IP for the internal hostname of the service. It would be something like fa_server.railway.internal (check in your service settings).
2 months ago
No I dont hard-code the IP address in the example you can see IP already resolved by DNS I guess. My service uses http://fa%5Fserver.railway.internal:8000
2 months ago
Try to use fa_server.railway.internal (or whatever the internal URL is) instead of fa_server .
2 months ago
Thats what I do, I use http://fa%5Fserver.railway.internal:8000. I made mistake in my prev comment, edited it. The setup worked fine some time ago. Something must have happen on railway guys side I guess.
2 months ago
One other thing you can try, is to make your fa_server bind on both IPv6 and IPv4 using :: . Connecting to IPv6 might reslove your problem.
If you are using express for example, your code would look like this:
app.listen(PORT, "::", () => {});2 months ago
"::" doesn't help. Internal communication is not working for my services can I finally get some actual support?