N8n Telegram Trigger ETIMEDOUT

Hi n8n Community! I am a recent convert from make to n8n self-hosted. So far it’s going great, but I am having an issue with the telegram bot trigger :confused:

When I try to setup a Telegram credential and input the bot token it does the test connection and immediately comes back with the ETIMEDOUT error. I have a domain pointed to my n8n instance using a Cloudflared tunnel. I’ve defined the domain as an ENV variable for webhooks url and host. I’m at my wits end on how to get it to connect to Telegram. All other nodes that I’ve setup so far work completely fine (Discord, Google sheets, ClickUp), so instance is definitely connected to the Internet.

I am able to run curl https://api.telegram.org/bot<your_bot_token>/getMe and get a response just fine if I do it through the container terminal, or even using the ‘Execute command’ node in n8n. But the Telegram nodes don’t work, somehow the n8n backend (https://domain.abc/rest/credentials/test )request to Telegram is not getting through.

I’m running n8n in a Proxmox LXC container (no docker), so it’s a bit harder to find relevant information, but I would really prefer to stick with this setup without having to go the Docker route.

  • n8n version: 1.39.1
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: Proxmox LXC container with Debian 12

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:

Hey @kreatiff,

Welcome to the community :raised_hands:

We recommend the docker approach as that is what we test and it includes the extra packages we need to fully run that you may not have without it like git.

Looking at the error if you are seeing a timeout error it would point to a network issue, What happens if you try to access the /getMe url from an http request node does that work?

1 Like

Hi Jon, thanks for getting back to me. I think there must’ve been some strange misconfig on the LXC container. I ended up redeploying a new one and installing n8n again and everything is working fine :slight_smile:

1 Like