# Can't connect to localhost fullnode **URL:** \ **Category:** Support\ **Created:** [April 23, 2018, 7:32pm UTC](https://bisq.community/t/cant-connect-to-localhost-fullnode/5315 "2018-04-23T19:32:17Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mcfly](https://bisq.community/letter_avatar/mcfly/32/5_5575768a8748004e209b776fc1b2916d.png) [@mcfly](https://bisq.community/u/mcfly)\ **Post date:** [April 23, 2018, 7:32pm UTC](https://bisq.community/t/cant-connect-to-localhost-fullnode/5315/1 "2018-04-23T19:32:17Z")
After starting bisq, it hangs just after I type my password. It looks like I’m getting an alert of some kind…saying I need to upgrade. Here’s the section from the log: ``` Apr-23 14:04:38.723 [PeerGroup Thread] INFO o.b.c.PeerGroup: Attempting connection to [127.0.0.1]:8333 (0 connected, 1 pending, 1 max) Apr-23 14:04:38.731 [NioClientManager] INFO o.b.n.NioClientManager: Connected to /127.0.0.1:8333 Apr-23 14:04:38.731 [NioClientManager] INFO o.b.core.Peer: Announcing to /127.0.0.1:8333 as: /bitcoinj:0.14.4/Bisq:0.6.7/ Apr-23 14:04:38.734 [NioClientManager] INFO o.b.core.Peer: [127.0.0.1]:8333: Got version=70015, subVer='/Satoshi:0.16.0/', services=0x1037, time=2018-04-23 14:04:38, blocks=519618 Apr-23 14:04:38.744 [NioClientManager] INFO o.b.c.PeerGroup: [127.0.0.1]:8333: New peer (1 connected, 0 pending, 1 max) Apr-23 14:04:38.745 [NioClientManager] INFO o.b.c.PeerGroup: Setting download peer: [127.0.0.1]:8333 Apr-23 14:04:38.745 [NioClientManager] INFO o.b.c.l.DownloadProgressTracker: Chain download switched to [127.0.0.1]:8333 Apr-23 14:04:38.746 [NioClientManager] INFO o.b.core.Peer: Received alert from peer [127.0.0.1]:8333: URGENT: Alert key compromised, upgrade required Apr-23 14:04:38.759 [NioClientManager] INFO o.b.core.Peer: Passed the fast catchup time (2017-11-07T20:37:27Z) at height 493519, discarding 2000 headers and requesting full blocks Apr-23 14:04:38.767 [NioClientManager] INFO o.b.c.PeerGroup: [127.0.0.1]:8333: Peer died (0 connected, 0 pending, 1 max) Apr-23 14:04:38.767 [NioClientManager] INFO o.b.c.PeerGroup: Download peer died. Picking a new one. Apr-23 14:04:38.767 [NioClientManager] INFO o.b.c.PeerGroup: Unsetting download peer: [127.0.0.1]:8333 ``` Anyone know why my bitcoind is complaining? Thanks! ---
**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\ **Post date:** [April 23, 2018, 8:31pm UTC](https://bisq.community/t/cant-connect-to-localhost-fullnode/5315/2 "2018-04-23T20:31:14Z")
I don’t think that alert is anything unusual or useful. Does Bisq work correctly when you don’t run a local node? ---
**Author:** ![mcfly](https://bisq.community/letter_avatar/mcfly/32/5_5575768a8748004e209b776fc1b2916d.png) [@mcfly](https://bisq.community/u/mcfly)\ **Post date:** [April 24, 2018, 12:20am UTC](https://bisq.community/t/cant-connect-to-localhost-fullnode/5315/3 "2018-04-24T00:20:02Z")
Yes, but once I start my node, it drops the other connections and tries (and fails) to connect to 127.0.0.1. ---
**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\ **Post date:** [April 24, 2018, 8:45am UTC](https://bisq.community/t/cant-connect-to-localhost-fullnode/5315/4 "2018-04-24T08:45:46Z")
It is supposed to drop connections to other nodes, when a local node is available. I am not sure why it fails though. Quite odd. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [April 24, 2018, 9:42pm UTC](https://bisq.community/t/cant-connect-to-localhost-fullnode/5315/5 "2018-04-24T21:42:52Z")
Seems you have some local Bitcoin node running but it does not accept connections. ---
**Author:** ![mcfly](https://bisq.community/letter_avatar/mcfly/32/5_5575768a8748004e209b776fc1b2916d.png) [@mcfly](https://bisq.community/u/mcfly)\ **Post date:** [April 25, 2018, 2:03am UTC](https://bisq.community/t/cant-connect-to-localhost-fullnode/5315/6 "2018-04-25T02:03:43Z")
I’m also running a lightning node (lnd) that uses my local node as a backend. Maybe lnd doesn’t want to share… I’ll experiment and see if I can narrow it down.