When I run a second Bisq instance and I try to take the offer that I make in the first Whonix workstation (the one where the Whonix gateway is on debut), I do not see any messages at all in the debug console.
But if someone (me) is connecting to Tor address in the Bisq instance, inside the Whonix Workstation, running on the Whonix Gateway, then… shouldn’t I see some evidence that it is trying to connect?
The second Bisq instance says that
Warning
You cannot take that offer because the maker is offline.
This is the error that everyone is getting recently using Bisq on Whonix. I have the debug window open (explained above), so what more can I do to help debug this?
No. That would be Microsoft Windows style “re-install Windows”. Hopefully on Linux such crude fixes aren’t required.
Best to look at the short source code of /usr/bin/onion-grater-add and/or run the script in verbose mode (xtrace).
sudo bash -x /usr/bin/onion-grater-add 40_bisq
It creates a symlink to /usr/local/etc/onion-grater-merger.d/.
/usr/local/etc/onion-grater-merger.d/
Also onion-grater journal log will show which profiles are load.
The actual file created by onion-grater-merger which will be consumed eventually by onion-grater is
/etc/onion-grater.d/30_autogenerated.yml
No. The kernel will eventually but that’s very low level and very most likely not something to worry about.
That’s Qubes-Whonix-Gateway internal IP. Reachable from Whonix-Workstation.
This most likely won’t be the issue. onion-grater is generally functional. Whonix-Workstation 127.0.0.1 is redirected to Whonix-Gateway. (anon-ws-disable-stacked-tor)
No, with whonix-gw as network qube the inbound connection do not get through. As inbound connections are required for Bisq to run properly, I had to completely abandon Whonix.
I’d love to see Bisq work on Whonix, but the instructions on the Whonix Wiki simply don’t work.
Yeah those instructions suck in every way. That’s why we’re debugging this. And it used to work last year, so something changed and so maybe it can be fixed.
Seems to be broken: [StartTor] ERRORbisq.network.p2p.network.RunningTor: Couldn't connect to Tor. net.freehaven.tor.control.TorControlError: Error reply: Command filtered
Error message may indicate an Onion Grater problem. Would require further testing to see what command is being sent.
Did some further digging.
This is the command being sent to Tor control port GETINFO status/bootstrap-phase
Then reply received: 510 Command filtered
That command happens after a bit of other back and forth control commands.