# Help with Telegram integration error

**URL:** <https://discourse.nodered.org/t/help-with-telegram-integration-error/59753>\
**Category:** General\
**Created:** [12 March 2022 11:59 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753 "2022-03-12T11:59:18Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![patofoto](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/patofoto/32/25792_2.png) [@patofoto](https://discourse.nodered.org/u/patofoto)\
**Post date:** [12 March 2022 11:59 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/1 "2022-03-12T11:59:18Z")

</div>

I am getting an `RequestError: Error: getaddrinfo ENOTFOUND api.telegram.org` when trying to set u to run on boot. It all works ok if I start it manually. Any suggestions?. I have a Telegram bot integration to send me a message when an event occurs.

```auto
❯ which node-red
/opt/homebrew/bin/node-red
❯ pm2 start /opt/homebrew/bin/node-red -- -v
[PM2] Applying action restartProcessId on app [node-red](ids: [0])
[PM2] [node-red](0) ✓
[PM2] Process successfully started
┌─────┬──────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼──────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 1 │ .node-red │ default │ 0.0.1 │ fork │ N/A │ 0 │ 15 │ stopped │ 0% │ 0b │ server │ disabled │
│ 0 │ node-red │ default │ N/A │ fork │ 53410 │ 0 │ 75 │ stopped │ 0% │ 0b │ server │ disabled │
└─────┴──────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
❯ pm2 logs node-red
[TAILING] Tailing last 15 lines for [node-red] process (change the value with --lines option)
/Users/server/.pm2/logs/node-red-error.log last 15 lines:
0|node-red | RequestError: Error: getaddrinfo ENOTFOUND api.telegram.org
0|node-red | at new RequestError (/Users/server/.node-red/node_modules/request-promise-core/lib/errors.js:14:15)
0|node-red | at Request.plumbing.callback (/Users/server/.node-red/node_modules/request-promise-core/lib/plumbing.js:87:29)
0|node-red | at Request.RP$callback [as _callback] (/Users/server/.node-red/node_modules/request-promise-core/lib/plumbing.js:46:31)
0|node-red | at self.callback (/Users/server/.node-red/node_modules/request/request.js:185:22)
0|node-red | at Request.emit (node:events:526:28)
0|node-red | at Request.onRequestError (/Users/server/.node-red/node_modules/request/request.js:877:8)
0|node-red | at ClientRequest.emit (node:events:526:28)
0|node-red | at TLSSocket.socketErrorListener (node:_http_client:442:9)
0|node-red | at TLSSocket.emit (node:events:526:28)
0|node-red | at emitErrorNT (node:internal/streams/destroy:164:8)
0|node-red | at emitErrorCloseNT (node:internal/streams/destroy:129:3)
0|node-red | at processTicksAndRejections (node:internal/process/task_queues:83:21) {
0|node-red | code: 'EFATAL'
0|node-red | }

/Users/server/.pm2/logs/node-red-out.log last 15 lines:
0|node-red | 1 Mar 11:50:53 - [info] Projects directory: /Users/server/.node-red/projects
0|node-red | 1 Mar 11:50:53 - [info] Server now running at http://127.0.0.1:1880/
0|node-red | 1 Mar 11:50:53 - [info] Active project : Dragonframe_Heartbeat_Server
0|node-red | 1 Mar 11:50:53 - [info] Flows file : /Users/server/.node-red/projects/Dragonframe_Heartbeat_Server/flow.json
0|node-red | 1 Mar 11:50:53 - [info] Starting flows
0|node-red | 1 Mar 11:50:53 - [info] Started flows
0|node-red | 1 Mar 11:50:53 - [info] [udp in:Pantry Camera Port 65519] udp listener at 0.0.0.0:65519
0|node-red | 1 Mar 11:50:53 - [info] [udp in:Trade Floor Camera Port 65515] udp listener at 0.0.0.0:65515
0|node-red | 1 Mar 11:53:36 - [info] Stopping modified nodes
0|node-red | 1 Mar 11:53:43 - [info] Stopped modified nodes

```

I have three Node-Red integrations on three different computers communicating to a single Telegram bot notifying me different status for each computer throughout the day.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [12 March 2022 13:21 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/2 "2022-03-12T13:21:34Z")

</div>

Are you connecting via wifi? Perhaps node-red starts up before the network is ready.

---

<div class="post-metadata">

**Author:** ![ScheepersJohan](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scheepersjohan/32/39556_2.png) [@ScheepersJohan](https://discourse.nodered.org/u/ScheepersJohan)\
**Post date:** [12 March 2022 13:25 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/3 "2022-03-12T13:25:25Z")

</div>

What happens when you wait a few minutes? The Telegram node poles every few minutes

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [12 March 2022 13:29 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/4 "2022-03-12T13:29:16Z")

</div>

I don't use pm2, but is that a fatal error that kills node-red? If so are you using the latest versions of node-red and the telegram node, and also a valid nodejs version? You can check that using `node -v`, which should preferably be 14 or 16. 12 should also work but it is nearly out of support so best avoided.

---

<div class="post-metadata">

**Author:** ![patofoto](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/patofoto/32/25792_2.png) [@patofoto](https://discourse.nodered.org/u/patofoto)\
**Post date:** [12 March 2022 13:48 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/5 "2022-03-12T13:48:21Z")

</div>

WiFi disabled. Connected via ethernet.

---

<div class="post-metadata">

**Author:** ![patofoto](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/patofoto/32/25792_2.png) [@patofoto](https://discourse.nodered.org/u/patofoto)\
**Post date:** [12 March 2022 13:48 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/6 "2022-03-12T13:48:50Z")

</div>

Nothing happens until I start Node-Red manually

---

<div class="post-metadata">

**Author:** ![patofoto](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/patofoto/32/25792_2.png) [@patofoto](https://discourse.nodered.org/u/patofoto)\
**Post date:** [12 March 2022 13:51 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/7 "2022-03-12T13:51:12Z")

</div>

I guess it is a fatal error?. Not sure hot to tell. I am using latest versions of everything. Using node v17.7.1. Should I be using node v16?.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [12 March 2022 15:25 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/8 "2022-03-12T15:25:51Z")

</div>

> [@patofoto](#):
>
> Should I be using node v16

[https://nodered.org/docs/faq/node-versions](https://nodered.org/docs/faq/node-versions)

---

<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:** [11 May 2022 15:26 UTC](https://discourse.nodered.org/t/help-with-telegram-integration-error/59753/9 "2022-05-11T15:26:18Z")

</div>

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