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

[JeremyRand]

> Dear Jeremy. That was what we call a "love letter" from support. I sent it earlier today.

Ah, I see. That explains the latency.  :D  Apologies for whatever hassle my misconfiguration caused for the support team, but at least it yielded a useful bug report I guess.

> Your onion is still rejecting incoming connections at the moment, FWIW.

I opened the port on my firewall right before I filed this bug, and someone took one of my offers shortly afterward, so I think it's fixed -- but let's keep this issue focused on improving Bisq rather than my incompetence setting up firewalls.

> Yes perhaps the Bisq software could automatically detect this. I'll take a look.

+1.  Only important thing to be careful about is that the probe needs to be routed through Tor (to the onion), not routed directly to localhost, since firewalls will behave differently for each.

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

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