Troubleshooting network issues - Revision history

Jmacxx: moved Network_status_indicator to top level page

2022-08-17T21:47:22Z

moved Network_status_indicator to top level page

Jmacxx: /* Network status indicator */

2022-08-17T02:21:52Z

Network status indicator

Jmacxx: Add section for Network status indicator

2022-08-17T02:07:58Z

Add section for Network status indicator

W000000t: /* 3/4 connection problem */

2022-06-29T17:54:16Z

3/4 connection problem

Jmacxx: Added section on 3/4 connection problem

2022-05-29T20:44:16Z

Added section on 3/4 connection problem

Plebeian9000: improve page organization

2020-06-19T05:25:03Z

improve page organization

Plebeian9000: Plebeian9000 moved page Tor & connectivity to Troubleshooting network issues: wikify page title

2020-06-19T01:59:57Z

Plebeian9000 moved page Tor & connectivity to Troubleshooting network issues: wikify page title

Plebeian9000: Add bits about weak internet connections and Windows antivirus; refine wording throughout.

2020-02-17T02:36:55Z

Add bits about weak internet connections and Windows antivirus; refine wording throughout.

MwithM at 10:38, 12 February 2020

2020-02-12T10:38:39Z

MwithM: /* Forks of Bitcoin(the codebase) in the same computer */

2020-02-12T10:34:53Z

Forks of Bitcoin(the codebase) in the same computer

← Older revision		Revision as of 21:47, 17 August 2022
Line 44:		Line 44:

	To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.		To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.
−
−	~~== Network status indicator ==~~
−
−	~~[''feature, TBD, in development'']~~
−
−	There is an icon in the bottom right footerbar to indicate the the status of the P2P network connection. It will be either red, yellow or green depending on the count and type of connections your node has. Hover over it with the mouse to see the connections detail, or click on it to get a description of the error state. This indicator has been added because some Bisq nodes get unknowingly stuck in a state of not accepting inbound connections, and therefore never getting any takers for their offers. If the status remains yellow for more than 30 minutes, the Bisq node will do a self-ping test over Tor in order to check incoming connectivity. If this test fails, a popup will appear describing the problem.
−
−	'''Red''' - An error situation- there are no P2P network connections. This would usually indicate that your internet connection has broken. Check other network applications such as a web browser. Bisq cannot function properly in this state.
−
−	~~'''Yellow''' - there are outbound but no inbound connections. This could be normal if there has not been enough uptime for peers to discover and connect to your node.~~
−	Bisq can operate in this state, but it is sub-optimal. It could mean that inbound connections are blocked, the result being your offers would not be reachable. (Peers would be frustrated with the response "Maker_Offline" as a result of trying to take your offer).
−	~~If this condition persists for more than a few hours, clear the Tor cache and restart Bisq by clicking on: Settings -> Network Info -> Open Tor Settings -> [Delete outdated Tor files and shut down].~~
−
−	~~'''Green''' - the P2P connection is healthy, as you have a mix of outbound and inbound connections.~~

@@ Line 49: / Line 49: @@
 [''feature, TBD, in development'']
-There is an icon in the bottom right footerbar to indicate the the status of the P2P network connection.  It will be either red, yellow or green depending on the count and type of connections your node has.  Hover over it with the mouse to see the connections detail, or click on it to get a description of the error state.  This indicator has been added because some users get unknowingly stuck in a state of not accepting inbound connections, and therefore never getting any takers for their offers.  If the status remains yellow for more than 30 minutes, the Bisq node will do a self-ping test over Tor in order to check incoming connectivity.  If this test fails, a popup will appear describing the problem.
+There is an icon in the bottom right footerbar to indicate the the status of the P2P network connection.  It will be either red, yellow or green depending on the count and type of connections your node has.  Hover over it with the mouse to see the connections detail, or click on it to get a description of the error state.  This indicator has been added because some Bisq nodes get unknowingly stuck in a state of not accepting inbound connections, and therefore never getting any takers for their offers.  If the status remains yellow for more than 30 minutes, the Bisq node will do a self-ping test over Tor in order to check incoming connectivity.  If this test fails, a popup will appear describing the problem.
 '''Red''' - An error situation- there are no P2P network connections.  This would usually indicate that your internet connection has broken.  Check other network applications such as a web browser.  Bisq cannot function properly in this state.

