Can't reach my node

[simpic]

Hello, I'm using Bitcoin Core 24.0 on Ubuntu 20.04.

I have installed tor 0.4.2.7-1 and made these changes to "/etc/tor/torrc":

uncommented this:

Code:

ControlPort 9051
CookieAuthentication 1

added this line:

Code:

CookieAuthFileGroupReadable 1

I run Bitcoin Core with this command:

bitcoind -conf=<my_path>/bitcoin.conf -proxy=127.0.0.1:9050 -debug=tor

Here is part of the debug.log file:

2022-12-09T21:41:56Z New outbound peer connected: version: 70016, blocks=766684, peer=0 (block-relay-only)
2022-12-09T21:41:57Z New outbound peer connected: version: 70016, blocks=766684, peer=1 (block-relay-only)
2022-12-09T21:42:02Z No valid UPnP IGDs found
2022-12-09T21:42:07Z New outbound peer connected: version: 70016, blocks=766684, peer=3 (outbound-full-relay)
2022-12-09T21:42:20Z Imported mempool transactions from disk: 3248 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2022-12-09T21:42:20Z loadblk thread exit
2022-12-09T21:42:28Z New outbound peer connected: version: 70016, blocks=766684, peer=4 (outbound-full-relay)
2022-12-09T21:42:37Z New outbound peer connected: version: 70016, blocks=766684, peer=7 (outbound-full-relay)
2022-12-09T21:42:39Z P2P peers available. Skipped DNS seeding.
2022-12-09T21:42:39Z dnsseed thread exit
2022-12-09T21:43:03Z Socks5() connect to 2001:41d0:700:2052:::8333 failed: general failure
2022-12-09T21:43:04Z New outbound peer connected: version: 70016, blocks=766684, peer=9 (outbound-full-relay)
2022-12-09T21:43:30Z New outbound peer connected: version: 70016, blocks=766684, peer=13 (outbound-full-relay)
2022-12-09T21:43:32Z New outbound peer connected: version: 70016, blocks=766684, peer=14 (outbound-full-relay)
2022-12-09T21:43:34Z New outbound peer connected: version: 70016, blocks=766684, peer=15 (outbound-full-relay)
2022-12-09T21:43:35Z New outbound peer connected: version: 70016, blocks=766684, peer=16 (outbound-full-relay)
2022-12-09T21:44:37Z New outbound peer connected: version: 70016, blocks=766684, peer=17 (outbound-full-relay)
2022-12-09T21:45:38Z New outbound peer connected: version: 70016, blocks=766684, peer=18 (outbound-full-relay)
2022-12-09T21:47:10Z No valid UPnP IGDs found

For "No valid UPnP IGDs found" message I have commented

Code:

upnp=1

line in bitcoin.conf file, but I'm still getting Socks5() connect to ... failed: general failure.
Can you tell me what that address (2001:41d0:700:2052:::8333) came from?

I also tried to connect Electrum to it with the following command:

Code:

electrum -1 -s <my_address>.onion:8333:t -p socks5:localhost:9050

but it hangs on "not connected"...

What am I missing?

[1714473268]

1714473268

[1714473268]

1714473268

[1714473268]

1714473268

[1714473268]

1714473268

[simpic]

I have added the user to "debian-tor" group, as described here and now I get this:

Socks5() connect to yuj6mmcy737xlaq7hz3abwslckwzuqdp73w7ipuqs22tq432nc4b7dad.onion:8333 failed: host unreachable

Now, and again, what that address is coming from?


Edit: new log lines

2022-12-09T23:23:15Z Socks5() connect to 134.122.40.106:8446 failed: general failure
2022-12-09T23:23:42Z Socks5() connect to 240e:390:240:6f70::1001:8333 failed: general failure
2022-12-09T23:23:44Z New outbound peer connected: version: 70015, blocks=766693, peer=7 (outbound-full-relay)
2022-12-09T23:23:45Z New outbound peer connected: version: 70016, blocks=766693, peer=6 (outbound-full-relay)
2022-12-09T23:23:54Z P2P peers available. Skipped DNS seeding.
2022-12-09T23:23:54Z dnsseed thread exit
2022-12-09T23:24:04Z New outbound peer connected: version: 70016, blocks=766693, peer=10 (outbound-full-relay)
2022-12-09T23:24:06Z New outbound peer connected: version: 70016, blocks=766693, peer=11 (outbound-full-relay)
2022-12-09T23:24:07Z New outbound peer connected: version: 70016, blocks=766693, peer=12 (outbound-full-relay)
2022-12-09T23:24:08Z New outbound peer connected: version: 70016, blocks=766693, peer=13 (outbound-full-relay)

[nc50lc]

I also tried to connect Electrum to it with the following command:

You need any implementation of Electrum Server to be able to connect your Bitcoin Core to Electrum.
You can try: https://github.com/spesmilo/electrumx - from the main developer of Electrum.

[simpic]

I also tried to connect Electrum to it with the following command:

You need any implementation of Electrum Server to be able to connect your Bitcoin Core to Electrum.
You can try: https://github.com/spesmilo/electrumx - from the main developer of Electrum.

Ok, so before this I will try to connect using Bitcoin Core from another computer...
Do you have any hint for doing that?

[nc50lc]

-snip-

Ok, so before this I will try to connect using Bitcoin Core from another computer...
Do you have any hint for doing that?

I can't reliably tell based from the available info.
But since you've used -proxy, -listen is automatically disabled which made your node unreachable
So try to add "-listen=1" to the command or "listen=1" to your bitcoin.conf file.

Also, if you decided to try the suggestion above, prioritize "addnode" since "connect" will limit you to the nodes that you've set.

[simpic]

You need any implementation of Electrum Server to be able to connect your Bitcoin Core to Electrum.
You can try: https://github.com/spesmilo/electrumx - from the main developer of Electrum.

Anyway, should reachability of a node be agnostic about running with Bitcoin Core, ElectrumX o other?

I can't reliably tell based from the available info.
But since you've used -proxy, -listen is automatically disabled which made your node unreachable
So try to add "-listen=1" to the command or "listen=1" to your bitcoin.conf file.

Ok, I removed "-proxy" parameter from the command:

bitcoind -conf=<my_path>/bitcoin.conf -debug=tor

Here is my bitcoin.conf file:

### IPv4/IPv6 mode ###
# This mode requires uPnP feature on your router to allow Bitcoin Core to accept incoming connections.
bind=0.0.0.0
#upnp=1

### Tor mode ###
# This mode requires tor (https://www.torproject.org/download/) to be running at the proxy address below.
# No configuration is needed on your router to allow Bitcoin Core to accept incoming connections.
#proxy=127.0.0.1:9050
bind=127.0.0.1
#onlynet=onion

listen=1
port=8333
maxconnections=64

dbcache=64
par=2
checkblocks=24
checklevel=0

disablewallet=1
server=1

datadir=<my_path>/.bitcoin
daemon=1

rpccookiefile=<my_path>/.bitcoin/.cookie
rpcbind=127.0.0.1
rpcport=8332
rpcallowip=127.0.0.1

I also commented "proxy" parameter here, unlike described here.
Are you sure I have to remove it?

[nc50lc]

I also commented "proxy" parameter here, unlike described here.
Are you sure I have to remove it?

No, I only suggested to add -listen=1 but leave -proxy parameter since you need it.
It's just if there's no -listen=1 while -proxy is used, listen will be set to 'disabled'.

[simpic]

I'm back

I installed electrs but when I run it I get the following error:

[2023-01-23T15:36:51.500Z INFO  electrs::db] closing DB at /<my_user>/.electrs/db/bitcoin
Error: electrs failed

Caused by:
    0: failed to open bitcoind cookie file: /<my_user>/.bitcoin/.cookie
    1: No such file or directory (os error 2)

But ".cookie" file is created only when Bitcoin Core daemon is running. Have I to run both Bitcoin Core and electrs?!?


Anyway, running both I get another error:

[2023-01-23T15:35:26.817Z INFO  electrs::db] closing DB at /<my_user>/.electrs/db/bitcoin
Error: electrs failed

Caused by:
    0: bitcoind RPC polling failed
    1: daemon not available
    2: JSON-RPC error: transport error: Didn't receive response data in time, timed out.

What is wrong?

[BlackHatCoiner]

Is there a particular tutorial you're following, or you're just setting up this yourself? If it's the latter, you might have not understood something properly in the process of installation.

0: bitcoind RPC polling failed

Do you bind locally? What's rpcbind in your configuration file?

1: daemon not available

Isn't bitcoind running?

[simpic]

Seems the problem was that Bitcoin Core not 100% synched...