Hi everyone,
I’m running a self-hosted instance of n8n on Hostinger shared hosting (not VPS, no terminal/SSH access).
The Telegram Trigger node used to work fine before the recent update. Now, whenever I try to add my bot token, the node freezes with no error message.
I’ve tested multiple bots, cleared caches, and even manually set the webhook via the Telegram API — no success. The webhook doesn’t trigger, and the node hangs.
My guess is it’s failing on api.telegram.org but without terminal access, I can’t confirm if it’s DNS, outbound blocks, or some other issue.
Has anyone faced this on shared hosting or found a workaround for this kind of frozen credential behavior?
Appreciate any help or insight ![]()
The issue is likely related to shared hosting restrictions blocking outgoing requests to Telegram’s API. Without terminal access, you can try this: Use a Function node to test connectivity by making a simple HTTP GET request to `https://api.telegram.org/bot<YOUR_TOKEN>/getMe`. If this fails, it confirms the hosting provider is blocking the connection. You might need to switch to a VPS or use a proxy service that allows Telegram API access.