Dyndns lightning node appears offline in eclair (android)

[ghost]

My lighting node (LND) is behind a dyndns with changing IP addresses. I connected to the node by entering the dyndns hostname. After a day, as my IP address changed it only shows up as offline. Does the eclair wallet (android) only save IPs and tries to reconnect? It should resolve the dyndns hostname to the current IP.

[charltonh]

Also running a lightningd node on a dynamic IP. The eclair wallet needs to be able to find it again because I have a channel open with it, but it cannot. It remains "OFFLINE".

I've decided to open a digital ocean droplet with a static IP and reroute my traffic to it just so that I can have a static IP to run my lightning node on. However, this is definitely a bug/limitation with the eclair wallet that shouldn't be too difficult to fix I'd think. My channel is still offline though, not sure if I need to close it now or what.

[githorray]

lnd now also supports tor and advertises .onion uris.

Using eclair behind Orbot in VPN mode, eclair can create a channel with lnd using the .onion url and can send payments. However after restart, eclair will not connect back to lnd. If you attempt to open a second channel to the same lnd node, eclair seems to suddenly re-discover the new address information of the lnd node and the previously disconnected channel will reconnect until you restart eclair.

Perhaps the IP info is not refreshed for a node in eclair unless certain actions take place like a new channel connection?

[hsjoberg]

I have the same problem with dynamic IP addresses.
I don't know if the android wallet is downloading the whole network graph, but as my node is announcing the correct IP address to the network, it should be able to reconnect to the node using the correct IP address.

How is Eclair Wallet handling this?

[AbelLykens]

For me it helps to re-enter the .onion address in "update node IP". Bit annoying though ;).