Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Bug: LDK reconnecting peer after IP address is not persisted #1113

Open
rolznz opened this issue Feb 20, 2025 · 0 comments · May be fixed by #1150
Open

Bug: LDK reconnecting peer after IP address is not persisted #1113

rolznz opened this issue Feb 20, 2025 · 0 comments · May be fixed by #1150
Assignees
@rolznz
Milestone
v1.15.0

Comments

@rolznz
Copy link
Contributor

rolznz commented Feb 20, 2025 •
edited
Loading

One of my peers changed their IP address and I re-connected with the correct IP address. Each time I restart Alby Hub, it reverts to the old IP address.

From tnull:

You should be able to call disconnect and connect with the persist flag set

currently that’s required as we won’t repersist if we already have an entry for that peer. It shouldn’t have any side effects.

(Currently we do not try to disconnect first)
@rolznz rolznz added this to the v1.15.0 milestone Feb 20, 2025
@rolznz rolznz self-assigned this Mar 5, 2025
@rolznz rolznz linked a pull request Mar 5, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rolznz rolznz

Labels
None yet
Projects
None yet
Milestone
v1.15.0
Development

Successfully merging a pull request may close this issue.

fix: disconnect ldk peer before re-connecting getAlby/hub
1 participant
@rolznz