Closed jleach closed 2 years ago
Hi @jleach I did the same configuration and set up the mediator for aries Bifold using von network. I am not using ngrok rather my ip, I was able to establish the connection but the area where I face issue is the communication part. It throws error for wss switching and renders this error message : Message is undeliverable to connection . Please find the attachment for reference:
Hi @jleach We are using Aries acapy mediator . Using the invitation URl of mediator we tried connecting Aries bifold mobile app. We are follwoing error.
Please let me know , how can resolve it.
@jainavinash845 I would test the connectivity to see where it's failing. Is the problem the wallet can not talk to the mediator or the mediator to the wallet? Or perhaps the mediator cannot talk to the agent? That IP looks like a Bogon network for CGNAT. Maybe you're having problems because you are running behind CGNAT and the inbound connection is not making it through? Try testing with the curl
command and find out where the network connection is being blocked.
Hi @jleach Thanx for your help.
In the initial while run the app changed the invitation url in the env file. And it does not redirect to wallet home page . It gives Time out error in the app and backed end Message unpack failed . I found the backend error logs Please let me know , how can resolve it. .
As far as I can tell the current repo, as it is, wont work for any wallet because its missing either the ACA-py plugin from the toolbox (which Indecio uses in their running example) or a reverse proxy like Caddy to route both
wss://
andhttps://
to the same port on the mediator. This means the docker stack will start but I don't think any wallet can meaningfully use it when running. Tested agains Aries Bifold.For context, the Aries Bifold wallet uses
https://
to respond to a connection invitation. Then it will open a DIDComm channel viawss://
for subsequent messaging. The wallet cannot establish thewss://
connection becausengrok
is only forwardinghttps://
back to the mediator container and, AFAIK, it can not be configured to do two ports simultaneously.