# Telegram node-red is no longer working

**URL:** <https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143>\
**Category:** General\
**Tags:** telegram\
**Created:** [11 July 2019 02:43 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143 "2019-07-11T02:43:43Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arm555](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@Arm555](https://discourse.nodered.org/u/Arm555)\
**Post date:** [11 July 2019 02:43 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/1 "2019-07-11T02:43:43Z")

</div>

I am getting these errors. Not sure what it means. I have an inject node that I am using to test and I get this message after a few seconds that the message goes through. I also have pihole on a docker, but on the query log i see it went through ?

`"Error: EFATAL: Error: getaddrinfo EAI_AGAIN api.telegram.org api.telegram.org:443"`

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [11 July 2019 02:52 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/2 "2019-07-11T02:52:42Z")

</div>

Did it work before ? I would suggest to report the problem on github instead.

---

<div class="post-metadata">

**Author:** ![Arm555](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@Arm555](https://discourse.nodered.org/u/Arm555)\
**Post date:** [11 July 2019 02:54 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/3 "2019-07-11T02:54:44Z")

</div>

Yes it did. I will report this.

---

<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:** [11 July 2019 06:00 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/4 "2019-07-11T06:00:04Z")

</div>

> [@Arm555](#):
>
> EAI\_AGAIN

A quick internet search turned up the likely answer.

> <https://stackoverflow.com/questions/40182121/whats-the-cause-of-the-error-getaddrinfo-eai-again>

You have a DNS problem.

---

<div class="post-metadata">

**Author:** ![Arm555](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@Arm555](https://discourse.nodered.org/u/Arm555)\
**Post date:** [24 July 2019 04:01 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/5 "2019-07-24T04:01:46Z")

</div>

Thank you for the response. I think in fact that my problem may be caused by something else as I tried to disable my PiHole (which I thought that was causing the problem) and that didn’t fix the problem.

I will try to make sure my Node Red Docker can ping somewhere outside and come back with more details on things I’ve tried.

---

<div class="post-metadata">

**Author:** ![craigcurtin](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@craigcurtin](https://discourse.nodered.org/u/craigcurtin)\
**Post date:** [24 July 2019 04:14 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/6 "2019-07-24T04:14:02Z")

</div>

Where does your DNS point to on the NR machine ?

Presumably the PiHole - if you are running that on Docker then i would look for some issues between Host and Network conenctivity - which can be tricky with Docker

From the NR machine try and ping a google address

ping 8.8.8.8 or 8.8.4.4

If that works then try and ping [NS.google.com](http://NS.google.com)

If that works then you do not have a DNS problem - move on to the next level

Craig

---

<div class="post-metadata">

**Author:** ![Arm555](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@Arm555](https://discourse.nodered.org/u/Arm555)\
**Post date:** [24 July 2019 11:37 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/8 "2019-07-24T11:37:56Z")

</div>

Thanks! Will try that. I actually turned off pihole just to see if the problem would be fixed and noticed the problem persists.

One thing I was going to try was to re add the telegram bot to see if that fixes. Or even make up another bot and see what happens but I will try what you mentioned.

I tried going to the console for node red via portainer and doing a ping but it told me that command doesn’t work. Did you mean that?

---

<div class="post-metadata">

**Author:** ![Arm555](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@Arm555](https://discourse.nodered.org/u/Arm555)\
**Post date:** [24 July 2019 11:39 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/10 "2019-07-24T11:39:39Z")

</div>

Thank you. I did post it on GitHub a few weeks ago. Will follow up again on that thread see if anyone has familiarity with that error.

---

<div class="post-metadata">

**Author:** ![Arm555](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@Arm555](https://discourse.nodered.org/u/Arm555)\
**Post date:** [4 August 2019 19:38 UTC](https://discourse.nodered.org/t/telegram-node-red-is-no-longer-working/13143/11 "2019-08-04T19:38:54Z")

</div>

Hey thanks again for the help. It is now working. I think it was a DNS issue that after changing my PiHole to another machine and fixing other DNS issues I had somehow Telegram node fixed “itself”.