Invalid commitment sig received from LND
See original GitHub issueIssue Description
Hi @alexbosworth, have you done anything special on yalls node 03e504
today? Both channels open to it have failed. Do you happen to have logs for channel 8c735210f593406af4146e3f7bbc7e118d3e839075dfe47f23c93e0344987ec3
? Thanks!
8c735210f593406af4146e3f7bbc7e118d3e839075dfe47f23c93e0344987ec3_lnd_invalidsig.log
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
reverse proxy causes invalid commit sig w/ CL #3586 - GitHub
I try to open a channel from C-Lightning to LND, and I get the following error right ... reverse proxy causes invalid commit...
Read more >lnwallet package - github.com/monasuite/lnd/lnwallet - Go Packages
type InitFundingReserveMsg; type InvalidCommitSigError ... returned in the case that we receive a valid commit secret within the ChannelReestablish message ...
Read more >These common title problems can snag your home closing
The American Land Title Association recently found that fraud and forgery issues between spouses have become more prevalent over the past several years...
Read more >A Guide to HMDA Reporting: Getting It Right! - FFIEC
Issues a written commitment that: (a) is for a home purchase loan; (b) is valid for a designated period of time and up...
Read more >Medicare Program: Payment Policies under the Physician Fee ...
We post all comments received before the close of the comment period on the ... We remain committed to the process of establishing...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The default logs in LND used to be much more verbose, I do plan to increase the log level in a future roll out
This is old and may have been fixed in more recent releases of
lnd
. Let’s close this and reopen a new issue if issue surfaces again.