# Telegram bot issue with node\_red version 3.0.2

**URL:** <https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482>\
**Category:** General\
**Created:** [13 February 2024 11:22 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482 "2024-02-13T11:22:17Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![joey\_ind](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@joey\_ind](https://discourse.nodered.org/u/joey_ind)\
**Post date:** [13 February 2024 11:22 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/1 "2024-02-13T11:22:17Z")

</div>

Hi,  
I need support to install telegram bot for nodered version 16.17.

I was trying install the latest version of telegram bot but the same was throwing up a " polling error".

Please help

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [13 February 2024 11:37 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/2 "2024-02-13T11:37:43Z")

</div>

> [@joey\_ind](#):
>
> nodered version 16.17.

The latest version of Node-RED is v3.1.5, are you running Home Assistant!? (if so, you might want to open an issue o their forum.) or is `16.16` the version of node.js you are running?

How did you try to do the node's install?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [13 February 2024 11:38 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/3 "2024-02-13T11:38:31Z")

</div>

Please indicate which node you installed and some more details of the error if you would like help from the forum. Thanks.

---

<div class="post-metadata">

**Author:** ![joey\_ind](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@joey\_ind](https://discourse.nodered.org/u/joey_ind)\
**Post date:** [14 February 2024 04:24 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/4 "2024-02-14T04:24:26Z")

</div>

I am sorry for the wrong information shared.

Node red version v3.0.2  
Node.js version v16.17.0

Node installed : node -red-contrib-telegrambot, v 15.1.9

Error received upon using receiver node : polling error

"EFATAL: Error: write EPROTO 6472:error:1408F10B:SSL routines:ssl3\_get\_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3\_record.c:332:"

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [14 February 2024 11:31 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/5 "2024-02-14T11:31:16Z")

</div>

While not the same error you are seeing, there is an issue on [node-red-contrib-telegrambot GitHub page](https://github.com/windkh/node-red-contrib-telegrambot/issues/343) so I would suggest upgrading NR to the latest version (3.1.5) and node.js to v18.15.2 and testing again.

If you still have an issue then create a small test flow using that node that recreates the error and export the flow and paste it to a reply along with the NR log from startup to the error.

---

<div class="post-metadata">

**Author:** ![joey\_ind](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@joey\_ind](https://discourse.nodered.org/u/joey_ind)\
**Post date:** [15 February 2024 09:27 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/6 "2024-02-15T09:27:33Z")

</div>

Oops! I gotta big application running on the current version. Upgrading would mean re-doing the entire thing ..

Any alternate nodes which might accomplish the task of sending simple notifications to telegram?

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [15 February 2024 09:33 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/7 "2024-02-15T09:33:33Z")

</div>

> [@joey\_ind](#):
>
> Upgrading would mean re-doing the entire thing ..

Why?

> [@joey\_ind](#):
>
> Any alternate nodes which might accomplish the task of sending simple notifications to telegram?

Well you can search the [flows tab](https://flows.nodered.org/) as easy as I could and you would have a better idea if anything you find could help you better than anyone else could...

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [15 February 2024 09:34 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/8 "2024-02-15T09:34:44Z")

</div>

> [@joey\_ind](#):
>
> I gotta big application running on the current version. Upgrading would mean re-doing the entire thing

um, not really. it _should_ be as simple as running `sudo npm install -g --unsafe-perm node-red@3.1.5` then start up and go!

Just make a backup of `.node-red` (or where-ever your node-red flows user dir is) before you start if you are worried

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [15 May 2024 09:35 UTC](https://discourse.nodered.org/t/telegram-bot-issue-with-node-red-version-3-0-2/85482/9 "2024-05-15T09:35:16Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.