I’m having this problem. I created a bot on Telegram. I connected to N8N. The connection was successful. I added a node trigger message. I clicked save, then publish. I sent a message on Telegram in the newly created bot, and there was no response from N8N.
This might be an issue with your Hostinger setup. On the N8N cloud plan, telegram always works for me. Is the connection being allowed through to hostinger from telegram or vice versa?
Hey 
@Andrzej_Sojka !
Did you set your WEBHOOK_URL env variable as well?
how to check if the connection is allowed from hostinger to telegram or what do you mean?
I didn’t configure anything like that. The only thing that works on N8N’s end is the Telegram connection, and on Hostigner’s end, nothing at all.
If you go to hostinger can you see any settings about the instance like connections? If so could you tell us what you are able to change or acsess?
I faced the same problem. I’ve been using telegram triggers in n8n on Hostinger before and it worked. But recently it just stopped to listen for on-message triggers from telegram bot. At the same time, I can send messages to my bot. The problem is only with trigger to get the message. I tried to create another bot and change credentials, but it didn’t work. I didn’t change any setting on VPS. I found out that Telegram blacklisted hostinger URLs.
I created workaround through HTTP request on schedule to get the messages and filter by timings, but it is not right solution
I have the same issue. I admit I am a novice at n8n but not a novice at programming and these tools.
I did create a first bot on telegram. Nothing worked.
I deleted the bot and created a new one, it worked fine.
I made some modifications to the workflow and …nothing works anymore. It just doesn’t receive the “On message” call. No matter how many messages I sent.
I see the issue has also come down on Telegram huh? WhatsApp has been down for a whole week. I’m moving to Elestio.
The errors started with WhatsApp and Hostinger is still trying to fix the issue.
@henryford yea, this has escalated to a hostinger issue,
hasn’t this been solved yet?
Nope move to n8n cloud or elestio
Hi! The same things! have you found the solution?
