search

wechaty / puppet-supports

Wechaty Puppet Services (WPS)
https://wechaty.js.org/docs/puppet-services/
Apache License 2.0
30 stars 3 forks source link

token: puppet_paimon and puppet: 'wechaty-puppet-service' Failed to link #126

Open 15335179243 opened 2 years ago

15335179243 commented 2 years ago

090906958447d3ced8b4b8fffe71d21 6 ERR PuppetService start() rejection: 14 UNAVAILABLE: No connection established Error: 14 UNAVAILABLE: No connection established at Object.callErrorFromStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/call.js:31:26) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client.js:179:52) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181) at /wechaty/node_modules/@grpc/grpc-js/build/src/call-stream.js:145:78 at processTicksAndRejections (node:internal/process/task_queues:78:11) 20:58:28 ERR PuppetService start() this.grpc.stop() rejection: 14 UNAVAILABLE: No connection established Error: 14 UNAVAILABLE: No connection established at Object.callErrorFromStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/call.js:31:26) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client.js:179:52) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181) at /wechaty/node_modules/@grpc/grpc-js/build/src/call-stream.js:145:78 at processTicksAndRejections (node:internal/process/task_queues:78:11) Error: 14 UNAVAILABLE: No connection established at Object.callErrorFromStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/call.js:31:26) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client.js:179:52) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181) at /wechaty/node_modules/@grpc/grpc-js/build/src/call-stream.js:145:78 at processTicksAndRejections (node:internal/process/task_queues:78:11) { code: 14, details: 'No connection established', metadata: Metadata { internalRepr: Map(0) {}, options: {} } } 20:58:28 ERR Wechaty start() exception: 14 UNAVAILABLE: No connection established 20:58:28 WARN PuppetService start() found this.grpc is already existed. dropped.

huan commented 2 years ago

Please disable TLS of you are using the latest version of Wechaty.

See:

15335179243 commented 2 years ago

如果您使用的是最新版本的微信，请禁用 TLS。

看：

I set TLS to cancel but still can not

WECHATY Environment Variables: 3 WECHATY_DOCKER=1 WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER=false WECHATY_LOG=

Starting Docker Container for Wechaty v0.0.0(unknown) with Node.js v16.8.0 ... Working directory: /bot Please make sure you had installed all the NPM modules which is depended on your bot script. Executing node a.js 21:57:31 ERR PuppetService start() rejection: 14 UNAVAILABLE: No connection established Error: 14 UNAVAILABLE: No connection established at Object.callErrorFromStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/call.js:31:26) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client.js:179:52) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141) at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181) at /wechaty/node_modules/@grpc/grpc-js/build/src/call-stream.js:145:78 at processTicksAndRejections (node:internal/process/task_queues:78:11)

huan commented 2 years ago

WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER=false

The above setting is not right.

Set it to true to disable the TLS.

15335179243 commented 2 years ago

WECHATY_PUPPET_SERVICE_NO_TLS_INSECURE_SERVER=false

上面的设置不对。

将其设置true为禁用 TLS。

Yes, I tried again with the Settings set to True while waiting for your reply,It's always blocked image

huan commented 2 years ago

If you set it to true then the TLS will be disabled, it can be conformed by the log output:

Init() TLS disabled.

So if you still can not connect to the puppet service, you need to check your puppet service token.

Can you try to run the following command and let me know what is the output? (Paste text please)

npm install -g wechaty-token

Then 

wechaty-token discover pippet_paimon_TOKEN

Note: replace the above token to yours.

15335179243 commented 2 years ago

If you set it to true then the TLS will be disabled, it can be conformed by the log output:

Init() TLS disabled.

So if you still can not connect to the puppet service, you need to check your puppet service token.

Can you try to run the following command and let me know what is the output? (Paste text please)

npm install -g wechaty-token

Then

wechaty-token discover pippet_paimon_TOKEN

Note: replace the above token to yours.

There is no problem with tokens

image

huan commented 2 years ago

If your token service is OK, could you please try the wechaty@0.62 to see if it can fix your problem?

If not, then there might be related to some unknown problems, I'd like to suggest that you should contact the support from your puppet service provider.

15335179243 commented 2 years ago

thank you

huan commented 2 years ago

You are welcome