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? |
|
|
|
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 unreachableNow, 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) |
|
|
|
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: ControlPort 9051
CookieAuthentication 1 added this line: CookieAuthFileGroupReadable 1 I run Bitcoin Core with this command: bitcoind -conf=<my_path>/bitcoin.conf -proxy=127.0.0.1:9050 -debug=torHere 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 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: electrum -1 -s <my_address>.onion:8333:t -p socks5:localhost:9050 but it hangs on "not connected"... What am I missing? |
|
|
|
This is very interesting to see, it could be even better than using Rpi if everything works ok, and it is certainly better than to throw away your android phone in garbage.
I guess phone needs to be connected to power all the time, but I am wondering how is it handling hard drive space, can you also use 1TB micro SD card or faster SSD drive?
The installation is for external drives connected using an OTG USB cable. So you can attach whatever you want, including SD card or SSD drive. It's nice to see code released on github, but you should add license information if it's open source. Added, thank you for the hint. |
|
|
|
 It looks a bit like a phone booth, but it's a full node made with what I had at home: an old android smartphone and an old 3.5'' hdd Would you try to do the same? https://github.com/smartm0use/smartino |
|
|
|
Ma senza dimenticare "Persiste ostinatamente la convinzione che si debba dare spazio all'innovazione a tutti i costi." scommetto che pure chi andava in giro ad accendere le candele o allevava cavalli diceva le stesse cose.
Sì, anche quella frase, so' rimasto impietrito quando l'ho letta! |
|
|
|
|
Ok, I solved, thank you so much.
|
|
|
|
Remove the local .bitcoin folder ( rm -rf /root/.bitcoin). You may need to add: Why this? |
|
|
|
Now I have tried to launch "bitcoin-cli getblockchaininfo" but it is still looking for default data dir: cannot create directories: File exists [/root/.bitcoin/wallets] bitcoin in AppInitRPC() How to change this behaviour? Here is the content of 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 #rpccookiefile=/root/bitcoin-core/.bitcoin/.cookie rpcbind=127.0.0.1 rpcport=8332 rpcallowip=127.0.0.1 And this is the command I run: /root/bitcoin-core/bin/bitcoind -conf=/mnt/media/<UUID>/.bitcoin/bitcoin.conf -datadir=/mnt/media/<UUID>/.bitcoin -daemon |
|
|
|
|
It was hardcoded in "bitcoin.conf" file, I just removed it and now it works.
As said by n0nce, Bitcoin Core saves the cookie in the data directory... that I passed as parameter to "bitcoind" command.
Thank you for your replies.
|
|
|
|
Hello, I have installed Bitcoin Core on Ubuntu 20 and I changed the path of ".bitcoin" folder. When I run "bitcoind" file it does not create "bitcoind.pid" file, as instead it does on another computer. Since the current instance file is not created the client crashes: 2022-11-29T16:56:38Z Bitcoin Core version v23.0.0 (release build)
2022-11-29T16:56:38Z Assuming ancestors of block 000000000000000000052d314a259755ca65944e68df6b12a067ea8f1f5a7091 have valid signatures.
2022-11-29T16:56:38Z Setting nMinimumChainWork=00000000000000000000000000000000000000002927cdceccbd5209e81e80db
2022-11-29T16:56:38Z Using the 'arm_shani(1way,2way)' SHA256 implementation
2022-11-29T16:56:38Z Default data directory /root/.bitcoin
2022-11-29T16:56:38Z Using data directory /mnt/media/<UUID>/.bitcoin
2022-11-29T16:56:38Z Config file: /mnt/media/<UUID>/.bitcoin/bitcoin.conf
2022-11-29T16:56:38Z Config file arg: bind="0.0.0.0"
2022-11-29T16:56:38Z Config file arg: checkblocks="24"
2022-11-29T16:56:38Z Config file arg: checklevel="0"
2022-11-29T16:56:38Z Config file arg: dbcache="64"
2022-11-29T16:56:38Z Config file arg: disablewallet="1"
2022-11-29T16:56:38Z Config file arg: listen="1"
2022-11-29T16:56:38Z Config file arg: maxconnections="64"
2022-11-29T16:56:38Z Config file arg: par="2"
2022-11-29T16:56:38Z Config file arg: port="8333"
2022-11-29T16:56:38Z Config file arg: rpcallowip="127.0.0.1"
2022-11-29T16:56:38Z Config file arg: rpcbind=****
2022-11-29T16:56:38Z Config file arg: rpccookiefile="/root/bitcoin-core/.bitcoin/.cookie"
2022-11-29T16:56:38Z Config file arg: rpcport="8332"
2022-11-29T16:56:38Z Config file arg: upnp="1"
2022-11-29T16:56:38Z Command-line arg: conf="/mnt/media/<UUID>/.bitcoin/bitcoin.conf"
2022-11-29T16:56:38Z Command-line arg: daemon=""
2022-11-29T16:56:38Z Command-line arg: datadir="/mnt/media/<UUID>/.bitcoin"
2022-11-29T16:56:38Z Using at most 64 automatic connections (32768 file descriptors available)
2022-11-29T16:56:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2022-11-29T16:56:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2022-11-29T16:56:38Z Script verification uses 1 additional threads
2022-11-29T16:56:38Z Wallet disabled!
2022-11-29T16:56:38Z scheduler thread start
2022-11-29T16:56:38Z HTTP: creating work queue of depth 16
2022-11-29T16:56:38Z Using random cookie authentication.
2022-11-29T16:56:38Z Unable to open cookie authentication file /root/bitcoin-core/.bitcoin/.cookie.tmp for writing
2022-11-29T16:56:38Z Error: Unable to start HTTP server. See debug log for details.
2022-11-29T16:56:38Z Shutdown: In progress...
2022-11-29T16:56:38Z scheduler thread exit
2022-11-29T16:56:38Z Shutdown: done Do you see any useful hint in this log file? Why the client still use default data directory for some paths? What could be the problem? I have also tried versione 24.0, but nothing changed. |
|
|
|
Ancora un'attività accetta pagamenti in bitcoin:  |
|
|
|
Nuova attività:  |
|
|
|
|
Show Posts
