LedgerHQ / satstack

Bitcoin full node with Ledger Live
BSD 2-Clause "Simplified" License
159 stars 32 forks source link

Ledger Live Could not reach Full Node #88

Closed dannuttall closed 1 year ago

dannuttall commented 1 year ago

I have a Bitcoin full node set up on a RPi4, running raspiblitz

I am trying to connect to it from Ledger Live which is running on a different computer on my local network, but keep getting the "Could not reach full node" message. I am using the local IP of the RP4 with 8332 port. Have tried both TLS on and off to no avail.

I have changed the bitcoin.conf settings "disablewallet" to 0, "txindex" to 1, and added the computer I'm running Ledger Live on to the rpcallowip list. See below for full config.

Am I missing something as to why this isn't working?

# mainnet/testnet
testnet=0

# Bitcoind options
server=1
daemon=1
txindex=1
disablewallet=0
peerbloomfilters=1
datadir=/mnt/hdd/bitcoin

# Connection settings
rpcuser=raspibolt
rpcpassword=xxxxxxxx
main.rpcport=8332
test.rpcport=18332
rpcallowip=127.0.0.1
rpcallowip=192.168.1.213
main.rpcbind=127.0.0.1:8332
test.rpcbind=127.0.0.1:18332
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333

# Raspberry Pi optimizations
dbcache=128
maxorphantx=10
maxmempool=300
maxconnections=40
maxuploadtarget=5000

# tor by default
onlynet=onion
proxy=127.0.0.1:9050
main.bind=127.0.0.1
test.bind=127.0.0.1
dnsseed=0
dns=0
adrienlacombe commented 1 year ago

hi @dannuttall thank you for give it a go :) what error are you having exactly? thank you!

dannuttall commented 1 year ago

image

image

Details all correct and Bitcoin node fully synced.

I assumed it would work because the requirements referenced Raspiblitz users. What scenario can someone run a Raspiblitz node and use ledger if not via another computer on the local network?

dannuttall commented 1 year ago

ok I figured it out. Tried locating the bitcoin.conf file on raspiblitz by blindly listing directories. i.e. ran command "ls". Then checking out the assets folder and running "ls" in there, which included a "bitcoin.conf" file, which is what I then amended. Have since realised I need the bitcoin.conf file located on the mnt. Amended that and it's now all working

adrienlacombe commented 1 year ago

thank you!