how to connect over tor

+2 votes

Just tried connecting over tor this way

multichaind chain1@someaddress.onion:6283

and it seems not to work, it says:

Retrieving blockchain parameters from the seed node someaddress.onion:6283 ...
Error: Couldn't connect to the seed node someaddress.onion on port 6283 - please check multichaind is running at that address and that your firewall settings allow incoming connections.

even tried this

multichaind chain1 -onion=someaddress.onion:6283

whith no look sad.  Any advice whould be very good laugh

asked May 20, 2017 by rayn
I'm looking for something similar, did you ever get this to work?
yes, i worked it out. Im sorry for not posting it here but i think im not understanding where is the bug. Well let it be simple to work around; The steps you follow in my answer below are fine, exept for the first point on the second server  "multichain-util create chainx" , replace this steep by coping the one generateted by the "first server". Well that looks to work very good.
Hopes it helps. Whem more efficient ill get back.

1 Answer

0 votes
We've never tried this, but MultiChain should work similarly to Bitcoin Core over the Tor network. Please consult this page to get started: https://en.bitcoin.it/wiki/Tor
answered May 22, 2017 by MultiChain
Thank for replying, very appretiate
Well everything i try seems to send the same messages:

net: Trying to connect to xxx.onion (by address)
net: trying connection xxx.onion lastseen=0.0hrs
Cannot connect to xxx.onion:8571: unsupported network
net: Connection not established

This is a list of attemps:

multichaind chain1@xxx.onion:6283 -proxy=127.0.0.1:9050 -debug -printtoconsole
multichaind chain1@xxx.onion:6283 -debug -printtoconsole
torsocks multichaind chain1@xxx.onion:6283 -debug -printtoconsole
multichaind chain1@xxx.onion:6283 -onion=127.0.0.1:9050 -addnode=xxx.onion -debug -printtoconsole
multichaind chain1@xxx.onion:6283 -onion=127.0.0.1:9050 -addnode=xxx.onion -debug -printtoconsole -onlynet=onion
multichaind chain1@xxx.onion:6283 -onion=127.0.0.1:9050 -debug -printtoconsole -onlynet=onion -discover
multichaind chain1 -externalip=xxx.onion:6283 -onion=127.0.0.1:9050 -debug -printtoconsole -onlynet=onion -discover
multichaind chain1@xxx.onion:6283 -externalip=xxx.onion -onion=127.0.0.1:9050 -debug -printtoconsole -onlynet=onion -discover
multichaind -externalip=xxx.onion -onion=127.0.0.1:9050 -debug -printtoconsole -listen
multichaind chain1 -externalip=xxx.onion -onion=127.0.0.1:9050 -debug -printtoconsole -listen
multichaind chain1@xxx.onion:6283 -externalip=xxx.onion -onion=127.0.0.1:9050 -debug -printtoconsole -onlynet=onion -listen

The only one that connected, but locally:

multichaind chain1@192.168.11.2:6283

Any suggestions on how to work around whould be very good. Thanks :)
Did you try working through these instructions: https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md
Hello and thanks. Following the instructions on that address. There they say this:

- In a typical situation, where you're only reachable via Tor, this should suffice:
- ./bitcoind -proxy=127.0.0.1:9050 -externalip=57qr3yd1nyntf5k.onion -listen

So i translate it to this (if im wrong let me know pliss)

multichaind chain5 -proxy=127.0.0.1:9050 -externalip=xxx.onion -listen

Then in the second server. They say:

- In a typical situation, this suffices to run behind a Tor proxy:
- ./bitcoin -proxy=127.0.0.1:9050

So i translate it to this (again if im wrong let me know pliss):

multichaind chain5@xxx.onion:5283 -proxy=127.0.0.1:9050

With output: "Error: Couldn't connect to the seed node xxx.onion on port 5283 - please check multichaind is running at that address and that your firewall settings allow incoming connections."

The hidden service is up and running ok. I tested it by allowing connections bia ssh (on port 22) and connecting successfully to it. This are the lines on the torrc file:

HiddenServiceDir /var/lib/tor/xxx/
HiddenServicePort 22 127.0.0.1:22
HiddenServicePort 5283 127.0.0.1:5283
HiddenServicePort 5282 127.0.0.1:5282

If there is more info to be needed letme know. Also i can share the onion address for testing purposes. Thanks a lot my friends :).

PD I was looking for an IRC channel and seems not to be such (correcte please).
I'm afraid this question is a little outside our scope, so I'm not sure we'll be able to solve it for you. But one guess is that you may need to use this on the second server if multichaind on the first server is effectively listening on port 9050.

multichaind chain5@xxx.onion:9050 -proxy=127.0.0.1:9050

Try using telnet on the second server to discover which ports are open on the first server.
it seems that in the second server we have to first of all create the chain
Steps Server 1:
multichain-util create chainx
multichaind chainx -proxy=127.0.0.1:9050 -externalip=xxx.onion -listen -port=<port> -rpcport=<rpcport>

Steps Server 2:
multichain-util create chainx
multichaind chainx@xxx.onion:<port> -proxy=127.0.0.1:9050

Well this is how far i tested it, will come to an answer when more mature. Thx
...