I'm using Node-red installed on a Ubuntu virtual private server to interface with several Telegram bots. Thus far I have used polling mode. I would like to change to webhooks, because of the several advantages over polling mode.
After some struggle, I managed to get one bot working via webhook, so my reverse proxy with Apache and SSL certification is working.
I'm using the following settings in the Telegram node:
Bot host: webhook.wernersmook.co.za
Bot path:
Public bot port: 8443
Local bot port: 1881
Apache is setup for the reverse proxy from port 8443 to port 1881.
Could not use 1880 for local bot port as Node-red is already running on it and it caused immediate restart loop.
The problem I have is that the same port collision problem occured when I changed my second bot to webhook mode, using the same settings.
As I understand, it is not possible for the two different bot nodes to listen on the same port. I find it hard to believe that each bot will have to listen on its own port as this will require lots of setup and admin, also to setup the reverse proxies.
I already tried different "bot path" settings for the two bots on webhook, but it did not solve the problem.
I would really like to find out whether there is a more feasible option regarding this. So far I'm getting the impression that few people are using Telegram webhooks in Node-red, as I'm struggling to find info on the internet.
ChatGPT seem to be unsure/confused about this as it remain to suggest local bot port to be the same as Node-red at 1880. It suggested the unique-port-per-bot option, but it does not seem to be a practical, scalable option to me.
Looking forward to any suggestion regarding this matter.
