Did you open or close a Lightning channel for 1 sat/vbyte? Most people do unless opening the channel is a priority. Well, the current state of the Bitcoin mempool is putting a hindrance on these transactions. They're getting pruned or removed from the mempool.
I was worried that a recent Lighning channel close that was set at 1 sat/vbyte would get pruned. And it did. Thankfully, with a little command line help, you can bump the fee on that transaction and get those funds swept into your on-chain wallet in a timely manner.
https://void.cat/d/DvkrzgRdhR9XGDYybY5Qjg.webp
I ssh'ed into my node and viewed the pending LND transactions that were waiting to be swept into my wallet. Then, I ran a command to bump the fees to 12 sats/vbyte.
```
lncli wallet pendingsweeps
lncli wallet bumpfee --sat_per_vbyte 12 tx-id-goes-here:0
```
It's really simple. It's just something that I had never done before. I hope this helps if you're ever in this situation.
I just had someone DM me, asking me how they could fix a Lightning channel that's stuck opening or closing on their Umbrel node due to the current high fees on the Bitcoin mempool. I figured it was a good time to reshare this quick and dirty guide I wrote a month ago. Good luck!
#[0]
Very good to know!
