-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telegram trigger don't working #9824
Comments
Hey @suelliton Which version of n8n are you using and what Node version? Have you tried using the container? I have just tried with 1.46.0 and it appears to be working ok for me. |
Docker version 26.1.4, build 5650f9b |
how i update for newest version? |
@Joffcom Not everyone encounters this situation, you can refer to the following two reddit discussion articles. I personally encountered it. I am currently using the latest version of n8n and still have problems. Thank you! The error message is n8n log is The problem is that if you use curl https://api.telegram.org/bot<your_bot_token>/getMe It can get the response. edited I try Version: 1.47.0, it still not resolved the issue. |
It sounds like this could be related to the ipv6 issue that was reported on the support forum which was highlighted more by the change to node 20. Sadly Reddit is not an official support platform so we often miss things posted there although I do try and check out posts when I have time. I would recommend keeping an eye on this post as it looks like it could be related: https://community.n8n.io/t/errors-since-last-n8n-update-1-44-1/48238/24 |
@Joffcom Thanks for your reply. At least we can see the clues and hope for solving this issue. |
@Joffcom I just test n8nio/n8n:enable-keepAlive, I can successfully save telegram Credentials and perform Telegram trigger, it seems to solve this issue, but I may need to do a longer test. |
Fix got released with |
@janober Can confirmed n8nio/n8n:1.47.1 works as well as n8nio/n8n:enable-keepAlive, so I think this issue could be closed? |
@suelliton They mentioned n8n:keepAlive in https://community.n8n.io/t/errors-since-last-n8n-update-1-44-1/48238/24 |
@suelliton The keepalive fix from what I understand didn't help the users with the issue but the change made in the PR we went with was a lot better. When you say it doesn't work with 1.47.1 can you be more specific and share the error you are seeing? It could be that you are seeing 2 different issues one that has been fixed and another that is local to your configuration. |
@Joffcom In this latest version 1.47.1, nothing worked, I simply didn't receive the message trigger, at all, neither when active nor in "test step" mode, but when I ran it with this keepalive version it worked, soon I will do more tests with both versions |
@suelliton Did you try using a webhook node outside of the telegram to see if that works? We know that this release has fixed the issue for most users. Have you tried setting |
@Joffcom the works is intermitent |
@Joffcom im hospeding the application 8n8 in oracle cloud, and i have the same error with telegram trigger, dont works, im configured the variable NODEJS_PREFER_IPV4=true in docker compose, im using a balancer with a certificate of test ssl. using this command curl -F "url=https://my-ip:443/n8n/webhook/telegram" https://api.telegram.org/bot/setWebhook |
@Joffcom using the version 1.47.1, i have this error, while tap test workspace : Telegram Trigger: Bad Request: bad webhook: Webhook can be set up only on ports 80, 88, 443 or 8443 |
Hey @suelliton, That sounds like Telegram is unhappy with the url being sent. What is the webhook_url set to for your instance and does it contain a port? |
@Joffcom I've tried thousands of possible ways, it doesn't work, now I'm trying to run the tunnel via docker-compose but I can't, with the tunnel some requests still work without it, it doesn't work |
Hey @suelliton, Sadly I am still not able to reproduce after testing on multiple environments. Are you able to share the exact configuration you are using? Based on the last error it looks like a config issue rather than an n8n issue but until we can see and test your exact config it is hard to suggest what may fix this. |
@Joffcom I give up, I've wasted too much time |
Bug Description
Telegram Trigger don't works, only in "test workspace" mode, and sometimes dont work too, i tested using npx execution and pm2, the twos have a error.
To Reproduce
Only setting a trigger and waiting a event onmessage, wait indefiniting times and dont works, sometimes the trigger receives all messages triggereds in telegram bot but only in mode of "test workspace" or "test step"
Expected behavior
The trigger running and receiving the messages of telegram bot.
Operating System
Linux Mint
n8n Version
21
Node.js Version
latest
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: