Get ECONNREFUSED when bot logout and cannot re-login #617
Comments
Need More InformationSorry, you did not follow the ISSUE Template, and there's not enough information about your problem. In order to help us to find the problem out, you should provide all the detail information about the issue. Please make sure you are following the ISSUE Template, answer all the question, and the more important: provide the steps to reproduce the problem. |
|
Close this issue due to not active for weeks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the bot run for a while, it logout and get the following error, then it cannot re-login again.
Paste the full output logs here with
WECHATY_LOG=sillyset$ WECHATY_LOG=silly npm run ts-node mybot.ts # or $ WECHATY_LOG=silly node dist/mybot.jsShow Logs
Paste the full output logs here with
WECHATY_LOG=sillyset09:41:47 WARN PuppetWebBrowser execute() exception: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:40914, Error: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:40914
at ClientRequest. (/wechaty/node_modules/selenium-webdriver/http/index.js:238:15)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:191:7)
at Socket.socketErrorListener (_http_client.js:358:9)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at emitErrorNT (net.js:1279:8)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
09:41:47 WARN PuppetWebBridge execute() exception: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:40914
09:41:47 WARN PuppetWebBridge proxyWechaty() noWechaty exception: Error: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:40914
at ClientRequest. (/wechaty/node_modules/selenium-webdriver/http/index.js:238:15)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:191:7)
at Socket.socketErrorListener (_http_client.js:358:9)
at emitOne (events.js:96:13)
at Socket.emit (events.js:191:7)
at emitErrorNT (net.js:1279:8)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickDomainCallback (internal/process/next_tick.js:128:9)
The text was updated successfully, but these errors were encountered: