#asknostr

#nodestrich

nostr:npub1hxfkcs9gvtm49702rmwn2aeuvhkd2w6f0svm4sl84g8glhzx5u9srk5p6t nostr:npub1aeh2zw4elewy5682lxc6xnlqzjnxksq303gwu2npfaxd49vmde6qcq4nwx

I need some help please.

I shut down my node to replace fan, restarted node and bitcoin node is synchronised and is seeing all new blocks but I can not connect to my lightning node. It just hangs. I have tried a few restarts and powered all way off again still no go.

Using a pi running umbrel

Reply to this note

Please Login to reply.

Discussion

Are you able to ssh to it and run lncli getinfo ?

As described here: https://community.umbrel.com/t/official-umbrel-troubleshooting-guide-and-faq/9873

I got it sorted thanks

How long did you wait after restarting for the Lightning node to come back online? Was there a progress bar on the screen?

I got it sorted thanks

Happened to me a few months ago - ended up resending whole blockchain and lightening restarted long enough to get most funds back but then reverted to hanging before opening. How did you get it sorted?

Interested to hear how this was resolved too.

Made no changes as such. Restarted whole node in cli instead of umbrel gui then rebooted just lnd in cli. It worked for a while then crashed. Restarted again in cli which didn’t bring it back up then restarted in gui and it started. It’s been up for 6 hrs now so holding my breathe.

The thing is every time I restarted Bitcoin core started ok but lnd took like 30 minutes. There is obviously an issue somewhere. I am now gun shy as a Kennedy to reboot or power off my node

For me, LND always takes around 30 minutes to become active after restarting.

Ok good to know.

lnd starts slow the more channels you have. 30mins seems to be normal with a pi

Ok good to know. I have a shed load of channels now and had added a lot since my last restart a few months back so I thought something was wrong.

yeah. seems all good…

Do the logs show any errors? You should be able to get the lightning logs from the CLI with:

~/umbrel/scripts/app compose lightning logs --tail 250

I got it sorted thanks