How to connect ZAP (zap-android) to lnd daemon and get the lndconnect scheme right? #6490
-
remote node runs debian lnd-linux-amd64-v0.14.3-beta.tar.gz the scheme zap android asks for the tls.cert and admin.maroon are in the lnd datadir. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
yes you can easily connect also your Node which is running behind tor, for zap-android it uses port 10009 (grpc) so it would look something like this:
for more infos check this out: https://github.com/rootzoll/raspiblitz/blob/v1.7/home.admin/config.scripts/bonus.lndconnect.sh#L76 or https://github.com/LN-Zap/lndconnect/blob/master/lnd_connect_uri.md |
Beta Was this translation helpful? Give feedback.
-
not sure which node setup your are running but you also need to create a hidden tor grpc service, so you can connect to it. Because the above onion address, is the address of my hidden service which is listening on port 10009. |
Beta Was this translation helpful? Give feedback.
-
lnd.conf has no (known) option to expose the grpc port on the tor hidden service v3. thus proceed manually in lnd.conf by #5750
and edit torrc
then if you encounter 'problem: Connection failed TLS ALPN negotiation failed with protocols: [h2]' it is due bad mapping 10009 to the lnd announced grpc 127.0.0.1:8080 (which seems logical but errors) instead of to 10009 (rpc). voila zap connects. |
Beta Was this translation helpful? Give feedback.
lnd.conf has no (known) option to expose the grpc port on the tor hidden service v3.
thus proceed manually in lnd.conf by #5750
and edit torrc
then
sudo systemctl restart tor
and restart lndif you encounter 'problem: Connection failed TLS ALPN negotiation failed with protocols: [h2]' it is due bad mapping 10009 to the lnd announced grpc 127.0.0.1:8080 (which seems logical but errors) ins…