where to get some help ?

[leostereo]

Hi guys ,
I can not get my bpa connecting with any available wallet.
Where can I get some help ?
Regards.

[etschelp]

Hey, you can either ask you questions here, or join hyperledger on discord: https://discord.gg/hyperledger and ask your questions in the business-partner-agent channel.

If all wallet connections fail, my very first guess would be that the port that handles didcomm is not exposed to the internet. If you test locally you need to use ngrok (see start-with-tunnels.sh), diode or a basic ssh tunnel. Also depending on how you open the connection make sure that both the bpa and the wallet are on the same ledger.

[leostereo]

@etschelp , thanks for your response:
Let me provide more info.
My bpa instance is running on an exposed server with fixed public ip address (I dont need ngrok here, do I ?).
I already tryed two ledgers:

1. indy-test.bosch-digital.de and
2. http://test.bcovrin.vonx.io

and two wallets:

1. esatus
2. indisi

(btw ... I succeded running two instance on same server and create a connection)
Could you recommend a working combination of ledger and wallet ?
I will share the lines I changed on my .env in case you can add something.

• BPA_HOST=43.198.117.99:8070
• BPA_PORT=8070
• BPA_WEBHOOK_URL=http://43.198.117.99:8070/log
• BPA_SCHEME=http
• BPA_WEB_MODE=false
• ACAPY_ENDPOINT=http://43.198.117.99:8030

And thats it.
I think , my problem is on my config since when trying to scan the invitation QR I got the:
invalid invitation
message.
Ok , I will continue working on this.
Thanks again, I really apretiate your words.
leo.

[etschelp]

It seems like your didcomm endpoint is not accessible, either it is not mapped or a firewall rule is blocking it

curl -v -X 'POST' -H 'Content-Type: application/didcomm-envelope-enc'  http://43.198.117.99:8030
*   Trying 43.198.117.99:8030...
*   connect to 43.198.117.99 port 8030 failed: Operation timed out

The rest looks good, the webhook url could also be docker internal, but I guess it works that way too.

[etschelp]

ah its probably 143 that one works

curl -v -X 'POST' -H 'Content-Type: application/didcomm-envelope-enc'  http://143.198.117.99:8030
*   Trying 143.198.117.99:8030...
*    Connected to 143.198.117.99 (143.198.117.99) port 8030 (#0)

So far everything looks good to me.

[leostereo]

@etschelp Thanks again.
Let me explain , for security reason I did not list my real public ip address:
I reproduced the curl call you made and it yelds:

curl -v -X 'POST' -H 'Content-Type: application/didcomm-envelope-enc'  http://43.198.117.99:8030
*   Trying 43.198.117.99:8030...
* Connected to 43.198.117.99 (43.198.117.99) port 8030 (#0)
> POST / HTTP/1.1
> Host: 43.198.117.99:8030
> User-Agent: curl/7.74.0
> Accept: */*
> Content-Type: application/didcomm-envelope-enc
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 400 Bad Request
< Content-Type: text/plain; charset=utf-8
< Content-Length: 16
< Date: Wed, 01 Jun 2022 14:17:58 GMT
< Server: Python/3.6 aiohttp/3.7.4.post0
< 
* Connection #0 to host 43.198.117.99 left intact`

BTW:
Im also testing with trinsic wallet now and it "freezes" after scanning the invitation QR code.
Also , I will provide all info you need to debug this in case you want to.
You mentioned that every think seems to be ok so it means that im close.
Is there any pair wallet - ledger you recomend for this poc ?
Leandro.

[etschelp]

Probably the Lissi wallet on bcovrin or sovrin ledgers. The last update on the trinsic wallet was like a year ago and I do not think it works well any more with the latest versions of aca-py. But at least initiating a connection with the v1 protocol should work I guess.

[etschelp]

The main issue that I have with the Trinsic wallet though is that push notifications are completely broken on their end (at least on ios) so that it is not very useful anyway.

[leostereo]

Have you ever tryed esatus ?
u other ? Lissi is not available on my region.
Regards.

[etschelp]

Esatus also works, also it lets you choose the ledger. If you are using sovrin main or test net you can try the connect.me app. Its a pity that the Lissi app is not available for you as it works very well.

[etschelp]

I figured out what is causing the connection issues. The older apps do not support the new didcomm mime types. In acapy-static-args.yml you have to set the following to false:

emit-new-didcomm-prefix: false
emit-new-didcomm-mime-type: false

This will cause issues with apps that can handle json-ld based credentials, because they in turn cannot handle the old mime-types, but as you are testing indy credentials it should not matter.

Esatus and Trinsic apps are able to connect that way, but as Trinsic notifications are broken you will be having issues with the credentials, but esatus should work if both the app and the BPA are on the same ledger (see ledger settings in the esatus app).

[leostereo]

Yes !! That was it. It is working now. Thank you ! El mar, 7 jun 2022 a las 10:09, Philipp Etschel ***@***.***>) escribió:

…

I figured out what is causing the connection issues. The older apps do not support the new didcomm mime types. In acapy-static-args.yml <https://github.com/hyperledger-labs/business-partner-agent/blob/main/scripts/acapy-static-args.yml> you have to set the following to false: emit-new-didcomm-prefix: falseemit-new-didcomm-mime-type: false This will cause issues with apps that can handle json-ld based credentials, because they in turn cannot handle the old mime-types, but as you are testing indy credentials it should not matter. Esatus and Trinsic apps are able to connect that way, but as Trinsic notifications are broken you will be having issues with the credentials, but esatus should work if both the app and the BPA are on the same ledger (see ledger settings in the esatus app). — Reply to this email directly, view it on GitHub <#753 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYKIVMSLUTHGECMGC7ZIMDVN5CXJANCNFSM5XPPVT4Q> . You are receiving this because you authored the thread.Message ID: <hyperledger-labs/business-partner-agent/repo-discussions/753/comments/2897929 @github.com>