axiref / telegram-pwsbot Goto Github PK

我想你应该联系我的tg，我需要帮助@guanchage

(node:4199) UnhandledPromiseRejectionWarning: Error: ETELEGRAM: 400 Bad Request: chat_id is empty
at /root/telegram-pwsbot/node_modules/node-telegram-bot-api/src/telegram.js:280:15
at tryCatcher (/root/telegram-pwsbot/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/root/telegram-pwsbot/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/root/telegram-pwsbot/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/root/telegram-pwsbot/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/root/telegram-pwsbot/node_modules/bluebird/js/release/promise.js:729:18)
at _drainQueueStep (/root/telegram-pwsbot/node_modules/bluebird/js/release/async.js:93:12)
at _drainQueue (/root/telegram-pwsbot/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/root/telegram-pwsbot/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (/root/telegram-pwsbot/node_modules/bluebird/js/release/async.js:15:14)
at processImmediate (internal/timers.js:461:21)
(node:4199) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:4199) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

在通过一个稿件并添加内容时，无法换行,会变成一行，试过添加 \n \r\n 都不行
例如：/ok 本稿件来自匿名用户
自助投稿：@XXXXXXX

建议加入用户留言功能，实现用户与后台人员的交互！

Unhandled rejection RequestError: Error: connect ETIMEDOUT 31.13.92.5:443
at new RequestError (/root/telegram-pwsbot/node_modules/request-promise-core/lib/errors.js:14:15)
at Request.plumbing.callback (/root/telegram-pwsbot/node_modules/request-promise-core/lib/plumbing.js:87:29)
at Request.RP$callback [as _callback] (/root/telegram-pwsbot/node_modules/request-promise-core/lib/plumbing.js:46:31)
at self.callback (/root/telegram-pwsbot/node_modules/request/request.js:185:22)
at Request.emit (node:events:513:28)
at Request.onRequestError (/root/telegram-pwsbot/node_modules/request/request.js:877:8)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

Unhandled rejection RequestError: Error: connect ETIMEDOUT 31.13.92.5:443
at new RequestError (/root/telegram-pwsbot/node_modules/request-promise-core/lib/errors.js:14:15)
at Request.plumbing.callback (/root/telegram-pwsbot/node_modules/request-promise-core/lib/plumbing.js:87:29)
at Request.RP$callback [as _callback] (/root/telegram-pwsbot/node_modules/request-promise-core/lib/plumbing.js:46:31)
at self.callback (/root/telegram-pwsbot/node_modules/request/request.js:185:22)
at Request.emit (node:events:513:28)
at Request.onRequestError (/root/telegram-pwsbot/node_modules/request/request.js:877:8)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

Unhandled rejection RequestError: Error: connect ETIMEDOUT 162.125.34.133:443
at new RequestError (/root/telegram-pwsbot/node_modules/request-promise-core/lib/errors.js:14:15)
at Request.plumbing.callback (/root/telegram-pwsbot/node_modules/request-promise-core/lib/plumbing.js:87:29)
at Request.RP$callback [as _callback] (/root/telegram-pwsbot/node_modules/request-promise-core/lib/plumbing.js:46:31)
at self.callback (/root/telegram-pwsbot/node_modules/request/request.js:185:22)
at Request.emit (node:events:513:28)
at Request.onRequestError (/root/telegram-pwsbot/node_modules/request/request.js:877:8)
at ClientRequest.emit (node:events:513:28)
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

运行后提示这个，服务器防火已开443
服务器端ping的话是可以通的
现在我的问题可能是目标服务器是否可用？或者可以替换使用的吗？

大概的想法是：设置好一个机器人，用户可以发送特定的命令选择需要投稿的频道，投稿到一个审核群中，若审核通过，自动发布到对应的那个频道。

感觉还是挺有用的，节约了搭建多个bot的资源，也不需要设置多个审稿群了。

不知可否实现。

经常有非频道订阅的人使用 bot，希望此举能够阻止一部分尝试使用 bot 的无关人士

或者有什么别的更好的办法告诉我一下