Update LND.conf for using tor #29
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When following this guide I ran into a small misconfiguration when setting up a node with tor.
title: Tor guideline update
description: Fix small issue with lnd.conf for tor usage
type: Edit
category:
Description
Thank you for providing the proper flags for running LND with tor using lnd.conf, instead of just command line flags. However I noticed that listen=true was placed in the Tor section. When running in this configuration lnd doesn't start up, that flag belongs in the application options section. While doing this research, I also found nat=false to be useful when using tor, so I also included it here.
Checklist
Affected core subsystem(s)
Testing
Proof Read
Refers/Fixes