# How to re-enable telegram receiver after network outage?

**URL:** <https://discourse.nodered.org/t/how-to-re-enable-telegram-receiver-after-network-outage/57057>\
**Category:** General\
**Created:** [22 January 2022 15:26 UTC](https://discourse.nodered.org/t/how-to-re-enable-telegram-receiver-after-network-outage/57057 "2022-01-22T15:26:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![loeten](https://avatars.discourse-cdn.com/v4/letter/l/b38774/32.png) [@loeten](https://discourse.nodered.org/u/loeten)\
**Post date:** [22 January 2022 15:26 UTC](https://discourse.nodered.org/t/how-to-re-enable-telegram-receiver-after-network-outage/57057/1 "2022-01-22T15:26:41Z")

</div>

Dear all, last year I felt the problem is solved, but came again now: After having a network outage (that may happen any time), the Telegram receiver on my raspi stops. The Telegram sender continues sending when triggered later the day. Is there a way or a workaround of "re-encouraging" the receiver to try to receive, other that reboot the raspi via crontab? Some details from the syslog:

```auto
$ sudo cat /var/log/syslog|grep telegram
Jan 22 03:03:33 watchdog Node-RED[435]: 22 Jan 03:03:33 - [warn] [telegram bot:xxx] EFATAL: Error: read ETIMEDOUT
Jan 22 03:03:33 watchdog Node-RED[435]: 22 Jan 03:03:33 - [warn] [telegram bot:xxx] Unknown error. Trying again.
Jan 22 03:04:14 watchdog Node-RED[435]: 22 Jan 03:04:14 - [warn] [telegram bot:xxx] EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
Jan 22 03:04:14 watchdog Node-RED[435]: 22 Jan 03:04:14 - [warn] [telegram bot:xxx] Network connection may be down. Trying again.
Jan 22 03:04:54 watchdog Node-RED[435]: 22 Jan 03:04:54 - [warn] [telegram bot:xxx] EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org
Jan 22 03:04:54 watchdog Node-RED[435]: 22 Jan 03:04:54 - [warn] [telegram bot:xxx] Network connection may be down. Trying again.
Jan 22 15:02:37 watchdog Node-RED[425]: Sat, 22 Jan 2022 15:02:37 GMT node-telegram-bot-api deprecated In the future, content-type of files you send will default to "application/octet-stream". See https://github.com/yagop/node-telegram-bot-api/blob/master/doc/usage.md#sending-files for more information on how sending files has been improved and on how to disable this deprecation message altogether. at .node-red/node_modules/node-red-contrib-telegrambot/telegrambot/99-telegrambot.js:1467:50

```

---

<div class="post-metadata">

**Author:** ![Andrei](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andrei/32/10446_2.png) [@Andrei](https://discourse.nodered.org/u/Andrei)\
**Post date:** [29 January 2022 19:34 UTC](https://discourse.nodered.org/t/how-to-re-enable-telegram-receiver-after-network-outage/57057/2 "2022-01-29T19:34:01Z")

</div>

Apparently the node developer is considering to implement a feature to restart the node in the runtime.

> <https://github.com/windkh/node-red-contrib-telegrambot/issues/228>
>
> The telegram bot should be stoppable and re-startable during runtime.
> This can …be useful when reconfiguring the token or when the network gets lost.
> 
> \--\> Nodes must dynamically register at the config node
> \--\> reply node must be removed first see https://github.com/windkh/node-red-contrib-telegrambot/issues/227
> \--\> control node needs to be added

---

<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:** [30 March 2022 19:34 UTC](https://discourse.nodered.org/t/how-to-re-enable-telegram-receiver-after-network-outage/57057/3 "2022-03-30T19:34:17Z")

</div>

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