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

[JeremyRand]

### Description

If the local Bisq P2P onion service is unreachable due to a firewall misconfiguration, it takes a week for Bisq to notify the user of this, while it should be trivially easy to detect immediately.

#### Version

Bisq v1.8.4

### Steps to reproduce

1. Install Bisq on Whonix as per the instructions on the Whonix wiki, but forget to configure the firewall on the Whonix-Workstation VM (thus, incoming onion connections from the Tor daemon to Bisq will be dropped).
2. Create an open offer.

### Expected behaviour

Bisq should immediately try to open a TCP connection to the local Bisq P2P onion service (routed through Tor), and when it finds that the connection is dropped, it should quickly convey this to the user.

### Actual behaviour

Bisq waits 1 week before displaying the following error:

> Important private notification!
> 
> You might need to clear your tor cache / restart your Bisq instance, as your 2 offers have not been reachable for at least a week.
> 
> To do that from the Bisq application menus:
> Settings -> Network Info -> Open Tor Settings -> Delete Outdated Tor Files and Shutdown

That's a long delay to notify the user about a problem that can be detected instantly.

### Screenshots

N/A; issue is in timing of graphical display, not the contents of the graphical display.

#### Device or machine

Haswell i7; Whonix 16 inside Qubes 4.1.

#### Additional info

N/A.


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

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