-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Polling Error: EFATAL #1136
Comments
This can be caused by connection Problem try this repo hope it helps |
Hi, I have this error, how can I handle this? It crash my app |
I have same error. The error happens with nodejs v20 and ubuntu 22.04. With nodejs v20 and mac, there is no error. :( |
@TheRebo Please could you share the environment? |
I have same error. The error happens with nodejs v20 and ubuntu 20.04. |
Same here. NodeJS v20 + Ubuntu 22.04. |
Any update on this? |
I am facing this same error in Ubuntu but I can run this code in replit and also works on Mac. |
I'm also facing this error how to solve this please help me |
Are you facing this error in Linux? |
No I'm getting this error in windows 11 |
same problem here |
same problem here on VPS ubuntu 22.04 - nodejs, all of my services were down because that error without any reason |
I used VPN and it started working. |
could you tell me detail? |
i was facing the same error but with nestgram, i managed to fix it by downgrading from nodejs v20 to v18, and started using proton VPN |
Same with Ubuntu 20.04 + Node 20. |
Same with Ubuntu 22.04 + Node v20.11.1 The application starts and works fine for a while. BUT |
I think I solved it, apparently you need to force IPv4 via agentOptions on the request API, like so: const botToken = "123123123:testAAAAA";
const telegramAPI = require("node-telegram-bot-api");
const bot = new telegramAPI(config.botToken, { polling: true, request: {
agentOptions: {
keepAlive: true,
family: 4
}
}});
bot.on("message", async function(msg) {
await bot.sendMessage(msg.chat.id, "test");
}); And then it works fine. Some related issues: |
same with windows 10 can anyone help? |
Thank you very much! |
It works! Thank you |
it works, thank you very much |
Hey guys, a little update for request type, is missing the URL parameter: request: { |
I think this is unnecessary since node-telegram-bot-api already fills that parameter with the correct URL, unless you're doing something really customized for your use-case you shouldn't do that. |
I am facing the same error with nodejs v20 and ubuntu 22.04 on virtual machine (VM). but there is no error on my local computer with nodejs v20 and macos. I downgraded the nodejs version to v14 on VM and it worked fine. |
Please help me!, error below happen when running the bot for the first time! :
RequestError: AggregateError
at new RequestError (/home/kali/Bot-Telegram-Password-Manager/node_modules/request-promise-core/lib/errors.js:14:15)
at plumbing.callback (/home/kali/Bot-Telegram-Password-Manager/node_modules/request-promise-core/lib/plumbing.js:87:29)
at Request.RP$callback [as _callback] (/home/kali/Bot-Telegram-Password-Manager/node_modules/request-promise-core/lib/plumbing.js:46:31)
at self.callback (/home/kali/Bot-Telegram-Password-Manager/node_modules/request/request.js:185:22)
at Request.emit (node:events:514:28)
at Request.onRequestError (/home/kali/Bot-Telegram-Password-Manager/node_modules/request/request.js:877:8)
at ClientRequest.emit (node:events:514:28)
at TLSSocket.socketErrorListener (node:_http_client:495:9)
at TLSSocket.emit (node:events:514:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'EFATAL'
}
The text was updated successfully, but these errors were encountered: