Bitcoin Forum
May 21, 2024, 08:10:24 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Need help connecting to full node over Tor  (Read 135 times)
Ambivilance (OP)
Newbie
*
Offline Offline

Activity: 21
Merit: 1


View Profile
March 09, 2021, 09:43:23 AM
Merited by ABCbits (1)
 #1

I have a raspberry pi with bitcoin core + electrum personal server. I would SSH into it and then run electrum with these arguments: ./electrum --oneserver --server localhost:50002:S . I later created a tor hidden service and got an onion address. I tried this: ./electrum --oneserver --server myOnion:50001:t -p socks5:localhost9050 and it would not connect.

On bitnodes my onion is up, though it does not say Tor under the network description, like it does for others. I forwarded port 8333.

I have these in the bitcoin.conf:

proxy=127.0.0.1:9050

listen=1

bind=127.0.0.1

I am unsure what I am meant to do. I want to connect to it through electrum and I want the maximum privacy, so I don't other people to be able to query my node. Am I meant to just do what I did before (./electrum --oneserver --server localhost:50002:S) and it is over tor since I have walletbroadcast=0 on, or am I meant to use a hidden service, in which case, what is the correct electrum argument?

Thank you.
BitMaxz
Legendary
*
Offline Offline

Activity: 3262
Merit: 2974


Block halving is coming.


View Profile WWW
March 09, 2021, 10:10:06 AM
Merited by ABCbits (1)
 #2

Is this a Raspibolt?

Can you try this command below with verbose logging enabled

Code:
electrum -v --oneserver --server <your_onion_hidden_service>.onion:50002:s --proxy socks5:127.0.0.1:9050


But if it doesn't work try to connect Electrum using this command.

Code:
electrum -v --oneserver --server raspibolt.local:50002:s

Then update here to any errors popup here.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Ambivilance (OP)
Newbie
*
Offline Offline

Activity: 21
Merit: 1


View Profile
March 09, 2021, 10:16:07 AM
 #3

Is this a Raspibolt?

Can you try this command below with verbose logging enabled

Code:
electrum -v --oneserver --server <your_onion_hidden_service>.onion:50002:s --proxy socks5:127.0.0.1:9050


But if it doesn't work try to connect Electrum using this command.

Code:
electrum -v --oneserver --server raspibolt.local:50002:s

Then update here to any errors popup here.

Not a raspibolt, just software manually installed.
What does the -v  do? 
I will try it.
Husires
Legendary
*
Offline Offline

Activity: 1596
Merit: 1287


View Profile WWW
March 09, 2021, 11:21:53 AM
 #4

use this https://github.com/bwt-dev/bwt#electrum-plugin if you have problems with EPS
NotATether
Legendary
*
Offline Offline

Activity: 1610
Merit: 6753


bitcoincleanup.com / bitmixlist.org


View Profile WWW
March 10, 2021, 07:23:47 AM
 #5

Are you sure you are connecting to the hidden service at the correct port? If the logs say something like this:

Code:
I/i | interface.[mic3bk5pvma4ng7zkc3kdjmr2vv4wt72by7uw4bgqwxdijgw2bel5sad.onion:50002] | disconnecting due to: SOCKSFailure('connection refused')
I/n | network | couldn't launch iface mic3bk5pvma4ng7zkc3kdjmr2vv4wt72by7uw4bgqwxdijgw2bel5sad.onion:50002:t -- CancelledError()

Then you may have to check your Bitcoin Core configuration to find the port that it is listening on for onion connections.

.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
odolvlobo
Legendary
*
Online Online

Activity: 4326
Merit: 3231



View Profile
March 24, 2021, 11:49:50 PM
 #6

I have a Raspibolt node running using TOR. Raspibolt has the following configuration for bitcoind. Compare to yours.

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
bind=127.0.0.1

# Connections
rpcuser=raspibolt
rpcpassword=PASSWORD_[B]
zmqpubrawblock=tcp://127.0.0.1:28332
zmqpubrawtx=tcp://127.0.0.1:28333

# Raspberry Pi optimizations
maxconnections=40
maxuploadtarget=5000

# Initial block download optimizations
dbcache=2000
blocksonly=1

Also, why run both Bitcoin Core and Electrum on the RPi? I run Electrs on the RPi, which allows me to run electrum on any computer on my network.

Join an anti-signature campaign: Click ignore on the members of signature campaigns.
PGP Fingerprint: 6B6BC26599EC24EF7E29A405EAF050539D0B2925 Signing address: 13GAVJo8YaAuenj6keiEykwxWUZ7jMoSLt
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!