Difference between revisions of "Troubleshooting network issues"

From Bisq Wiki
Jump to navigation Jump to search
(Add bits about weak internet connections and Windows antivirus; refine wording throughout.)
Line 1: Line 1:
  
  
If you're stuck on Bisq's initial loading screen for a while and then you are shown a screen about Tor it is probably because you ISP or network provider is actively blocking Tor.
+
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 actively working against these ISPs that block it by providing bridges. These bridges help you hop into the tor network through a not so known node. You can either know someone who runs a bridge and ask them for the details or you can go to https://bridges.torproject.org/bridges to get your own.
+
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 in Bisq's Tor screen:  
+
They look like this, and should be inserted on Bisq's Tor screen:  
  
Note that the picture is only illustrative, the Bridges shown 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 uncensorability here).
+
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==
 
==Other Known connection issues==
====Forks of Bitcoin (the codebase) in the same computer====
 
  
Some forks of the Bitcoin repository (i.e. Litecoin, Dogecoin and more) are known to affect Bisq's connectivity setup. These forks are recognized by Bisq as a local Bitcoin node and Bisq attempts to connect to them to find Bisq related transactions. That will never work, as Litecoin blockchain have no Bisq related transactions :)
+
====Windows Antivirus Software====
  
To solve this issue, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.
+
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==
 
==Tor Bridges that don't work==
  
Some network administrators try really hard to block any Tor activity in their network (Universities in particular) and go as far as blocking specific types of SSL traffic & handshakes.
+
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 you can use a VPN to connect your computer to their network and then have Bisq use Tor from within the VPN tunnel to connect to the Bitcoin network.
+
When that happens, consider using a VPN and then running Bisq from within the VPN tunnel.

Revision as of 02:36, 17 February 2020


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.