Skip to content
This repository has been archived by the owner on Jun 3, 2023. It is now read-only.

启动bot时显示token不存在 #61

Open
nsioo opened this issue Jul 2, 2022 · 0 comments
Open

启动bot时显示token不存在 #61

nsioo opened this issue Jul 2, 2022 · 0 comments

Comments

@nsioo
Copy link

nsioo commented Jul 2, 2022

puppet 为 'wechaty-puppet-service'
token 为 puppet_wxwork_ 开头
然后本地测试启动,
出现:
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
17:57:26 WARN WechatyToken discover() retry.execute(discoverApi) fail: WechatyToken discover() endpointhttps://api.chatie.io/v0/hosties/我的token rejection: Error: read ECONNRESET
17:57:26 WARN ResolverWechaty updateResolution() address not found target wechaty://api.chatie.io/我的token: token does not exist
node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^

GError: 14 UNAVAILABLE: Wechaty service discovery / resolution failed for target wechaty://api.chatie.io/我的token: token "我的token" does not exist
at Object.callErrorFromStatus (E:\workspace\wechaty-test\node_modules@grpc\grpc-js\build\src\call.js:31:26)
at Object.onReceiveStatus (E:\workspace\wechaty-test\node_modules@grpc\grpc-js\build\src\client.js:189:52)

token本身确认没有问题
请问用这种方式启动bot还缺少什么东西吗

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant