LND stuck in "Cert is not yet signed for current IP" loop after recovery + IP change

StartOS Support
1

Hi everyone,

After a power loss and USB recovery on my Server One 2026, LND is stuck in an infinite loop printing “Cert is not yet signed for current IP…” every second. All other packages (Bitcoin Knots, Fulcrum, Mempool) work fine.

The node’s IP changed from 192.168.1.200 to 192.168.1.82 during recovery. StartOS knows the correct IP everywhere (ip addr, nmcli, embassy.db), but startd’s internal port forwarding between LXC containers and the bridge network appears broken — Tor’s SOCKS proxy runs inside its container on 9050 but is unreachable at 10.0.3.1:9050 from other packages.

I’ve tried: deleting certs, server rebuild, server restart, package rebuild, upgrading from alpha.21 to beta.0, and manual cert generation via start-cli. Nothing fixes the loop.

Full diagnostic and technical details in the GitHub issue: LND stuck in cert loop after recovery + IP change — startd port forwarding broken (0.4.0-beta.0) · Issue #3154 · Start9Labs/start-os · GitHub

Also emailed dev@start9.com. Wallet data is untouched and safe.

Has anyone hit this after an IP change? Any guidance appreciated.

StartOS 0.4.0-beta.0 | Server One 2026 | LND 0.20.1-beta

2

Thank you, we’re looking into it.

3

Any fix? I’m having the same issue and looking for a fix before all of my lightning channels force close.

Edit: My issue is resolved. I redownloaded and trusted the Root CA, restarted start9 server.

4

Something will make it into a future release to prevent or warn of the situation.