-
Notifications
You must be signed in to change notification settings - Fork 3k
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
TGbot 推送失败 #2558
Comments
一样的问题,我设置了tgbot反代,但是每个人的库notify.py关于反代都不一样,
|
解决了吗, 我尝试解决,没搞定 |
现在bark推送也是报这个错. |
我发现是sendNotify.js的tgBotNotify方法有问题,然后我用Claude重写了这个方法,试了下,可以用。 function tgBotNotify(text, desp) {
} |
Qinglong version
V2.17.12
Steps to reproduce
Telegram 发送通知消息失败😞
RequestError
at ClientRequest. (/ql/node_modules/.pnpm/got@11.8.6/node_modules/got/dist/source/core/index.js:970:111)
at Object.onceWrapper (node:events:634:26)
at ClientRequest.emit (node:events:531:35)
at origin.emit (/ql/node_modules/.pnpm/@szmarczak+http-timer@4.0.6/node_modules/@szmarczak/http-timer/dist/source/index.js:43:20)
at TLSSocket.socketErrorListener (node:_http_client:500:9)
at TLSSocket.emit (node:events:519:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1117:18)
at internalConnectMultiple (node:net:1185:5)
at Timeout.internalConnectMultipleTimeout (node:net:1711:5)
at listOnTimeout (node:internal/timers:575:11)
at process.processTimers (node:internal/timers:514:7) {
code: 'ETIMEDOUT',
timings: {
start: 1731295532933,
socket: 1731295532934,
lookup: 1731295532940,
connect: undefined,
secureConnect: undefined,
upload: undefined,
response: undefined,
end: undefined,
error: 1731295533193,
abort: undefined,
phases: {
wait: 1,
dns: 6,
tcp: undefined,
tls: undefined,
request: undefined,
firstByte: undefined,
download: undefined,
total: 260
}
}
}
What is expected?
推送失败问题
What is actually happening?
Tgbot一直推送失败
System Info
No response
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: