Topic: Bitcoin core won't connect over Tor. (Read 185 times)
In Bitcoin Core, go to Help>Debug Window Change the tab to Console and type get network info, and hit enter. Make sure that “proxy” is 127.0. 0.1:9050 (or 9150 if you've changed it) and that “onion” is reachable. ... Once this is done, Bitcoin Core won't connect to anyone else unless Tor is running.
I changed the proxy to port 9050 and I have 13 connections (all out) and some are onion nodes.
maybe electrum will connect to my onion now...
maybe electrum will connect to my onion now...
OK I did getnetworkinfo and yielded basically this:
Also I have 10 connections but they are all out, no in connections if that is of any significance.
Code:
name onion
limited false
reachable true
proxy 127.0.0.1:9150
address myOnion.onion
port 8333
score: not zero, won't say because I do not know what it means
limited false
reachable true
proxy 127.0.0.1:9150
address myOnion.onion
port 8333
score: not zero, won't say because I do not know what it means
Also I have 10 connections but they are all out, no in connections if that is of any significance.
A non-zero score basically means things are able to connect to your hidden service.
I think I know the problem based on the fact that you have no incoming connections. It is because you have:
bind=127.0.0.1
So it is only listening on localhost (try to use bitcoin-cli from the same machine and it should work, but not from a machine over the network).
Try putting bind=0.0.0.0 to listen on all network interfaces including the one that's connected to the internet, or removing that line entirely to let Core figure out to do that itself.
Did you just added "onlynet=onion" on bitcoin.conf?
Can you post here the whole text from your Bitcoin.conf here
It seems it's not properly set up that is why the debug.log says connection refused.
Anyway, use these links and the video guide below to set up your node to run it over TOR service.
- Setting up a Tor hidden service
For two youtube video guides
- https://www.youtube.com/watch?v=57GW5Q2jdvw
- https://www.youtube.com/watch?v=n2IUYL7hCOI
Follow the steps carefully so that you can properly set up it with TOR service.
Can you post here the whole text from your Bitcoin.conf here
It seems it's not properly set up that is why the debug.log says connection refused.
Anyway, use these links and the video guide below to set up your node to run it over TOR service.
- Setting up a Tor hidden service
For two youtube video guides
- https://www.youtube.com/watch?v=57GW5Q2jdvw
- https://www.youtube.com/watch?v=n2IUYL7hCOI
Follow the steps carefully so that you can properly set up it with TOR service.
txindex=1
server=1
walletbroadcast=0
proxy=127.0.0.1:9150
listen=1
bind=127.0.0.1
addnode=abc....onion
Did you just added "onlynet=onion" on bitcoin.conf?
Can you post here the whole text from your Bitcoin.conf here
It seems it's not properly set up that is why the debug.log says connection refused.
Anyway, use these links and the video guide below to set up your node to run it over TOR service.
- Setting up a Tor hidden service
For two youtube video guides
- https://www.youtube.com/watch?v=57GW5Q2jdvw
- https://www.youtube.com/watch?v=n2IUYL7hCOI
Follow the steps carefully so that you can properly set up it with TOR service.
Can you post here the whole text from your Bitcoin.conf here
It seems it's not properly set up that is why the debug.log says connection refused.
Anyway, use these links and the video guide below to set up your node to run it over TOR service.
- Setting up a Tor hidden service
For two youtube video guides
- https://www.youtube.com/watch?v=57GW5Q2jdvw
- https://www.youtube.com/watch?v=n2IUYL7hCOI
Follow the steps carefully so that you can properly set up it with TOR service.
Do you by chance edit the respond you provided after using the getnetworkinfo cause status of your ipv4 and ipv6 connections ought to be included.
Follow the above description but if the problem continue that mean you will have to operate over Tor completely by starting it with this option:
Follow the above description but if the problem continue that mean you will have to operate over Tor completely by starting it with this option:
Code:
-onlynet=onion
Check here for more insight. yes I got an onion address in the debug
If you run getnetworkinfo from the console or bitcoin-cli and you see something like:
Code:
"networks": [
...
{"name": "onion",
"reachable": false,
...
}
]
...
{"name": "onion",
"reachable": false,
...
}
]
Then it means your Tor is misconfigured and you need to check that there is actually a Tor process listening on port 9050 or whichever port you configured bitcoin Core to use.
Alternatively if you see a score of zero in the "addresses" section of the output for your onion address then you might have put a custom onion address in the bitcoin.conf that is different from the hidden service that Tor created. Don't specify it in bitcoin.conf so that it finds the onion address automatically.
OK I did getnetworkinfo and yielded basically this:
Code:
name onion
limited false
reachable true
proxy 127.0.0.1:9150
address myOnion.onion
port 8333
score: not zero, won't say because I do not know what it means
limited false
reachable true
proxy 127.0.0.1:9150
address myOnion.onion
port 8333
score: not zero, won't say because I do not know what it means
Also I have 10 connections but they are all out, no in connections if that is of any significance.
yes I got an onion address in the debug
If you run getnetworkinfo from the console or bitcoin-cli and you see something like:
Code:
"networks": [
...
{"name": "onion",
"reachable": false,
...
}
]
...
{"name": "onion",
"reachable": false,
...
}
]
Then it means your Tor is misconfigured and you need to check that there is actually a Tor process listening on port 9050 or whichever port you configured bitcoin Core to use.
Alternatively if you see a score of zero in the "addresses" section of the output for your onion address then you might have put a custom onion address in the bitcoin.conf that is different from the hidden service that Tor created. Don't specify it in bitcoin.conf so that it finds the onion address automatically.
yes I got an onion address in the debug
Did you get an onion address in the debug.log? Did you configure Tor correctly? Can you add debug=Tor into the config file?
Try following the steps here: https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md#3-automatically-listen-on-tor
Try following the steps here: https://github.com/bitcoin/bitcoin/blob/master/doc/tor.md#3-automatically-listen-on-tor
I am trying to connect to my full node over tor using my hidden service but it will not connect.
If I put
If I put
Code:
onlynet=onion
in the bitcoin.conf, then I get 0 peers. If I add onion seednodes, then in the debug.log it says connection refused (111). Jump to: