My LN node's IP has changed but the IP that shows up when selecting my node in the #recksplorer is the old one. This also of course impacts the invoice generation feature.
I'm using clightning's (v0.6) --bind-addr argument for my lan ip (using 0.0.0.0) and --announce-addr with my new public IP but perhaps the recksplorer is not "listening" for that information and instead caching the original IP.
I imagine this could be a relatively common occurrence based on folks hosting Bitcoin nodes at home and subject to public IP changes after outages or in some cases just periodically, so it seems relatively important.
I'll look through the code myself to see what I can figure out, but someone more familiar might make short work of it. :)
My LN node's IP has changed but the IP that shows up when selecting my node in the #recksplorer is the old one. This also of course impacts the invoice generation feature.
I'm using clightning's (v0.6) --bind-addr argument for my lan ip (using 0.0.0.0) and --announce-addr with my new public IP but perhaps the recksplorer is not "listening" for that information and instead caching the original IP.
I imagine this could be a relatively common occurrence based on folks hosting Bitcoin nodes at home and subject to public IP changes after outages or in some cases just periodically, so it seems relatively important.
I'll look through the code myself to see what I can figure out, but someone more familiar might make short work of it. :)
Thanks and great tool!