a year ago
I successfully installed this docker https://github.com/gyoridavid/ai-agents-no-code-tools and it's running on, viewable at the domain and /health and /docs.
I was able to successfully test the API with ```
curl --location 'https://YOUR_DOMAIN/api/v1/media/audio-tools/tts/kokoro/voices'
So everything is seemingly working, but theres a connection issue between n8n hosted on Railway and the docker image hosted on railway as well. The form in n8n triggers the workflow to take the AI tools URL (the docker image) and add /health which spits back a server status (OK) then continues, or it gives the server error route. In this case it's given the error every time, despite being live and running. This is a railway to n8n specific issue, as discussed with the author of the docker image who hosts on coolify.37 Replies
a year ago
hey, how are you specifying the URL on the n8n?
It’s in the server config node which just has a variable. I’ve tried without https://, without the forward slash, no port number etc.
a year ago
if you're trying through the public networking then surely it shouldn't be issue
a year ago
I would check if the variable is correct, Railway has no issues in connecting between services.
a year ago
also, be warned that the public networking occurs bandwidth charges.
a year ago
be sure to be using private networking.
a year ago
make sure it's with the correct port and all, without https
a year ago
private networking should just work, are you able to get the error?
a year ago
are you getting any errors from n8n? like actual errors with messages
AxiosError: Unsupported protocol illustrious-caring.railway.internal:\n at dispatchHttpRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/axios@1.8.3/node_modules/axios/lib/adapters/http.js:275:21)\n at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/axios@1.8.3/node_modules/axios/lib/adapters/http.js:152:5\n at new Promise ()\n at wrapAsync (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/axios@1.8.3/node_modules/axios/lib/adapters/http.js:132:10)\n at http (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/axios@1.8.3/node_modules/axios/lib/adapters/http....
code
ERR_BAD_REQUEST
a year ago
you did not add http:// at the start of the URL
a year ago
but I need the error with http, that error is basically saying that it needs the protocol (http or https)
"Error: getaddrinfo ENOTFOUND illustrious-caring.railway.internal\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:536: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:524:28)\n at emitErrorEvent (node:http_client:101:11)\n at Socket.socketErrorListener (node:http_client:504:5)\n at Socket.emit (node:events:524:28)\n at emitErrorNT (node:internal/streams/destroy:169:8)\n at emitErrorCloseNT (node:internal/streams/destroy:128:3)\n at processTicksAndRejections (node:internal/process/task_queues:82: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:95:5)\n at invokeAxios (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:206:10)\n at proxyRequestToAxios (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:656:20)\n at Object.request (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_openai@4.78.1_encoding@0.1.13_zod@3.24.1_/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1698:4)
a year ago
You can't use the internal address there
a year ago
Use the public one and it will work
a year ago
@meowsseline can you try that please? ˆ^
a year ago
the private url is setup correctly here, if it didn't work then I think you need to stick with the public one
a year ago
maybe it does some internal lookup and it resolves wrongly idk
a year ago
I agree with Medim. It seems like it's not worth the trouble. Use the public network and monitor to see if it incurs noticeable bandwidth charges.
a year ago
Go to your service and then select the metrics tab and look at the network metrics
a year ago
go to your project, click on settings on the top bar and then select usage.
keep an eye out for network usage
a year ago
keep a look for a few days, if something happens feel free to open a new help thread
a year ago
!s
Status changed to Solved medim • 11 months ago