Cannot connect to LND via Tor about bitbanana

[michaelWuensch]

Hi,
first of all, Orbot is not needed, BitBanana suports tor natively.
The problem is most likely that you are trying to connect on port 9735 which is the port for the lightning peer 2 peer protocol. But what you want to connect to is the api that lnd exposes which is on 10009 for gRPC.
Therefore, in BitBanana go to manage nodes and edit the connection settings and change the port to 10009 and save.

[djesys]

Hi again, I did lndconnect - j, then exchanged clearnet ip in output with my xxxxxxxx.onion address on port 10009 (opened in firewall) . Pasted that into BitBanana and getting this after a while Connection failed. UNAVAILABLE: Response returned from proxy was not successful (expected 2xx, got 502 Bad Gateway (unexpected close)). Response body: Server: curl --socks5 localhost:9050 --socks5-hostname localhost:9050 -s https://check.torproject.org/ | cat | grep -m 1 Congratulations | xargs Congratulations. This browser is configured to use Tor. Is the certificate connected to my clearnet ip ? Could it be a cert issue ? Thanks so much

…

On 11. Jan 2024, at 04:38, Michael Wünsch ***@***.***> wrote: Hi, first of all, Orbot is not needed, BitBanana suports tor natively. The problem is most likely that you are trying to connect on port 9735 which is the port for the lightning peer 2 peer protocol. But what you want to connect to is the api that lnd exposes which is on 10009 for gRPC. Therefore, in BitBanana got to manage nodes and edit the connection settings and change the port to 10009 and save. — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCPAQXPRTWSXUGDWMG3K63YN6JGZAVCNFSM6AAAAABBT7RYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBWGQ4TONJRGM>. You are receiving this because you authored the thread.

[djesys]

Just tried this on the server: lndconnect --lnddir=/home/.lnd -j ***@***.*** --port 10009 -j Result: lndconnect://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%4xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.onion:10009?cert=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Noticed cert is the same. Pasted into bitbanana The provided host or port is invalid.

…

On 11. Jan 2024, at 04:38, Michael Wünsch ***@***.***> wrote: Hi, first of all, Orbot is not needed, BitBanana suports tor natively. The problem is most likely that you are trying to connect on port 9735 which is the port for the lightning peer 2 peer protocol. But what you want to connect to is the api that lnd exposes which is on 10009 for gRPC. Therefore, in BitBanana got to manage nodes and edit the connection settings and change the port to 10009 and save. — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCPAQXPRTWSXUGDWMG3K63YN6JGZAVCNFSM6AAAAABBT7RYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBWGQ4TONJRGM>. You are receiving this because you authored the thread.

[michaelWuensch]

Hi,
when connecting over tor, the certificate isn't even needed. Tor already ensures you are connected with the correct service. Therefore when connecting over Tor BitBanana does not even check the cert.
What is needed though is the admin macaroon (macaroon = fancy cookie), which defines what access the API user has. Admin macaroon grants access to everything.
So in your lndconnect command you have to add the admin macaroon path.

[djesys]

Hi, so I added this to
/etc/tor/torrc

HiddenServiceDir /var/lib/tor/lnd
HiddenServicePort 10009 127.0.0.1:10009

and used this string to create an lndconnect string:

lndconnect --adminmacaroonpath=/home/user/.lnd/data/chain/bitcoin/mainnet/admin.macaroon --port=10009 --host=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.onion -j

The result I pasted into bitbanana. Response continues

Connection failed.

UNAVAILABLE: Response
returned from proxy was not
successful (expected 2xx, got
502 Bad Gateway (unexpected
close)). Response body:

nmap:
9050/tcp open tor-socks
9051/tcp open tor-control
9735/tcp open unknown
10009/tcp open swdtp-sv

curl --socks5 localhost:9050 --socks5-hostname localhost:9050 -s https://check.torproject.org/ | cat | grep -m 1 Congratulations | xargs
Congratulations. This browser is configured to use Tor.

Firewall 10009 is open, even though propably not necessary.

I am out of ideas now.

[michaelWuensch]

Hm, me too.
I myself actually use preconfigured setups like Start9 or Umbrel instead of setting up everything on my own. Therefore I don't have to much experience with it. What I can see from your posts looks correct.
In general Tor connection is not very reliable. Connecting to my nodes with tor often works, then sometimes it doesn't for a few hours or so without me changing anything. I cannot remember though if that error message you get was one of the temporary failures.
I personally switched to using Tailscale VPN to connect to my nodes. The user experience is so much better as it is way faster and much more reliable. But of course not as private.

I guess it is still the same with ZEUS?
(For ZEUS you need to use port 8080 as ZEUS only supports REST, not gRPC)

[djesys]

I can confirm connecting to clearnet IP works. So, it´s something Tor-related. I will give tailscale a shot, just hoping the setup is straight forward.