From d2bd1f0fa92823ad37e4e4483b01aedcea139f41 Mon Sep 17 00:00:00 2001 From: Dave Scotese Date: Tue, 11 Aug 2020 18:10:23 -0700 Subject: [PATCH] Update TOR.md 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). --- doc/TOR.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/TOR.md b/doc/TOR.md index 424e67b31..5b168fbfa 100644 --- a/doc/TOR.md +++ b/doc/TOR.md @@ -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.