mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-11-19 09:54:16 +01:00
Code Issues Projects Releases Wiki Activity

Update TOR.md

Browse Source 
My testing shows that I received errors which turned out to be fatal ("/usr/libexec/c-lightning/lightning_connectd: libbacktrace: no debug info in ELF executable") when I had two `bind-addr=...` settings in my config file, which the instructions insinuated since c-lightning would already have been installed and runnable (therefore, already having a bind-addr).
This commit is contained in:
Dave Scotese 2020-08-11 18:10:23 -07:00 committed by Christian Decker
parent f81611e551
commit d2bd1f0fa9
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/TOR.md
View File

@ -69,7 +69,7 @@ Uncomment those in, then restart `tor` (usually `systemctl restart tor` or
Debian and Ubuntu, or just restart the entire computer if you cannot figure
it out).
Then add these to your `${LIGHTNING_DIR}/config` or other C-Lightning configuration
Then make sure these are in your `${LIGHTNING_DIR}/config` or other C-Lightning configuration
(or prepend `--` to each of them and add them to your `lightningd` invocation
command line):
@ -86,7 +86,9 @@ always-use-proxy=true
for a `SocksPort` entry to confirm the port number.
2. `bind-addr` informs C-Lightning to bind itself to port 9735.
This is needed for the subsequent `statictor` to work.
9735 is the normal Lightning Network port.
9735 is the normal Lightning Network port, so this setting may already be present.
If you add a second `bind-addr=...` you may get errors, so choose this new one
or keep the old one, but don't keep both.
This has to appear before any `statictor:` setting.
3. `addr=statictor:` informs C-Lightning that you want to create a persistent
hidden service that is based on your node private key.