2 months ago
OpenClaw told me to change openrouter dozens of times so i did.
I dont' know what to do since it completely crashed.
I've been trying to figure it out for hours now can't see to fix it
Below is what Railway says is the issue.
"Telegram bot won't start alongside dashboard. Dashboard on 8080, bot needs 3001. Both processes need to run in parallel in the same service."
17 Replies
Status changed to Open Railway • about 2 months ago
2 months ago
okay will do!
2 months ago
Still error. I'm not sure what the issue is
2 months ago
2 months ago
I'm not able to access your project. Please copy or screenshot the relevant logs.
2 months ago
2026-04-28T22:07:08.104604388Z [err] throw er; // Unhandled 'error' event 2026-04-28T22:07:08.104609331Z [err] ^ 2026-04-28T22:07:08.104615169Z [err] 2026-04-28T22:07:08.104620159Z [inf] > start 2026-04-28T22:07:08.104621179Z [err] at Server.setupListenHandle [as _listen2] (node:net:1940:16) 2026-04-28T22:07:08.104622120Z [err] Error: listen EADDRINUSE: address already in use :::3001 2026-04-28T22:07:08.104623908Z [inf] 2026-04-28T22:07:08.104628674Z [inf] > sh -c 'node dashboard/server.js & node telegram-bot.js & wait' 2026-04-28T22:07:08.104636195Z [err] at Module._compile (node:internal/modules/cjs/loader:1705:14) 2026-04-28T22:07:08.104637547Z [inf] 🤖 OpenClaw web interface running on http://0.0.0.0:3001 2026-04-28T22:07:08.104638396Z [err] at listenInCluster (node:net:1997:12) 2026-04-28T22:07:08.104645719Z [err] at Object..js (node:internal/modules/cjs/loader:1838:10) 2026-04-28T22:07:08.104646961Z [inf] Model: openai/gpt-4o-mini 2026-04-28T22:07:08.104647257Z [err] at Server.listen (node:net:2102:7) 2026-04-28T22:07:08.104650575Z [err] at Function._load (node:internal/modules/cjs/loader:1263:12) 2026-04-28T22:07:08.104653815Z [err] at Module.load (node:internal/modules/cjs/loader:1441:32) 2026-04-28T22:07:08.104655930Z [inf] [STARTUP] OPENROUTER_API_KEY is set (length=73) 2026-04-28T22:07:08.104657121Z [err] at Object. (/app/telegram-bot.js:206:8) 2026-04-28T22:07:08.104658270Z [err] npm warn config production Use --omit=dev instead. 2026-04-28T22:07:08.104664519Z [inf] [STARTUP] Using model: openai/gpt-4o-mini 2026-04-28T22:07:08.104664921Z [err] at TracingChannel.traceSync (node:diagnostics_channel:328:14) 2026-04-28T22:07:08.104669038Z [inf] 2026-04-28T22:07:08.104673361Z [err] node:events:497 2026-04-28T22:07:08.104674310Z [err] at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) 2026-04-28T22:07:08.112023715Z [err] at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5) 2026-04-28T22:07:08.112027172Z [err] at node:internal/main/run_main_module:36:49 2026-04-28T22:07:08.112031087Z [err] Emitted 'error' event on Server instance at: 2026-04-28T22:07:08.112034123Z [err] at emitErrorNT (node:net:1976:8) 2026-04-28T22:07:08.112037298Z [err] at process.processTicksAndRejections (node:internal/process/task_queues:89:21) { 2026-04-28T22:07:08.112040623Z [err] code: 'EADDRINUSE', 2026-04-28T22:07:08.112044649Z [err] errno: -98, 2026-04-28T22:07:08.112048316Z [err] syscall: 'listen', 2026-04-28T22:07:08.112051732Z [err] address: '::', 2026-04-28T22:07:08.112055547Z [err] port: 3001 2026-04-28T22:07:08.112059520Z [err] } 2026-04-28T22:07:08.112066961Z [err] 2026-04-28T22:07:08.112070468Z [err] Node.js v22.22.2 2026-04-28T22:07:08.541609658Z [inf] Starting Container 2026-04-28T22:07:15.848284474Z [inf] Stopping Container 2026-04-28T22:07:16.693325513Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-28T21_59_42_279Z-debug-0.log 2026-04-28T22:07:16.693448853Z [err] npm error path /app 2026-04-28T22:07:16.693454873Z [err] npm error command failed 2026-04-28T22:07:16.693466352Z [err] npm error signal SIGTERM 2026-04-28T22:07:16.693472327Z [err] npm error command sh -c sh -c 'node dashboard/server.js & node telegram-bot.js & wait' 2026-04-28T22:08:00.242890999Z [inf] Starting Container 2026-04-28T22:08:00.471459167Z [err] at Function._load (node:internal/modules/cjs/loader:1263:12) 2026-04-28T22:08:00.471459941Z [err] ^ 2026-04-28T22:08:00.471470329Z [err] at TracingChannel.traceSync (node:diagnostics_channel:328:14) 2026-04-28T22:08:00.471472850Z [err] 2026-04-28T22:08:00.471477821Z [err] at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) 2026-04-28T22:08:00.471481246Z [err] Error: listen EADDRINUSE: address already in use :::3001 2026-04-28T22:08:00.471489420Z [err] at Server.setupListenHandle [as _listen2] (node:net:1940:16) 2026-04-28T22:08:00.471492731Z [err] at Server.listen (node:net:2102:7) 2026-04-28T22:08:00.471499351Z [err] at Object. (/app/telegram-bot.js:206:8) 2026-04-28T22:08:00.471501841Z [inf] > start 2026-04-28T22:08:00.471505055Z [err] at Module._compile (node:internal/modules/cjs/loader:1705:14) 2026-04-28T22:08:00.471511604Z [err] at Object..js (node:internal/modules/cjs/loader:1838:10) 2026-04-28T22:08:00.471513615Z [err] at listenInCluster (node:net:1997:12) 2026-04-28T22:08:00.471518038Z [inf] > sh -c 'node dashboard/server.js & node telegram-bot.js & wait' 2026-04-28T22:08:00.471521291Z [err] at Module.load (node:internal/modules/cjs/loader:1441:32) 2026-04-28T22:08:00.471527631Z [inf] 2026-04-28T22:08:00.471535960Z [err] npm warn config production Use --omit=dev instead. 2026-04-28T22:08:00.471537965Z [inf] 🤖 OpenClaw web interface running on http://0.0.0.0:3001 2026-04-28T22:08:00.471545821Z [inf
2 months ago
Are you running two scripts within the same service? If so, you will either need to explicitly make one of the subservices listen to a different port from the other one (eg, you can do PORT + 1) or you'll need to separate them into two services in Railway.
2 months ago
so this is the last few days I decided to put here i'm not sure what happend. I worked perfectly about 12 hours a go
Attachments
0x5b62656e5d
Are you running two scripts within the same service? If so, you will either need to explicitly make one of the subservices listen to a different port from the other one (eg, you can do PORT + 1) or you'll need to separate them into two services in Railway.
2 months ago
I'm not sure how that happend either
2 months ago
just openrouter api
2 months ago
but since then it's been a mess fixing it
jordanjayhays-cpu
but since then it's been a mess fixing it
2 months ago
I’d suggest reverting your deployment to a previous known working deployment in Railway (click the 3 dots on older deployments), and create a branch in Github for your Openrouter API patches so it doesn’t affect production. Once you’ve verified that the code works locally, then you should merge it into your main branch.
2 months ago
okay will try
2 months ago
still trying
2 months ago
it's late i will stop trying for now I don't know what to do anymore. I think it's a human error at this point (me)