-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
reverse proxy causes invalid commit sig w/ CL #3586
Comments
I have open the same issue in c-lightning github, as I don't know who is the culprit here: ElementsProject/lightning#3140 |
What does your |
It doesn't appear there, as it was inmediatly closed as I said in the first msg. But in closed channels it appears:
|
My guess is that this is just a feature bit disagreement, where one thinks it’s doing safu commitments and the other doesn’t. Was the channel opened before upgrading to rc2 or after? |
I think I found the trigger for this bug: I am behind a reverse SSH proxy for incoming connections, and I used
This is the autossh command in case you want to reproduce this error:
If I change the address from |
Will likely be fixed by #3872 |
Closing per #3586 (comment) |
Background
I have two nodes, a LND one and a C-Lightning one. I try to open a channel from C-Lightning to LND, and I get the following error right after the 3 confirmations:
I can provide any additional information you ask.
My environment
The text was updated successfully, but these errors were encountered: