Error: "We did not receive a filter object from the seed nodes"

[so7ow]

Description

Version

1.9.2

Steps to reproduce

Launch Bisq.

Expected behaviour

No error.

Actual behaviour

Error.

Screenshots

Device or machine

Docker image fflo/bisq-on-docker running on Synology 1815+, DSM 7.1-42661 update 2.

Additional info

[boring-cyborg[bot]]

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

[kwall2020]

Same

[ripcurlx]

This is unfortunately still related to the choppy Tor connection based on the DDoS attack on the Tor network: https://status.torproject.org/

[stone212]

@ripcurlx

This was not happening for me on the same connection on 1.8.?. It only started when I upgraded. So maybe it's not due to the Tor connection? Or did the problem exist but 1.9.4 introduced the error message?

[jmacxx]

It is strongly correlated with the DDoS. Many users started reporting the error at the same time, as a result one of our support agents @w0000000t created this workaround to manually select functioning seednodes.

[Menziess]

I'm having the issue right now. v3 Onion Services: Disrupted

[so7ow]

Haven't seen this since the initial report.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.