Channel with dynamic DNS goes offline forever after ip changes

[sezaru]

Hello,

I have a LND node at

02e157c1d59d64570c48fec441a57a9e50c4f15e1a701458d686d3cc426827cba9@thunderpay.webredirect.org:9735

And I use the Eclair-Wallet to create channels with it.

As you can see from the lightning channel address, I use a dynamic DNS since my ip is not static. But it seems that every time my ip changed the channel would go offline forever (my DNS was updated with the new ip so I could access the node from outside the wallet just normal).

Actually I could make it go back online if I scan the address again and create a new channel, right after that it seems the wallet would update to the new ip and the old channel would go online again.

[menzels]

same for me.
023a3311d6a1680b51ae7fe0d2298999ae1323db6aea9e13eed9a1ab46c8daf282@broemelbude.hopto.org:9735

this seems to be the same: #73

[meeDamian]

A temporary mitigation that worked for me was attempting to open a 2nd channel to the stuck node, providing a connstring with a correct new IP. You get an error that multiple channels aren't supported, but it un-stucks the original channel.

I have a 2nd node that works only over Tor v3, that I managed to open a channel to using Eclair+orbot in VPN mode, and which also went offline after some time, however the previously described hack did not work there :(. Although, I'm not fully sure if it's the same underlying issue.

edit: Ooops… That's definitely a dup of #73 and this issue should be closed 😬.