Troubleshooting network issues

From Bisq Wiki
Revision as of 02:36, 17 February 2020 by Plebeian9000 (talk | contribs) (Add bits about weak internet connections and Windows antivirus; refine wording throughout.)
Jump to navigation Jump to search


If you're stuck on Bisq's initial loading screen for a while and then you are shown a screen about Tor it might be because your ISP or network provider is actively blocking Tor.

Tor is tries to fight these obstacles by providing bridges. Bridges help you hop onto Tor through a less well-known node. If you know someone who runs a bridge, you can ask to use their bridge, or you can go to https://bridges.torproject.org/bridges to pick a bridge listed by the Tor Project.

They look like this, and should be inserted on Bisq's Tor screen:

Note that this picture is only for information purposes only, as bridges you should use will vary on your IP range and a series of other factors (see more about how the Tor Project team optimises the list of bridges for maximum censorship-resistance here).

Other Known connection issues

Windows Antivirus Software

Antivirus software is known to cause connection issues. Try turning it off to see if it helps Bisq to connect, and if it does, consider switching antivirus software or running Bisq on another operating system on which you don't need to run antivirus.

Weak Internet Connections

Bisq generally needs a strong, fast connection to work properly. Tethering on mobile connections can work but is known to have issues.

Altcoin Nodes Running on the Same Computer

Some forks of the Bitcoin repository (e.g., Litecoin, Dogecoin, etc) are known to cause issues with Bisq starting up. Bisq can sometimes recognize altcoin nodes as Bitcoin nodes, causing Bisq to try connecting to them and then failing when it finds no Bitcoin blocks.

To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.

Tor Bridges that don't work

Some network administrators try really hard to block all Tor activity on their network (universities are infamous for this) and will even sometimes block specific types of SSL traffic & handshakes.

When that happens, consider using a VPN and then running Bisq from within the VPN tunnel.