-
Notifications
You must be signed in to change notification settings - Fork 913
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
v24.11rc4: Calling connect
fails with Unable to connect, no address known for peer
#7913
Comments
connect
fails with Unable to connect, no address known for peer
connect
fails with Unable to connect, no address known for peer
I can fix my integration tests by omitting the |
OK, this is fascinating. Here's what's happening:
Of course, l1 knows how to connect to l2, and eventually it does. You can simply ask l1 to connect to l2 not vice-versa and it will work. But I shall queue a few fixes for this case next release. |
I think this might be preventing channels from being opened? The connection at some point drops, then when manually trying to reconnect with Here is a log snippet of this happening:
This is a brand new signet channel with an LND v0.18.3-beta node and seems stuck at
|
Issue and Steps to Reproduce
connect
to l1 with explicit host and portConnect fails with
Unable to connect, no address known for peer
, while the connection details were in the request.getinfo
outputv24.11rc4
The text was updated successfully, but these errors were encountered: