Prevent LND from rotating TLS cert every startup #318
Merged
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
This PR adds a setting to not include the container hostname (its Docker container ID) in the certificate. Thus, lnd won't detect changes at each restart and won't create a new certificate, which was leading to invalid connection on Lightning wallets like Zap after a restart.
lukechilds
approved these changes
Nov 20, 2020
lukechilds
changed the title
|
Great stuff, thanks @louneskmt! |
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.
This PR adds a setting to not include the container hostname (its Docker container ID) in the certificate. Thus, lnd won't detect changes at each restart and won't create a new certificate, which was leading to invalid connection on Lightning wallets like Zap after a restart.