← Older revision		Revision as of 02:07, 17 August 2022
Line 44:		Line 44:

	To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.		To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.
		+
		+	== Network status indicator ==
		+
		+	[''feature, TBD, in development'']
		+
		+	There is an icon in the bottom right footerbar to indicate the the status of the P2P network connection. It will be either red, yellow or green depending on the count and type of connections your node has. Hover over it with the mouse to see the connections detail, or click on it to get a description of the error state. This indicator has been added because some users get unknowingly stuck in a state of not accepting inbound connections, and therefore never getting any takers for their offers. If the status remains yellow for more than 30 minutes, the Bisq node will do a self-ping test over Tor in order to check incoming connectivity. If this test fails, a popup will appear describing the problem.
		+
		+	'''Red''' - An error situation- there are no P2P network connections. This would usually indicate that your internet connection has broken. Check other network applications such as a web browser. Bisq cannot function properly in this state.
		+
		+	'''Yellow''' - there are outbound but no inbound connections. This could be normal if there has not been enough uptime for peers to discover and connect to your node.
		+	Bisq can operate in this state, but it is sub-optimal. It could mean that inbound connections are blocked, the result being your offers would not be reachable. (Peers would be frustrated with the response "Maker_Offline" as a result of trying to take your offer).
		+	If this condition persists for more than a few hours, clear the Tor cache and restart Bisq by clicking on: Settings -> Network Info -> Open Tor Settings -> [Delete outdated Tor files and shut down].
		+
		+	'''Green''' - the P2P connection is healthy, as you have a mix of outbound and inbound connections.

← Older revision		Revision as of 17:54, 29 June 2022
Line 14:		Line 14:

	See https://github.com/bisq-network/bisq/issues/2547#issuecomment-1016787843		See https://github.com/bisq-network/bisq/issues/2547#issuecomment-1016787843
		+
		+	For a geekier approach, you can also try [[Manually_select_seednodes\|manually choosing seednodes to connect to]]

	== Windows antivirus software ==		== Windows antivirus software ==

← Older revision		Revision as of 20:44, 29 May 2022
Line 6:		Line 6:

	Bisq generally needs a strong, fast connection to work properly. Tethering on mobile connections can work but is known to cause issues.		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 <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.
		+
		+	See https://github.com/bisq-network/bisq/issues/2547#issuecomment-1016787843

	== Windows antivirus software ==		== Windows antivirus software ==

@@ 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 might be because your ISP or network provider is actively blocking Tor.
+== Weak internet connection ==
-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.
+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 on Bisq's Tor screen:
+== Windows antivirus software ==
-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).
+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.
-==Other Known connection issues==
+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.
-====Windows Antivirus Software====
+== Tor censorship ==
-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.
+In certain situations, Bisq may fail to start because your ISP or network provider is actively blocking Tor.
-====Weak Internet Connections====
+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.
-Bisq generally needs a strong, fast connection to work properly. Tethering on mobile connections can work but is known to have issues.
+If you're in China, [[在中国运行Bisq_(Running_Bisq_in_China)|this method using SStap]] has worked to get around the Great Firewall.
-====Altcoin Nodes Running on the Same Computer====
+==Tor bridges that don't work ==
-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.
+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.
-To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.
+In these scenarios, consider using a VPN and then running Bisq from within the VPN tunnel.
-==Tor Bridges that don't work==
+== Altcoin nodes running on the same computer ==
-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.
+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.
-When that happens, consider using a VPN and then running Bisq from within the VPN tunnel.
+To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.

← Older revision	Revision as of 01:59, 19 June 2020
(No difference)

@@ Line 8: / Line 8: @@
 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).
 ==Other Known connection issues==
 ====Forks of Bitcoin (the codebase) in the same computer====