Core Lightning Node open channel stuck at 9 peers

I try to open a channel with you Paul but my CLN still stuck on pending with 9peers confirmed. I can’t find my funded transaction in mempool.
What can I do to unstuck on pending status?

The number of peers listed is a red herring.

Check if the transaction has been broadcasted to the network, and if so has it been mined yet. Open the channel detals, and copy the value from “Funding ID”. Paste that into Mempool to look up the transaction.

Hi Paul,
I did check with the mempool but there is no transaction found in the pool.

Do you get the same if you check with the Mempool service (as opposed to mempool.space)?

Hi Paul,
I’m not sure how to access the Mempool service. I only did check the mempool.space.

What operating system are you running Core Lightning on?

0.3.5-1 StartOS is the operation system

I already created SSH follow your video tutorial.

You can install the Mempool service via the Start9 registry (same place you installed Core Lightning from).

Ok, I hope the configuration is correct.

@oldguy reported a similar problem recently on this thread here. Basically, the transaction to open the channel was never sent to your Knots node (or it got filtered out). This appears to be a bug with Core Lightning. Unfortunately, I’m not sure you’ll be able to regain the sats you have locked up in those channels (perhaps oldguy can confrim whether or not he was able to get the sats back in his case).

My recommendation at this point (since the problem has happend to multiple forum members now) is to not open channels from Core Lightning. Instead, create a LND node, and open a chanel back from your LND node back to your Core Lightning node (via the Ride the Lightning service). If that succeeds, then open a channel from your LND node out to the larger network, and send sats out from it to open inbound liquidity. This will create a path for your mining rewards to flow from Ocean, into your LND node, and from there into your Core Lightning node (without needing to open any channels from Core Lightning which might experience the bug)