diff options
| author | Jon Atack <jon@atack.com> | 2020-10-15 12:35:36 +0200 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-12-17 12:29:22 +0100 |
| commit | 2c8482d0a279d07a814eaaae231c90d3d2058e55 (patch) | |
| tree | 4464e3b19b8223ded37d82ef39df91c7ee359a5d /doc | |
| parent | 0c1fa78af1c413c848359df76f4d55f819b9fad5 (diff) | |
doc: add tor.md section on how to get tor info via bitcoind
Github-Pull: #19961
Rebased-From: dc8a591222f249da81c7eef8aa5961f8d7dd1e23
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/tor.md | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/tor.md b/doc/tor.md index 8fe87bdde6..ccf8a226ee 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -5,6 +5,16 @@ It is possible to run Bitcoin Core as a Tor onion service, and connect to such s The following directions assume you have a Tor proxy running on port 9050. Many distributions default to having a SOCKS proxy listening on port 9050, but others may not. In particular, the Tor Browser Bundle defaults to listening on port 9150. See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort) for how to properly configure Tor. +## How to see information about your Tor configuration via Bitcoin Core + +There are several ways to see your local onion address in Bitcoin Core: +- in the debug log (grep for "tor:" or "AddLocal") +- in the output of RPC `getnetworkinfo` in the "localaddresses" section +- in the output of the CLI `-netinfo` peer connections dashboard + +You may set the `-debug=tor` config logging option to have additional +information in the debug log about your Tor configuration. + ## 1. Run Bitcoin Core behind a Tor proxy |