Skip to content
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.

error: failed to unpack msg from ws: unpack #3500

Open
gouravvemula0 opened this issue Jan 30, 2023 · 1 comment
Open

error: failed to unpack msg from ws: unpack #3500

gouravvemula0 opened this issue Jan 30, 2023 · 1 comment

Comments

@gouravvemula0
Copy link

What I'm trying to do

Integrated web KMS provided by trustbloc to the aries rest agent and tried creating a new connection, it got stuck at "requested" state and this error showed up in the agent: error: failed to unpack msg from ws: unpack
I actually want to use the web KMS as a common keystore for all the aries services running along with it so that I can route requests from one to another after connection establishment succeeds.

Expected result
It should move from "requested" state to "completed" state and did:key of this connection should be retrievable by the other aries services

Actual result

error: failed to unpack msg from ws: unpack

@sudeshrshetty
Copy link
Contributor

@gouravvemula0 would you be able to provide more details?
There should be some underlying error in agent logs & also in web kms logs.

We have already used webkms in many places for DIDComm, you can refer integration tests in https://github.com/trustbloc/agent-sdk project.

Let me know if you need more details.

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

No branches or pull requests

2 participants