Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Telegram channel silently fails to connect on fresh Fly.io deploy (v2026.3.23) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#57323•Fetched 2026-04-08 01:51:00
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
InkviInkvi
Participants
InkviInkvivincentkocvincentkoc
Assignees
vincentkocvincentkoc
Timeline (top)
assigned ×1commented ×1

On a fresh Fly.io deploy, the Telegram channel is marked as "configured, enabled automatically" in gateway startup logs, but never actually connects or polls for updates. No error is logged. The gateway starts normally, port 3000 binds, other plugins (diagnostics-otel) load successfully, but Telegram is completely silent.

Error Message

On a fresh Fly.io deploy, the Telegram channel is marked as "configured, enabled automatically" in gateway startup logs, but never actually connects or polls for updates. No error is logged. The gateway starts normally, port 3000 binds, other plugins (diagnostics-otel) load successfully, but Telegram is completely silent.

Root Cause

On a fresh Fly.io deploy, the Telegram channel is marked as "configured, enabled automatically" in gateway startup logs, but never actually connects or polls for updates. No error is logged. The gateway starts normally, port 3000 binds, other plugins (diagnostics-otel) load successfully, but Telegram is completely silent.

RAW_BUFFERClick to expand / collapse

Description

On a fresh Fly.io deploy, the Telegram channel is marked as "configured, enabled automatically" in gateway startup logs, but never actually connects or polls for updates. No error is logged. The gateway starts normally, port 3000 binds, other plugins (diagnostics-otel) load successfully, but Telegram is completely silent.

Environment

  • OpenClaw version: 2026.3.23 (also reproduced on 2026.3.28 via latest)
  • Platform: Fly.io, shared-cpu-2x, 4GB RAM
  • Deployment: Docker image ghcr.io/openclaw/openclaw:2026.3.23
  • Process command: node dist/index.js gateway --port 3000 --bind lan
  • Config: channels.telegram.enabled: true, dmPolicy: "allowlist", allowFrom: ["<user_id>"]
  • TELEGRAM_BOT_TOKEN is set as a Fly secret and verified present in env

Steps to Reproduce

  1. fly apps create my-openclaw
  2. fly volumes create openclaw_data --size 1 --region iad
  3. Set secrets including TELEGRAM_BOT_TOKEN
  4. fly deploy with standard fly.toml
  5. Push openclaw.json with Telegram channel config via SSH
  6. Wait for gateway to fully start (port 3000 listening, ~5-10 minutes)
  7. Send message to bot on Telegram — no reply

Expected Behavior

Telegram long-polling should start and the bot should respond to messages.

Actual Behavior

  • Gateway logs show: [gateway] auto-enabled plugins: - Telegram configured, enabled automatically.
  • Gateway binds port 3000 successfully
  • diagnostics-otel plugin loads: [plugins] diagnostics-otel: logs exporter enabled (OTLP/Protobuf)
  • No [telegram] subsystem logs appear at all — no connection, no polling, no errors
  • Bot does not respond to messages
  • /tmp/openclaw/openclaw-*.log contains zero references to Telegram except the "auto-enabled" message

Additional Context

  • On an earlier boot (before gateway port issue was resolved), we briefly saw Telegram working — the bot replied to a message. After a restart, Telegram never reconnected.
  • A separate instance (Jenna) deployed on March 24 from the same image works correctly, but that instance has persistent volume state from the original deploy.
  • Tried: clearing JITI cache (rm -rf /tmp/jiti), multiple restarts, fresh ocm create, pinned image tag — none fixed it.
  • The first boot crashes with "Missing config" (no --allow-unconfigured), which may corrupt Telegram plugin state. However, adding --allow-unconfigured and fresh deploys didn't help either.

extent analysis

Fix Plan

To resolve the issue with the Telegram channel not connecting or polling for updates, we need to ensure that the TELEGRAM_BOT_TOKEN is correctly set and the Telegram plugin is properly configured. Here are the steps to follow:

  • Verify that the TELEGRAM_BOT_TOKEN secret is correctly set in the Fly.io environment.
  • Check the openclaw.json configuration file to ensure that the Telegram channel is enabled and properly configured.
  • Add logging to the Telegram plugin to debug the issue.

Example Code

To add logging to the Telegram plugin, you can modify the telegram.js file in the plugins directory:

// plugins/telegram.js
const logger = require('../logger');

// ...

async function start() {
  logger.info('Telegram plugin starting...');
  // ...
}

async function pollUpdates() {
  logger.info('Polling for updates...');
  // ...
}

// ...

You can also add error handling to catch any exceptions that may be occurring:

// plugins/telegram.js
const logger = require('../logger');

// ...

async function start() {
  try {
    // ...
  } catch (error) {
    logger.error('Error starting Telegram plugin:', error);
  }
}

async function pollUpdates() {
  try {
    // ...
  } catch (error) {
    logger.error('Error polling for updates:', error);
  }
}

// ...

Verification

To verify that the fix worked, you can check the logs for the Telegram plugin and ensure that it is connecting and polling for updates correctly. You can also test the bot by sending a message and verifying that it responds correctly.

Extra Tips

  • Make sure to check the Fly.io environment variables and secrets to ensure that they are correctly set.
  • Verify that the openclaw.json configuration file is correctly formatted and that the Telegram channel is enabled and properly configured.
  • If you are still experiencing issues, try enabling debug logging for the Telegram plugin to get more detailed information about the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#tool integration#LLM response#prompt template#agent execution#callback error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Telegram channel silently fails to connect on fresh Fly.io deploy (v2026.3.23) [1 comments, 2 participants]