Topic: No incoming connections while I should be getting (Read 119 times)
Yep, it worked. Thanks!
From what i've seen, most guide about setting Onion Service on Bitcoin Core usually enable bind=127.0.0.1. Enable it first and restart your Bitcoin Core process.
This is my bitcoin.conf:
As you can see I only relay through Tor. Due to the easiness Tor provides, I theoretically can contribute to the network's bandwidth by allowing incoming connections without having to port forward anything. However, I don't understand why I get 0 incoming connections.
Isn't listen=1 and listenonion=1 enough? What do I do wrong?
Code:
# RaspiBolt: bitcoind configuration
# /mnt/ext/bitcoin/bitcoin.conf
# Bitcoin daemon
server=1
txindex=1
# Network
listen=1
listenonion=1
proxy=127.0.0.1:9050
onlynet=onion
#bind=127.0.0.1
# Connections
rpcuser=[USER]
rpcpassword=[PASS]
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
# /mnt/ext/bitcoin/bitcoin.conf
# Bitcoin daemon
server=1
txindex=1
# Network
listen=1
listenonion=1
proxy=127.0.0.1:9050
onlynet=onion
#bind=127.0.0.1
# Connections
rpcuser=[USER]
rpcpassword=[PASS]
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333
As you can see I only relay through Tor. Due to the easiness Tor provides, I theoretically can contribute to the network's bandwidth by allowing incoming connections without having to port forward anything. However, I don't understand why I get 0 incoming connections.
Isn't listen=1 and listenonion=1 enough? What do I do wrong?
Jump to: