Using Bisq from inside a firewall which blocks access to Tor here. I’m not experienced with Tor but crucially I must be doing something right, because Bisq starts and I have successfully completed trades as a maker. For the most part, Tor inside Bisq is working if I access it through a socksv5 proxy.
BUT there is a kind of name resolution to .onion addresses which Bisq performs frequently in relationship to multiple types of events; I gather this sort of name resolution is not DNS, it’s something else (and that’s all I know). This creates multiple severe usability problems which are non-blocking but still painful when trading as a maker, and I think this problem makes it completely impossible for me to trade as a taker.
“Name or service not known” error message
Here’s an example “Name or service not known” error message extract (I redacted the exact basename of the URL in case it matters for privacy):
Error at doRequestWithProxy with url http://123abcde.onion/ and param getAllMarketPrices. Throwable=123abcde.onion: Name or service not known
Generally speaking, what should I look into to solve a name resolution problem such as this one?
My setup
Maybe someone will be able to help with my specific situation too; surely the errors as shown above are related to the non-standard way in which I have to use Bisq. Specifically, 2 things I’m doing are not standard:
- As already explained, I bypass a firewall which blocks Tor using a socksv5 proxy, which I open with a ssh connection.
- Bisq cannot currenntly be installed on my distro (Guix). I have created a QEMU VM with Debian. I ssh into the VM, then I start Bisq on the VM with an X window on the Guix bare metal, thanks to X forwarding. I also open my socks proxy connection from the bare metal OS. Then the Bisq running in the VM uses the proxy exposed on the bare metal machine, which from its point of view is at IP 10.0.2.2.