Skip to content
Server is running my app, but it's misconfigured on Railway.
jstamb
OP

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.
Solved

37 Replies

jstamb
OP

a year ago

2c432a7b-889f-40b7-9355-a32600a35e68


a year ago

hey, how are you specifying the URL on the n8n?


jstamb
OP

a year ago

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.


jstamb
OP

a year ago

how can this be avoided?


jstamb
OP

a year ago

I just had to update n8n and it started working


a year ago

be sure to be using private networking.

https://docs.railway.com/guides/private-networking


jstamb
OP

a year ago

hmm the private networking URL doesn't work


a year ago

make sure it's with the correct port and all, without https


jstamb
OP

a year ago

docs say to use http


jstamb
OP

a year ago

no http doesn't work either


jstamb
OP

a year ago

any ideas on getting local to work?


a year ago

private networking should just work, are you able to get the error?


jstamb
OP

a year ago

It doesn’t work. Unreachable via local network


a year ago

are you getting any errors from n8n? like actual errors with messages


jstamb
OP

a year ago

AxiosError: Unsupported protocol illustrious-caring.railway.internal:\n at dispatchHttpRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/node_modules/axios/lib/adapters/http.js:275:21)\n at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/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/[email protected]/node_modules/axios/lib/adapters/http.js:132:10)\n at http (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/node_modules/axios/lib/adapters/http....

code

ERR_BAD_REQUEST


a year ago

you did not add http:// at the start of the URL


jstamb
OP

a year ago

^^^^^


jstamb
OP

a year ago

I’ve tried http


jstamb
OP

a year ago

Not at my computer but I’ll resend the error with the http


a year ago

but I need the error with http, that error is basically saying that it needs the protocol (http or https)


jstamb
OP

a year ago

"Error: getaddrinfo ENOTFOUND illustrious-caring.railway.internal\n at Function.AxiosError.from (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/node_modules/axios/lib/core/AxiosError.js:92:14)\n at RedirectableRequest.handleRequestError (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]/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/[email protected]/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/[email protected]/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@[email protected]_encoding@[email protected]/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@[email protected]_encoding@[email protected]/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@[email protected]_encoding@[email protected]_/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1698:4)


jstamb
OP

a year ago


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.


jstamb
OP

a year ago

Where do I monitor network 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


jstamb
OP

a year ago

Network usage is low, highest is memory


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 • over 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...