[bisq-network/bisq] Bisq tries to connect to local (pruned) node even if I specified custom node IP address. (#4303)

[Vincas Dargis]

### Description
I've been using `Use custom Bitcoin Core node` for quite some time. It lives on different computer on may LAN.

Recently I've started using _second_ instance of bitcoind, running on my laptop, in pruned mode.

`Use custom Bitcoin Core node` is still set, but Bisq still tries (and fails) and fails to use that local node:
```
birž.-14 14:56:35.702 [PeerGroup Thread] INFO  org.bitcoinj.core.PeerGroup: Attempting connection to [127.0.0.1]:8333     (0 connected, 1 pending, 1 max)    
birž.-14 14:56:35.702 [NioClientManager] INFO  o.b.net.NioClientManager: Connected to /127.0.0.1:8333                                                        
birž.-14 14:56:35.702 [NioClientManager] INFO  org.bitcoinj.core.Peer: Announcing to /127.0.0.1:8333 as: /bitcoinj:0.14.7.bisq.1-SNAPSHOT/Bisq:1.3.4/ 
birž.-14 14:56:35.703 [NioClientManager] INFO  org.bitcoinj.core.Peer: [127.0.0.1]:8333: Got version=70015, subVer='/Satoshi:0.18.1/', services=0x1036, time=
2020-06-14 14:56:35, blocks=634697                                                                                                                           
birž.-14 14:56:35.704 [NioClientManager] INFO  org.bitcoinj.core.Peer: [127.0.0.1]:8333: Peer does not have a copy of the block chain.         
birž.-14 14:56:35.704 [NioClientManager] INFO  org.bitcoinj.core.PeerGroup: [127.0.0.1]:8333: Peer died      (0 connected, 0 pending, 1 max)
```

#### Version

v1.3.4, built from Git.

### Steps to reproduce

- Set `Use custom Bitcoin Core node` option and specify custom archival butcoind IP address.
- Launch local pruned `bitcoind`.
- Start Bisq.


### Expected behaviour

Bisq should not use local node if custom node IP address is explicitly specified.

### Actual behaviour

Bsiq trys to use bitcoind on localhost even if custom node IP address is specified.

### Screenshots



#### Device or machine

Debian Sid amd64.

#### Additional info



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/4303
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200614/93351988/attachment.html>