Telegram node stuck in testing/executing on self-hosted n8n 2.1.4

Questions
1

I’m having an issue with the Telegram node in n8n where it gets permanently stuck in Testing / Loading / Executing and eventually times out.
I’m running self-hosted n8n v2.1.4
Telegram API keys are valid
I also tested with older bot tokens that were previously working without issues
The workflow never errors out explicitly, it just hangs indefinitely during execution
This setup was working fine before and stopped working without any intentional changes on my side
At this point I can’t identify what broke or why the Telegram API is no longer responding through the Telegram node. Other parts of n8n seem to be functioning normally.
Has anyone run into this recently or knows what could cause the Telegram node to hang like this in a self-hosted setup?

image
image592×520 19.4 KB

ey! The fastest way to find solutions is by using the :magnifying_glass_tilted_right: search function at the upper right.
If your question hasn’t been asked before, please follow the template below. Skip the questions that are not relevant to you. →

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

How is your n8n instance set up? Are you using a reverse proxy to make it publicly accessible?

The Telegram Trigger node can only register one Webhook with the Telegram API server at a time and can theoretically get stuck when running in production and is being tested at the same time. This can be fixed be deactivating the workflow sometimes. However, its more likely that your reverse proxy config is the issue here.

You can read more about it here:

3

I’m using a Hostinger VPS + Server Avatar. Domain is through CloudFlare. This worked before. Any tips on how this can be solved?

4

UPDATE: Cause: Broken IPv6 routing. Node.js prefers IPv6 → TLS handshake hangs for api.telegram.org.

Fix:

NODE_OPTIONS=--dns-result-order=ipv4first

Restart n8n.
No nginx / Cloudflare changes needed.

2 Likes
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.