No funds after restoring with seed.

[jetlagv1]

Closed issue #205 was mine.
I didn't have time for a while but got around to restoring the raspiblitz with the use of the seed and password. It is running again but the funds are not showing. Not just the funds locked in channels but also the funds in the wallet. Everything shows 0 balance. Most of the funds where on chain and not in channels so how do I get acces to the wallet balance again? I also have a backup of the bitcoin and lnd folder from the original install if that is of any use.

[rootzoll]

@jetlagv1 please check out the LND Slack for that question: https://lightningcommunity.slack.com .. on-chain funds should get recovered when you restore by seed. If they dont that is an LND error I cannot give deeper support on.

About restoring old bitcoin/lnd folders on the raspiblitz .. that could be an action of last resort. Its risky, because if you have an "old state" in the lnd backup, the channel counterparty could see this as you trying to cheat and claim the whole channel fundings. But for on-chains funds that should be of no risk to try. Please report your experience if you do.

[jetlagv1]

The risk of the old channel state is indeed limited because most of the balance was not in channels. And this is also the balance I would like to restore most. I'll go over to slack....

[jetlagv1]

I cannot get into that channel. I don't have an account in that workspace

[rootzoll]

@jetlagv1 follow the SLACK invite link on this page to register: https://dev.lightning.community
please report back on your findings or if you try to restore bitcoin/lnd backups - this is a topic of interest. thx.

[jetlagv1]

admin@DMN737:~ $ sudo journalctl -u lnd -b --no-pager -n20
-- Logs begin at Thu 2019-01-17 13:01:13 GMT, end at Thu 2019-01-17 14:04:52 GMT. --
Jan 17 14:04:44 DMN737 lnd[3030]: 2019-01-17 14:04:44.415 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=605925465006342144, flag=259, update_time=2019-01-17 14:03:38 +0000 GMT) from 23.237.77.11:57343
Jan 17 14:04:44 DMN737 lnd[3030]: 2019-01-17 14:04:44.415 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=613134962741936129, flag=0, update_time=2019-01-17 14:04:28 +0000 GMT) from 23.237.77.11:57343
Jan 17 14:04:44 DMN737 lnd[3030]: 2019-01-17 14:04:44.418 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=603584604680224769, flag=1, update_time=2019-01-17 14:03:52 +0000 GMT) from 23.237.77.11:57343
Jan 17 14:04:49 DMN737 lnd[3030]: 2019-01-17 14:04:49.033 [DBG] PEER: Received Ping from 213.174.156.70:9735
Jan 17 14:04:49 DMN737 lnd[3030]: 2019-01-17 14:04:49.033 [DBG] PEER: Sending Pong to 213.174.156.70:9735
Jan 17 14:04:49 DMN737 lnd[3030]: 2019-01-17 14:04:49.036 [DBG] PEER: Sending Ping to 213.174.156.70:9735
Jan 17 14:04:49 DMN737 lnd[3030]: 2019-01-17 14:04:49.164 [DBG] PEER: Received Pong from 213.174.156.70:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.286 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=606510405197496320, flag=257, update_time=2019-01-17 14:03:48 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.317 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=600664301885915136, flag=257, update_time=2019-01-17 14:03:44 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.321 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=614473068400803840, flag=256, update_time=2019-01-17 14:03:45 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.326 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=606513703695876096, flag=257, update_time=2019-01-17 14:03:48 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.326 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=606510405197496320, flag=256, update_time=2019-01-17 14:03:48 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.438 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=613134962741936129, flag=0, update_time=2019-01-17 14:04:28 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.438 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=611426321775329281, flag=257, update_time=2019-01-17 14:03:47 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.439 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=606513703695876096, flag=256, update_time=2019-01-17 14:03:48 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.439 [DBG] PEER: Received ChannelUpdate(chain_hash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f, short_chan_id=614463172726358016, flag=256, update_time=2019-01-17 14:03:45 +0000 GMT) from 98.215.0.206:9735
Jan 17 14:04:51 DMN737 lnd[3030]: 2019-01-17 14:04:51.440 [DBG] DISC: Got ChannelUpdate for edge not found in graph(shortChanID=611426321775329281), saving for reprocessing later
Jan 17 14:04:52 DMN737 lnd[3030]: 2019-01-17 14:04:52.197 [ERR] CMGR: Can't accept connection: unable to accept connection from 94.209.71.14:53002: EOF
Jan 17 14:04:52 DMN737 lnd[3030]: 2019-01-17 14:04:52.370 [DBG] RPCS: [walletbalance] Total balance=0 BTC
Jan 17 14:04:52 DMN737 lnd[3030]: 2019-01-17 14:04:52.457 [DBG] RPCS: [walletbalance] Total balance=0 BTC
admin@DMN737:~ $

[jetlagv1]

Can you see something fishy here?

[vhmanu]

im having the same issue. After a new setup the onchain funds are gone (LND wallet was restored with the right seed)

[OfficialBigAl]

I had the same issue - Luckily was able to get backups from HDD of .Bitcoin and .LND folders and once the rebuild was completed (took 2 attempts) - Restored the .LND folder back, waited 24hrs to sync and funds started to appear in both off & on-chain wallets.

LND restarting was problematic, I think due to some differences in permissions. Started manually with Bitcoin account and it works. I feel like it's a house of cards though and could collapse at anytime!!

I get RPC errors when trying to access channels & balance info or remove funds but I'm patient and will sort that I'm sure.

At least I can see funds are there... Phew!

[rootzoll]

@OfficialBigAl if you restore LND folder manually the macaroons/TLS are in mismatch with admin user. In the 1.0 release there will be a option to RESET those macaroons/TLS in the EXPORT menu point. And yes - using lightning at this point in time is still #reckless. One idea of the RaspiBlitz is to have a early home-run lightning node to find all the weakspots to get them fixed and let the LND developers know. So please report that you also were not able to recover your funds in the normal way over at the LND Dev Slack, so LND devs put priority to fix this: https://dev.lightning.community

[IvanThinking]

Same for me. My old v.96 raspiblitz blew up somehow so I started over. Channels have been closed. No opportunity to release funds with the raspiblitz, as it was all kinds of messed up, but since no open channels I figured no big deal. Started fresh, and used the recovery seed when asked... no funds present now.

[rootzoll]

Did anybody get a response on that from the LND Slack channel? They are doing a great job, but this is really something that needs to be improved and cannot be the status quo. https://dev.lightning.community

[rootzoll]

Posted to LND Slack with hope to get some more details on this issue.

[githorray]

lightningnetwork/lnd#900

[molxyz]

lncli unlock --recovery_window=250000 will surely help.

[mr-dakota]

Just to chip in here... I've had a similar issue and have used recovery window up to 5000 to no avail.
Only issues on LND github seem to point to that as a solution, but I'd be very surprised if any Blitz users have got through more addresses than the default recovery window covers.

Hopefully there is some attention in Slack soon, as although it's not large amount of satoshis for me, recovery is certainly an important issue!!