Troubleshooting network issues

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.

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.