N8n 1.68/1.69 @ docker - Telegram Webhook Input Buffers issue

Questions
1

My workflow works, but sometimes it feels like something randomly breaks and it just gets stuck in a loop of

{
  "errorMessage": "Input buffers must have the same byte length",
  "errorDetails": {},
  "n8nDetails": {
    "n8nVersion": "1.69.0 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "RangeError: Input buffers must have the same byte length",
      "    at WebhookContext.webhook (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/TelegramTrigger.node.js:210:35)",
      "    at Workflow.runWebhook (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:660:15)",
      "    at Object.executeWebhook (/usr/local/lib/node_modules/n8n/dist/webhooks/webhook-helpers.js:144:33)"
    ]
  }
}

This behavior seems to persist on 1.67.1, 1.68 and 1.69. I already tried clearing the pending updates via Telegram API as well as recreating the bot token, but this issue keeps returning and unfortunately means very little to me given how opaque the process is being.

If anyone’s got any ideas, I’d be very grateful!

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

After having the workflow disabled for two days, it’s now working again after being enabled.

Still incredibly frustrating not knowing what the actual cause is, and I’m practically counting down the minutes until it breaks again.

4

Hi @hxii ! The error is not the clearest, but the issue seems to be that the x-telegram-bot-api-secret-token header does not match the secret defined in the Telegram Trigger Node. Since in this case the webhook responds with status 500, Telegram probably retries the webhook. After you disabled the workflow, telegram gave up on retrying. I created a bug report about this and we are tracking this issue internally as NODE-2114.

1 Like
5

New version [email protected] got released which includes the GitHub PR 12018.