btcserver issue after patch

[robert-lgtm]

Hi — running BTCPay Server (self-hosted, Docker, updated to 2.4.2) with bundled LND v0.21.1-beta.
Following the Aug 7 critical vulnerability advisory, I attempted to rotate my LND macaroons
by stopping the container and renaming admin.macaroon / macaroons.db, then restarting.
LND has been stuck in WAITING_TO_START ever since, even after restoring the original
macaroon files from backup.

Details:

• LND container restarts cleanly, opens bitcoind connection and Tor hidden service fine
• Logs show it reaches "Opening the main database, this might take a few minutes..."
  then nothing further — no errors, no progress
• channel.db is ~6.3GB
• docker stats shows ~0.7% CPU, near-idle — doesn't look like an active recovery/compaction
• No lock files found, no other process holding the file (lsof shows only the lnd process itself)
• bitcoind: fully synced, peers connected, healthy
• Tor: bootstrapped 100%, some "resolve failed / No more HSDir available" warnings but
  hidden service files exist and are pre-existing (2021)
• Disk space: 14GB free, not an issue

Separately, I noticed a directory at /root/x/ containing old (2021/2022) LND credentials
not part of the current Docker volume structure, and a file at
/data/.macaroon-rotated-lnd-security-2026-08-v1 (0 bytes) timestamped Aug 7 23:28 UTC —
same timestamp as a regenerated tls.cert/tls.key. I did not create this file. Not sure if
this is from BTCPay's own patch/update tooling or something else — flagging in case it's
relevant given the current exploit activity.

Node has been isolated (firewall closed to public, nginx stopped) since discovering this,
so no active exposure currently — just need help getting LND to boot again. Happy to share
full logs on request.

[robert-lgtm]

Thank you, the bbolt open just needed more time