Ah, got it. Maturity on both pending channels FCs is a few thousand blocks ago, so your node should have swept the sats already.
Don’t remember 100%, but 90%ish likelihood is that your LND is upset that the anchors got stolen, and you need to remind it by republishing the closing tx:
Check out the following helptext:
lncli wallet publishtx -h
NAME:
lncli wallet publishtx - Attempts to publish the passed transaction to the network.
USAGE:
lncli wallet publishtx [command options] tx_hex
DESCRIPTION:
Publish a hex-encoded raw transaction to the on-chain network. The
wallet will continually attempt to re-broadcast the transaction on start up, until it
enters the chain. The label parameter is optional and limited to 500 characters. Note
that multi word labels must be contained in quotation marks ("").
OPTIONS:
--label value (optional) transaction label
So you need the raw tx of both closing transactions, and rebroadcast them:
This is the first closing tx, you can get the raw hex from mempool:
https://mempool.space/api/tx/162188c6c1550e15b31e54b7856ee389e070d67091d3c881bbd9c4503d1255eb/hex
And the second:
https://mempool.space/api/tx/cadd1ba641884044584827730e57b73eafe5aa6ed819cc3688b3c7a1233a9793/hex
If you can, open two terminals! One to keep an eye on the logs, like
sudo docker logs lightning_lnd_1 -f -n 200 | grep -E "ae2a57c6c4c895666610201274832641f4cb68683ede5ec0e367403a51d8f146:1|162188c6c1550e15b31e54b7856ee389e070d67091d3c881bbd9c4503d1255eb"
and a second one to rebroadcast. This way, you will immediately see what LND takes in from your command here. Copy the first raw hex and append it to the command above, like this:
lncli wallet publishtx 0200000000010146f1d8513a4067e3c05ede3e6868cbf441268374122010666695c8c4c6572aae01000000007e932280044a0100000000000022002032aab8cf5696999c9ae69e2bdf5fcb1a9b7e67aeabd0a035d69c09b6589f675d4a01000000000000220020823230974434a7a1235cdd825e5d2bc53f9d933d5341c232e8392698f818c2ccb14a0000000000002200200d2c38af2cb0fdb126e3c2ad3392c3aea0bd0340792a6a6b9cb3aae6b55edea063510700000000002200203bc9bd70c698e4b885a31546bab504fc219382a9582bf6dd99bc0343d874e31e0400473044022051bd5727bd9685fab99a8e35705508638b7ac89c1e45fb3c4171a5eb5e79a6dc022048982d7e21fa677c3df171d953039d7a189ad0ea05931aab34613c2bd250138201483045022100957db4c8eff5cd46d7a2468fab55755a11a17b74428411396d9e5c7bfbab145a02205933aea1b1872867b601366a2edff1888c41fe073064fd5b7947283cd8674f0e014752210258892f416b3b19ec4429c7d74fdcd0af8cc5482f324254a512c2336a7e4a95ae21032f90f633bffa754e760ee79c8f060420c9aaf8e510414c97fcfbaa5b5cc1bdb552ae6e5f5720
In your terminal 1 window, you should see LND republishing the tx, ideally the sweeper waking up because LND recognises that these TX belong to you. Copy the results, so you have them in case nothing happens after a few blocks, and please only then share the logfile parts here.
I assume it’ll work, so firing the second in Terminal 2
lncli wallet publishtx 02000000000101beaf45131f1d83ed51ddc26d6414001a674cf1cff2d32dcc4076073f2d2c50470100000000f758d980044a010000000000002200202412a8b1dac9972e500a1be0df8bcabae4aa2bbf971da7e6cde75e9650144d994a010000000000002200204819867d9ae9f72246e298a701277764988915b76e9d47d406f0d4473229f8851a680100000000002200208ad7c0eb3b2a1955435b28014715b6c1393e9146596380dae64596dba98d6d6ba632060000000000220020f2b006318a4a9535d9a2f51b7c681d042638924ffe9179d467d1bbb4f576c72404004830450221009b1d34687d1cb8ad961db7c5aaae8362bee46a2d702bb3e0d063c2291544d9f202206f7d41a198ddeefbf06d19c455472fde0938d3f195a94efbbdf9fd1d5ca3b9a20147304402203cab113d75afa349d9fb6636d106990aa67db8568e533d475f698f6682aac4da0220746aed8e948cdedf8a08b0172e0eb997eb70942f968f68532174bbca8db3a50b0147522102e12bd5756d0799d00f51ae02785eb76aea5f03af6876a7350869c2fcf99ff140210316ea105618a274952f12dec0bec6c754851fa89e85be6306f44a1dcdacd26c6152ae1eb50820
Lmk if this works
