Umbrel: Cannot connect to Electrs via Tor

[esackbauer]

I was wondering why I cannot connect via Tor to my Electrum node.
It seems docker-compose.yml gets somehow created in a wrong way:

ports:
- "50001:50001"
networks:
net:
ipv4_address: 10.11.4.0

I guess the .0 IP address is the problem. Happens both with electrs and frontail. The other services have proper IP addresses.

I installed umbrel on a fresh install inside a VM:
Debian 10.7 AMD64
Docker 20.10.1 (via debian repository)
docker-compose 1.27.4
Umbrel 0.2.15

[lukechilds]

Apart from the formatting that all looks correct. Are you sure you're connecting through a Tor proxy and that electrs has finished indexing?

[esackbauer]

Ok it seems there are no /24 subnets, only one big /16 net, so IPs are fine.

Yes, I can connect with orbot to Tor in general and have selected the Electrum wallet app. It says "not connected"

However on my Windows desktop in the same LAN as Umbrel, I can connect locally to the port 50001 with the Windows Electrum app and its working.

[esackbauer]

Connecting to the web interface via onion address works fine via Tor.
The onion address of the Bitcoin Core node seems to also not work. I have checked access with bitnodes.io, they also support onion addresses.

[Vilas1979]

Same problem, conecting to the web interface via onion address works. But node is invisible for bitnodes.io and no success connecting wallets using Bitcoin Core P2P or Bisq.

[louneskmt]

Are you sure you use a Tor proxy running on your devices? Did you setup a Tor proxy service (with either Homebrew on macOS, Chocolatey on Windows or a normal package manager on Linux)?

You also need to configure your app proxy. For example, in Electrum, you need to go to the "Proxy" tab and enable "Use Tor proxy on port 9050".

[mayankchhabra]

Umbrel uses Tor v3 for Bitcoin Core, and both Bitnodes and Bisq support Tor v2, so none of them can connect to your node. This is expected to change after the upcoming Bitcoin Core v0.21.0 release which brings official Tor v3 support.

[louneskmt]

Good to know, thanks @mayankchhabra!

[esackbauer]

@mayankchhabra Thanks for clarification!
It seems that Orbot is only using Tor V2 for now, maybe that is the reason:
https://github.com/guardianproject/orbot/pull/415

But then, how am I supposed to connect my mobile clients to Umbrel? Using port forwards or VPN on the firewall in the meantime?

[esackbauer]

Problem solved. I had in Android general connection setting "Private DNS" activated. This is not working properly with Orbot.
I switched it off, and everything was connecting properly via Orbot.