Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LND shuts down if tor.skip-proxy-for-clearnet-targets is enabled #6005

Closed
deafboy opened this issue Nov 19, 2021 · 3 comments
Closed

LND shuts down if tor.skip-proxy-for-clearnet-targets is enabled #6005

deafboy opened this issue Nov 19, 2021 · 3 comments

Comments

@deafboy
Copy link

deafboy commented Nov 19, 2021

Background

When option tor.skip-proxy-for-clearnet-targets is set to true, LND shuts down after wallet is unocked.

Your environment

  • v0.14.0
  • Ubuntu 18.04
  • btcd 1.3.0

Steps to reproduce

set tor.skip-proxy-for-clearnet-targets=true
start LND
unlock wallet

tor related conf:

[tor]
tor.active=true
tor.socks=9050
#tor.dns=nodes.lightning.directory
tor.streamisolation=true
tor.control=localhost:9051
tor.v3=true
tor.skip-proxy-for-clearnet-targets=true
#tor.directconnections=true
#tor.dns=nodes.lightning.directory

Actual behaviour

[bitcoin@lnd ~]$ lncli unlock && tail -f .lnd/logs/bitcoin/mainnet/lnd.log
Input wallet password: 

lnd successfully unlocked!
2021-11-19 11:50:06.105 [INF] CHDB: Not compacting database file at /home/bitcoin/.lnd/data/graph/mainnet/channel.db, it was last compacted at 2021-11-15 12:40:07.65350925 +0100 CET (95h9m58s ago), min age is set to 168h0m0s
2021-11-19 11:50:06.574 [INF] CHDB: Not compacting database file at /home/bitcoin/.lnd/data/chain/bitcoin/mainnet/macaroons.db, it was last compacted at 2021-11-19 11:47:08.522229478 +0100 CET (2m58s ago), min age is set to 168h0m0s
2021-11-19 11:50:06.574 [INF] CHDB: Not compacting database file at /home/bitcoin/.lnd/data/graph/mainnet/sphinxreplay.db, it was last compacted at 2021-11-15 12:40:35.594800489 +0100 CET (95h9m30s ago), min age is set to 168h0m0s
2021-11-19 11:50:06.633 [INF] LTND: Creating local graph and channel state DB instances
2021-11-19 11:50:09.255 [INF] CHDB: Checking for schema update: latest_version=24, db_version=24
2021-11-19 11:50:09.255 [INF] LTND: Database(s) now open (time_to_open=3.150344391s)!
2021-11-19 11:50:09.256 [INF] LTND: We're not running within systemd
2021-11-19 11:50:09.256 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create a wallet, `lncli unlock` to unlock an existing wallet, or `lncli changepassword` to change the password of an existing wallet and unlock it.
2021-11-19 11:50:24.309 [INF] LNWL: Opened wallet
2021-11-19 11:50:24.401 [INF] CHRE: Primary chain is set to: bitcoin
2021-11-19 11:50:24.414 [INF] CHRE: Initializing btcd backed fee estimator
2021-11-19 11:50:25.223 [INF] LNWL: The wallet has been unlocked without a time limit
2021-11-19 11:50:25.242 [INF] CHRE: LightningWallet opened
2021-11-19 11:50:25.255 [INF] LTND: Shutdown complete

^C
[bitcoin@lnd ~]$
@guggero
Copy link
Collaborator

guggero commented Nov 19, 2021

I think the actual error is being swallowed here. Not sure if the tor.skip-proxy-for-clearnet-targets=true setting really is the culprit. Do you have the stdout of lnd somewhere? Perhaps systemd? There the actual error should be logged (hopefully).

@deafboy
Copy link
Author

deafboy commented Nov 19, 2021

You're right.

2021-11-19 12:49:06.067 [INF] CHRE: LightningWallet opened
2021-11-19 12:49:06.094 [INF] LTND: Shutdown complete

while stream isolation is enabled, the TOR proxy may not be skipped

@guggero
Copy link
Collaborator

guggero commented Nov 19, 2021

Right, that makes sense that stream isolation (=no traffic correlation, even when encrypted) and skip proxy for clearnet (=send everything you can over clearnet) don't go together, as they're on complete opposites of the privacy concern spectrum.

Closing as this is a configuration issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants