<p>I had a look at the logs.<br>
I see all the "[BlockingClient network thread for xxxxx.onion:8333] ERROR o.b.n.BlockingClient: Error trying to open/read from connection: xxxxx.onion:8333".<br>
I see these error lines on my Bisq node too.<br>
I tried to figure out what could be wrong, but could not find anything.<br>
So,</p>
<ul>
<li>tor network instability could be the reason, <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="436357225" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2773" data-hovercard-type="issue" data-hovercard-url="/bisq-network/bisq/issues/2773/hovercard" href="https://github.com/bisq-network/bisq/issues/2773">#2773</a> was fixed by trying again after an OS restart.</li>
<li>"Use bitcoinj with connection handling audit fixes" PR (<a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="428435156" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq/issues/2618" data-hovercard-type="pull_request" data-hovercard-url="/bisq-network/bisq/pull/2618/hovercard" href="https://github.com/bisq-network/bisq/pull/2618">#2618</a>) was not merged. Although there is no direct fix for this problem, I would like to see whether we keep seeing this problem when that PR is merged.</li>
</ul>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/2754#issuecomment-486261148">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNVSI47OQR426R6OO33PSBTY3ANCNFSM4HHI5EYQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AJFFTNSSOMNNKELNLTBENXTPSBTY3ANCNFSM4HHI5EYQ.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/bisq","title":"bisq-network/bisq","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/bisq"}},"updates":{"snippets":[{"icon":"PERSON","message":"@oscarguindzberg in #2754: I had a look at the logs.\r\nI see all the \"[BlockingClient network thread for xxxxx.onion:8333] ERROR o.b.n.BlockingClient: Error trying to open/read from connection: xxxxx.onion:8333\".\r\nI see these error lines on my Bisq node too.\r\nI tried to figure out what could be wrong, but could not find anything.\r\nSo,\r\n- tor network instability could be the reason, #2773 was fixed by trying again after an OS restart.\r\n- \"Use bitcoinj with connection handling audit fixes\" PR (https://github.com/bisq-network/bisq/pull/2618) was not merged. Although there is no direct fix for this problem, I would like to see whether we keep seeing this problem when that PR is merged.\r\n \r\n\r\n"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/bisq/issues/2754#issuecomment-486261148"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/2754#issuecomment-486261148",
"url": "https://github.com/bisq-network/bisq/issues/2754#issuecomment-486261148",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>