[bisq-network/bisq] Unreachable local Bisq onion takes way too long to detect (Issue #6142)

[jmacxx]

@JeremyRand  That looks the same as [what I followed](https://www.whonix.org/wiki/Bisq).  Just to be sure I ran them again and rebooted both Gateway and Workstation.
Cmd line = `./bisq-desktop --torControlPort=9051 --torControlPassword=notrequired --socks5ProxyBtcAddress=127.0.0.1:9050 --useTorForBtc=true --daoActivated=false`

(daoActivated=false because I only have 8Gb RAM and was experiencing memory exhaustion with the overhead of the VM).

It still is not reachable from outside, just as your Bisq is not reachable.
If you'd like to check, here is a test offer I'm holding open:  

![image](https://user-images.githubusercontent.com/47253594/163081679-4ee19d00-1f06-4bce-bff1-be48fc7a7783.png)

![image](https://user-images.githubusercontent.com/47253594/163081605-1c448045-6644-463e-bdeb-59b982b1c5a9.png)



-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/6142#issuecomment-1097464137
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/issues/6142/1097464137 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20220412/f77e601b/attachment-0001.htm>