ProcessExitedBeforeReadyError: Process exited with code 127 before becoming ready. Waiting for: port 18789 (TCP)

[maxmillionbeatz]

ProcessExitedBeforeReadyError: Process exited with code 127 before becoming ready. Waiting for: port 18789 (TCP)

This is the second time this happens. Usually right after editing clawdbot.json

[Jexep]

I got the same error and just changed from "npm run deploy" to "npx wrangler deploy"
Also I added one Variable CLAWDBOT_GATEWAY_TOKEN duplicate with MOLTBOT_GATEWAY_TOKEN (Seems like they didn't change all the name)

and it worked 😅 not sure why though.

[tanushmahalka]

If you have telegram enabled,

// Telegram configuration
if (process.env.TELEGRAM_BOT_TOKEN) {
    config.channels.telegram = config.channels.telegram || {};
    config.channels.telegram.botToken = process.env.TELEGRAM_BOT_TOKEN;
    config.channels.telegram.enabled = true;
    config.channels.telegram.dm = config.channels.telegram.dm || {};
    config.channels.telegram.dmPolicy = process.env.TELEGRAM_DM_POLICY || 'pairing';
}

In start-moltbot.sh, remove config.channels.telegram.dm = config.channels.telegram.dm || {};.
It seems like openclaw ( previously molt ) might have removed that as a key.

It looks like this for me, after removing:

if (process.env.TELEGRAM_BOT_TOKEN) {
    config.channels.telegram = config.channels.telegram || {};
    config.channels.telegram.botToken = process.env.TELEGRAM_BOT_TOKEN;
    config.channels.telegram.enabled = true;
    config.channels.telegram.dmPolicy = process.env.TELEGRAM_DM_POLICY || 'pairing';
}

This seemed to solve it for me.

[futureCreator]

I resolved this. It worked for me.
#80 (comment)

[mervyns]

If you have telegram enabled,

// Telegram configuration
if (process.env.TELEGRAM_BOT_TOKEN) {
    config.channels.telegram = config.channels.telegram || {};
    config.channels.telegram.botToken = process.env.TELEGRAM_BOT_TOKEN;
    config.channels.telegram.enabled = true;
    config.channels.telegram.dm = config.channels.telegram.dm || {};
    config.channels.telegram.dmPolicy = process.env.TELEGRAM_DM_POLICY || 'pairing';
}

In start-moltbot.sh, remove config.channels.telegram.dm = config.channels.telegram.dm || {};. It seems like openclaw ( previously molt ) might have removed that as a key.

It looks like this for me, after removing:

if (process.env.TELEGRAM_BOT_TOKEN) {
    config.channels.telegram = config.channels.telegram || {};
    config.channels.telegram.botToken = process.env.TELEGRAM_BOT_TOKEN;
    config.channels.telegram.enabled = true;
    config.channels.telegram.dmPolicy = process.env.TELEGRAM_DM_POLICY || 'pairing';
}

This seemed to solve it for me.

If the dm issue persists, It's cos the code

 if (process.env.TELEGRAM_BOT_TOKEN) {
     config.channels.telegram = config.channels.telegram || {};
     config.channels.telegram.botToken = process.env.TELEGRAM_BOT_TOKEN;
     config.channels.telegram.enabled = true;
     config.channels.telegram.dmPolicy = process.env.TELEGRAM_DM_POLICY || 'pairing';
}

doesn't delete keys in a created object.

There might be a need to overwrite it like this

if (process.env.TELEGRAM_BOT_TOKEN) {
    config.channels.telegram = {
        botToken: process.env.TELEGRAM_BOT_TOKEN,
        enabled: true,
        dmPolicy: process.env.TELEGRAM_DM_POLICY || 'pairing'
    };
}

[sidharthachatterjee]

Fixed this in the script, thanks for reporting!