Difference between revisions of "Troubleshooting network issues"

From Bisq Wiki
Jump to navigation Jump to search
m (moved Network_status_indicator to top level page)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
You may be experiencing '''network issues''' if you're stuck on Bisq's initial loading screen for a while. Often this results in a screen mentioning outdated Tor files and other Tor settings. This could occur for a number of reasons.
  
 +
__TOC__
  
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.
+
== Weak internet connection ==
  
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.
+
Bisq generally needs a strong, fast connection to work properly. Tethering on mobile connections can work but is known to cause issues.
  
They look like this, and should be inserted in Bisq's Tor screen:
+
== 3/4 connection problem ==
  
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).
+
If Bisq stalls at step 3/4 of the startup sequence for more than 5 minutes it means the initial data download from seednodes has failed, or is taking too long.
 +
This can happen on weak or slow internet connections, or if Tor is having issues relaying the large data download to your node.
 +
Proposed mitigation is to clear the Tor cachefiles. (Close Bisq first). All files except <code>hiddenservice</code> can be deleted from <code>btc_mainnet/tor</code> beneath the [[https://bisq.wiki/Data_directory#Default_locations data directory]], they will be re-created as necessary at startup.  <code>hiddenservice</code> should be kept as it defines your onion address.
  
==Other Known connection issues==
+
See https://github.com/bisq-network/bisq/issues/2547#issuecomment-1016787843
====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 :)
+
For a geekier approach, you can also try [[Manually_select_seednodes|manually choosing seednodes to connect to]]
  
To solve this issue, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.
+
== Windows antivirus software ==
  
==Tor Bridges that don't work==
+
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.
  
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.
+
== Being temporarily banned by the Tor network ==
  
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.
+
Trying to open Bisq too many times in a short timeframe can result in failing to connect to the Tor network. Simple wait 30-60 minutes and then try opening Bisq again.
 +
 
 +
== Tor censorship ==
 +
 
 +
In certain situations, Bisq may fail to start because your ISP or network provider is actively blocking Tor.
 +
 
 +
Tor is tries to fight such obstacles by providing ''bridges''. Bridges help you connect to the Tor network 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.
 +
 
 +
If you're in China, [[在中国运行Bisq_(Running_Bisq_in_China)|this method using SStap]] has worked to get around the Great Firewall.
 +
 
 +
==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 and handshakes.
 +
 
 +
In these scenarios, consider using a VPN and then running Bisq from within the VPN tunnel.
 +
 
 +
== 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.

Latest revision as of 21:47, 17 August 2022

You may be experiencing network issues if you're stuck on Bisq's initial loading screen for a while. Often this results in a screen mentioning outdated Tor files and other Tor settings. This could occur for a number of reasons.

Weak internet connection

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

3/4 connection problem

If Bisq stalls at step 3/4 of the startup sequence for more than 5 minutes it means the initial data download from seednodes has failed, or is taking too long. This can happen on weak or slow internet connections, or if Tor is having issues relaying the large data download to your node. Proposed mitigation is to clear the Tor cachefiles. (Close Bisq first). All files except hiddenservice can be deleted from btc_mainnet/tor beneath the [data directory], they will be re-created as necessary at startup. hiddenservice should be kept as it defines your onion address.

See https://github.com/bisq-network/bisq/issues/2547#issuecomment-1016787843

For a geekier approach, you can also try manually choosing seednodes to connect to

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.

Being temporarily banned by the Tor network

Trying to open Bisq too many times in a short timeframe can result in failing to connect to the Tor network. Simple wait 30-60 minutes and then try opening Bisq again.

Tor censorship

In certain situations, Bisq may fail to start because your ISP or network provider is actively blocking Tor.

Tor is tries to fight such obstacles by providing bridges. Bridges help you connect to the Tor network 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.

If you're in China, this method using SStap has worked to get around the Great Firewall.

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 and handshakes.

In these scenarios, consider using a VPN and then running Bisq from within the VPN tunnel.

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.