On-chain and Lightning Wallets keep Synchronizing; Wallet not Created; Wallet not Found

Hello. Had to reinstall Umbrel all new hardware. I typed in the seed phrase and the Bitcoin Core is 100% synched, BUT the Bitcoin and Lightning Wallets keep synchronizing - there is no balance AND the addresses for both wallets are not showing up.

I ran the debug log and saw lots of lines about “wallet not found” and “wallet not created”. The full debug log is below. Please can anyone help? I’ve reviewed the Umbrel Troubleshooting Guide. As I’m a total newbie, I haven’t been able to figure out the fix.

I’ve seen lots of posts with the same issue, but haven’t seen a fix posted. Hopefully this post will show the way!

=====================
= Umbrel debug info =

Umbrel version

0.4.16

Flashed OS version

v0.4.0

Raspberry Pi Model

Revision : c03111
Serial : 100000009ae9773c
Model : Raspberry Pi 4 Model B Rev 1.1

Firmware

Aug 3 2021 18:14:56
Copyright © 2012 Broadcom
version 40787ee5905644f639a2a0f6e00ae12e517a2211 (clean) (release) (start)

Temperature

temp=48.2’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 3.8G 1.1G 87M 2.0M 2.6G 2.6G
Swap: 4.1G 246M 3.8G

total: 29.0%
bitcoin: 16.4%
system: 8.4%
electrs: 2.3%
lnd: 1.3%
tor: 0.6%

Memory monitor logs

2022-02-13 21:45:45 Warning memory usage at 91%
2022-02-13 21:46:45 Warning memory usage at 91%
2022-02-13 21:47:45 Warning memory usage at 91%
1990 ? S 2:20 bash ./scripts/memory-monitor
Memory monitor is already running
2022-03-08 23:47:42 Memory monitor running!
2022-03-12 22:12:08 Memory monitor running!
2022-03-20 19:03:50 Memory monitor running!
1036 ? S 0:04 bash ./scripts/memory-monitor
Memory monitor is already running

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 29G 2.9G 25G 11% /
/dev/sda1 3.6T 505G 3.0T 15% /home/umbrel/umbrel

Startup service logs

Mar 20 19:03:57 umbrel umbrel startup[1015]: Creating tor …
Mar 20 19:03:57 umbrel umbrel startup[1015]: Creating umbrel_tor_server_1 …
Mar 20 19:03:57 umbrel umbrel startup[1015]: Creating dashboard …
Mar 20 19:04:00 umbrel umbrel startup[1015]: Creating umbrel_tor_server_1 … done
Mar 20 19:04:01 umbrel umbrel startup[1015]: Creating electrs … done
Mar 20 19:04:01 umbrel umbrel startup[1015]: Creating dashboard … done
Mar 20 19:04:01 umbrel umbrel startup[1015]: Creating tor … done
Mar 20 19:04:01 umbrel umbrel startup[1015]: Creating manager …
Mar 20 19:04:06 umbrel umbrel startup[1015]: Creating manager … done
Mar 20 19:04:06 umbrel umbrel startup[1015]: Creating lnd …
Mar 20 19:04:06 umbrel umbrel startup[1015]: Creating nginx …
Mar 20 19:04:15 umbrel umbrel startup[1015]: Creating nginx … done
Mar 20 19:04:15 umbrel umbrel startup[1015]: Creating bitcoin …
Mar 20 19:04:16 umbrel umbrel startup[1015]: Creating lnd … done
Mar 20 19:04:20 umbrel umbrel startup[1015]: Creating bitcoin … done
Mar 20 19:04:20 umbrel umbrel startup[1015]: Creating middleware …
Mar 20 19:04:20 umbrel umbrel startup[1015]: Creating neutrino-switcher …
Mar 20 19:04:26 umbrel umbrel startup[1015]: Creating middleware … done
Mar 20 19:04:27 umbrel umbrel startup[1015]: Creating neutrino-switcher … done
Mar 20 19:04:27 umbrel umbrel startup[1015]: Removing status server iptables entry…
Mar 20 19:04:27 umbrel umbrel startup[1015]: Removed existing iptables entry.
Mar 20 19:04:27 umbrel umbrel startup[1015]: Starting installed apps…
Mar 20 19:04:27 umbrel umbrel startup[1015]: Umbrel is now accessible at
Mar 20 19:04:27 umbrel umbrel startup[1015]: http://umbrel.local
Mar 20 19:04:27 umbrel umbrel startup[1015]: http://192.168.1.64
Mar 20 19:04:27 umbrel systemd[1]: Started Umbrel Startup Service.
Mar 22 21:06:56 umbrel passwd[22553]: pam_unix(passwd:chauthtok): password changed for umbrel
Mar 23 16:24:24 umbrel passwd[4928]: pam_unix(passwd:chauthtok): password changed for umbrel
Mar 23 23:55:18 umbrel passwd[9688]: pam_unix(passwd:chauthtok): password changed for umbrel

External storage service logs

– Logs begin at Sun 2022-03-20 19:03:30 UTC, end at Thu 2022-03-24 00:17:01 UTC. –
Mar 20 19:03:34 umbrel systemd[1]: Starting External Storage Mounter…
Mar 20 19:03:34 umbrel external storage mounter[502]: Running external storage mount script…
Mar 20 19:03:35 umbrel external storage mounter[502]: Found device “WD My Passport 2627”
Mar 20 19:03:35 umbrel external storage mounter[502]: Blacklisting USB device IDs against UAS driver…
Mar 20 19:03:35 umbrel external storage mounter[502]: Rebinding USB drivers…
Mar 20 19:03:35 umbrel external storage mounter[502]: Checking USB devices are back…
Mar 20 19:03:35 umbrel external storage mounter[502]: Waiting for USB devices…
Mar 20 19:03:36 umbrel external storage mounter[502]: Waiting for USB devices…
Mar 20 19:03:37 umbrel external storage mounter[502]: Checking if the device is ext4…
Mar 20 19:03:37 umbrel external storage mounter[502]: Yes, it is ext4
Mar 20 19:03:37 umbrel external storage mounter[502]: Checking if device contains an Umbrel install…
Mar 20 19:03:37 umbrel external storage mounter[502]: Yes, it contains an Umbrel install
Mar 20 19:03:37 umbrel external storage mounter[502]: Bind mounting external storage over local Umbrel installation…
Mar 20 19:03:37 umbrel external storage mounter[502]: Bind mounting external storage over local Docker data dir…
Mar 20 19:03:37 umbrel external storage mounter[502]: Bind mounting external storage to /swap
Mar 20 19:03:37 umbrel external storage mounter[502]: Bind mounting SD card root at /sd-card…
Mar 20 19:03:37 umbrel external storage mounter[502]: Checking Umbrel root is now on external storage…
Mar 20 19:03:38 umbrel external storage mounter[502]: Checking /var/lib/docker is now on external storage…
Mar 20 19:03:38 umbrel external storage mounter[502]: Checking /swap is now on external storage…
Mar 20 19:03:38 umbrel external storage mounter[502]: Setting up swapfile
Mar 20 19:03:44 umbrel external storage mounter[502]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
Mar 20 19:03:44 umbrel external storage mounter[502]: no label, UUID=ab8efede-f690-4f1d-aeb0-f4e14050bc5b
Mar 20 19:03:44 umbrel external storage mounter[502]: Checking SD Card root is bind mounted at /sd-root…
Mar 20 19:03:44 umbrel external storage mounter[502]: Starting external drive mount monitor…
Mar 20 19:03:44 umbrel external storage mounter[502]: Mount script completed successfully!
Mar 20 19:03:44 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Sun 2022-03-20 19:03:30 UTC, end at Thu 2022-03-24 00:17:01 UTC. –
Mar 20 19:03:50 umbrel systemd[1]: Starting External Storage SDcard Updater…
Mar 20 19:03:50 umbrel external storage updater[934]: Checking if SD card Umbrel is newer than external storage…
Mar 20 19:03:50 umbrel external storage updater[934]: No, SD version is not newer, exiting.
Mar 20 19:03:50 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

=======================================

== End Update Script 02-run.sh ==

== Begin Update Script 03-run.sh ==

=======================================
=============== UPDATE ================

=========== Stage: Success ============

Removing backup
Successfully installed Umbrel v0.4.16
== End Update Script 03-run.sh ==

Deleting cloned repository
Removing lock
Got signal: backup
karen is getting triggered!
Deriving keys…
cat: /home/umbrel/umbrel/db/umbrel-seed/seed: No such file or directory
Missing derivation parameter, this is unsafe, exiting.
Got signal: backup
karen is getting triggered!
Deriving keys…
cat: /home/umbrel/umbrel/db/umbrel-seed/seed: No such file or directory
Missing derivation parameter, this is unsafe, exiting.
Got signal: backup
karen is getting triggered!
Deriving keys…
cat: /home/umbrel/umbrel/db/umbrel-seed/seed: No such file or directory
Missing derivation parameter, this is unsafe, exiting.
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: backup
karen is getting triggered!
Deriving keys…
cat: /home/umbrel/umbrel/db/umbrel-seed/seed: No such file or directory
Missing derivation parameter, this is unsafe, exiting.
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
middleware Up 27 hours
bitcoin Up 27 hours
lnd Up 27 hours
nginx Up 27 hours
manager Up 27 hours
dashboard Up 27 hours
tor Up 27 hours
umbrel_tor_server_1 Up 27 hours
electrs Up 27 hours

Umbrel logs

Attaching to middleware, manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:33 GMT] “GET /v1/system/get-update HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:35 GMT] “POST /v1/system/debug HTTP/1.0” 200 17 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:36 GMT] “GET /v1/system/debug-result HTTP/1.0” 200 23 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:37 GMT] “GET /v1/system/is-umbrel-os HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:37 GMT] “GET /v1/system/memory HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:37 GMT] “GET /v1/system/storage HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
middleware | umbrel-middleware
middleware | Unable to list on-chain transactions, wallet not created, create one to enable full RPC access
middleware | /v1/lnd/transaction
middleware | LndError: Unable to list on-chain transactions
middleware | at /app/services/lnd.js:69:18
middleware | at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1210:9)
middleware | at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:568:42)
middleware | at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:618:8)
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
middleware | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:37 GMT] “GET /v1/lnd/transaction HTTP/1.0” 500 96 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
middleware |
middleware | umbrel-middleware
middleware | (node:44) UnhandledPromiseRejectionWarning: LndError: Unable to list channels
middleware | at /app/services/lnd.js:69:18
middleware | at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1210:9)
middleware | at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:568:42)
middleware | at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:618:8)
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:37 GMT] “GET /v1/system/get-update HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:37 GMT] “GET /v1/system/temperature HTTP/1.0” 200 2 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:37 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:38 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
manager |
manager | umbrel-manager
middleware | (node:44) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 181)
middleware | Unable to get payments, wallet not created, create one to enable full RPC access
middleware | /v1/lnd/lightning/payments
middleware | LndError: Unable to get payments
middleware | at /app/services/lnd.js:69:18
middleware | at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1210:9)
middleware | at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:568:42)
middleware | at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:618:8)
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
middleware | ::ffff:10.21.21.2 - - [Thu, 24 Mar 2022 00:18:37 GMT] “GET /v1/lnd/lightning/payments HTTP/1.0” 500 82 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.74 Safari/537.36”
middleware |
middleware | umbrel-middleware

Bitcoin Core logs

Attaching to bitcoin
bitcoin | 2022-03-23T22:39:47Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
bitcoin | 2022-03-23T22:43:23Z New outbound peer connected: version: 70016, blocks=728714, peer=407 (block-relay-only)
bitcoin | 2022-03-23T22:44:06Z New outbound peer connected: version: 70016, blocks=728714, peer=408 (block-relay-only)
bitcoin | 2022-03-23T22:53:31Z UpdateTip: new best=0000000000000000000064adfa51617917bca11881f7e06ac371af8b224fa5a6 height=728715 version=0x2000e004 log2_work=93.419076 tx=719940821 date=‘2022-03-23T22:53:01Z’ progress=1.000000 cache=23.6MiB(125567txo)
bitcoin | 2022-03-23T22:58:51Z UpdateTip: new best=0000000000000000000168c8e927fc60b76405f217e5af3c965f0a811007b9f8 height=728716 version=0x31abc000 log2_work=93.419089 tx=719942983 date=‘2022-03-23T22:57:54Z’ progress=1.000000 cache=24.6MiB(134210txo)
bitcoin | 2022-03-23T23:01:53Z New outbound peer connected: version: 70016, blocks=728716, peer=409 (block-relay-only)
bitcoin | 2022-03-23T23:02:27Z New outbound peer connected: version: 70016, blocks=728716, peer=411 (outbound-full-relay)
bitcoin | 2022-03-23T23:05:48Z New outbound peer connected: version: 70016, blocks=728716, peer=413 (block-relay-only)
bitcoin | 2022-03-23T23:06:31Z UpdateTip: new best=00000000000000000003a6db487e6e3433a77d2a04a6f947c3cbe8181c7cdd05 height=728717 version=0x2c458000 log2_work=93.419102 tx=719946126 date=‘2022-03-23T23:05:54Z’ progress=1.000000 cache=25.8MiB(143771txo)
bitcoin | 2022-03-23T23:17:10Z New outbound peer connected: version: 70016, blocks=728717, peer=414 (outbound-full-relay)
bitcoin | 2022-03-23T23:17:59Z Socks5() connect to 91.193.4.205:8333 failed: connection refused
bitcoin | 2022-03-23T23:20:03Z Socks5() connect to 2409:4071:d86:d0c9:8d13:1cdb:5bd3:e7a8:8333 failed: general failure
bitcoin | 2022-03-23T23:23:44Z New outbound peer connected: version: 70016, blocks=728717, peer=416 (block-relay-only)
bitcoin | 2022-03-23T23:24:34Z Socks5() connect to 185.220.101.32:8333 failed: connection refused
bitcoin | 2022-03-23T23:27:11Z UpdateTip: new best=000000000000000000052382ef683117553af74f390d5078716194d03fadcb33 height=728718 version=0x20800004 log2_work=93.419114 tx=719948985 date=‘2022-03-23T23:26:54Z’ progress=1.000000 cache=27.4MiB(156763txo)
bitcoin | 2022-03-23T23:30:17Z UpdateTip: new best=000000000000000000013302b35e2d09ce23c85b4cfc9afe2a66846766771fba height=728719 version=0x20200004 log2_work=93.419127 tx=719950217 date=‘2022-03-23T23:27:10Z’ progress=0.999999 cache=28.5MiB(165543txo)
bitcoin | 2022-03-23T23:32:13Z New outbound peer connected: version: 70016, blocks=728719, peer=418 (block-relay-only)
bitcoin | 2022-03-23T23:38:01Z New outbound peer connected: version: 70016, blocks=728719, peer=420 (block-relay-only)
bitcoin | 2022-03-23T23:42:50Z UpdateTip: new best=000000000000000000053475f64d998b2d16445e740b45747965c4e635e94e36 height=728720 version=0x20000000 log2_work=93.419140 tx=719952670 date=‘2022-03-23T23:42:13Z’ progress=1.000000 cache=29.5MiB(174150txo)
bitcoin | 2022-03-23T23:44:06Z Socks5() connect to 185.220.102.7:8333 failed: connection refused
bitcoin | 2022-03-23T23:54:27Z UpdateTip: new best=00000000000000000003f7219641c414dc5121937b302c4f5d7f922e74a51292 height=728721 version=0x20000004 log2_work=93.419153 tx=719954785 date=‘2022-03-23T23:53:45Z’ progress=1.000000 cache=30.4MiB(181495txo)
bitcoin | 2022-03-23T23:54:54Z UpdateTip: new best=00000000000000000005ee98e684888ead90b015bad61d39ab6034306308bbe6 height=728722 version=0x20e00000 log2_work=93.419166 tx=719955524 date=‘2022-03-23T23:54:18Z’ progress=1.000000 cache=30.8MiB(184807txo)
bitcoin | 2022-03-24T00:01:43Z Socks5() connect to 104.220.83.58:8333 failed: general failure
bitcoin | 2022-03-24T00:15:35Z UpdateTip: new best=0000000000000000000898906c526cf98234104a8bd587b76a93f6245c63c006 height=728723 version=0x20200000 log2_work=93.419179 tx=719957649 date=‘2022-03-24T00:14:54Z’ progress=1.000000 cache=33.2MiB(203617txo)
bitcoin | 2022-03-24T00:15:48Z Socks5() connect to 2800:bf0:149:f4b:d3:20aa:1e51:c37e:8333 failed: general failure

LND logs

Attaching to lnd
lnd | 2022-03-24 00:18:09.957 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:09.974 [ERR] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet]: wallet not found
lnd | 2022-03-24 00:18:17.360 [ERR] RPCS: [/lnrpc.Lightning/ChannelBalance]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.367 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.368 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.368 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.391 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.415 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.415 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.431 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.433 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.478 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.493 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:17.517 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:19.994 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:20.056 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:20.073 [ERR] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet]: wallet not found
lnd | 2022-03-24 00:18:30.091 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:30.149 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:30.167 [ERR] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet]: wallet not found
lnd | 2022-03-24 00:18:37.255 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:37.358 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:37.358 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:37.361 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:37.361 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:37.363 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:37.424 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:40.188 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:40.261 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2022-03-24 00:18:40.279 [ERR] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet]: wallet not found

electrs logs

Attaching to electrs
electrs | [2022-03-23T22:20:38.826Z INFO electrs::index] indexing 1 blocks: [728709…728709]
electrs | [2022-03-23T22:20:38.969Z INFO electrs::chain] chain updated: tip=000000000000000000083e7c3255f314f184d7e6ba3c8ed99fbec95acfc940f8, height=728709
electrs | [2022-03-23T22:23:13.480Z INFO electrs::index] indexing 1 blocks: [728710…728710]
electrs | [2022-03-23T22:23:13.660Z INFO electrs::chain] chain updated: tip=00000000000000000008a34bf87b95ff79fd8cc3a64619c46d0e42eae32ab142, height=728710
electrs | [2022-03-23T22:30:18.708Z INFO electrs::index] indexing 1 blocks: [728711…728711]
electrs | [2022-03-23T22:30:18.856Z INFO electrs::chain] chain updated: tip=00000000000000000007620d770a4d8b25bb709a587a11654d14f5fc33ca419c, height=728711
electrs | [2022-03-23T22:30:51.678Z INFO electrs::index] indexing 1 blocks: [728712…728712]
electrs | [2022-03-23T22:30:51.881Z INFO electrs::chain] chain updated: tip=000000000000000000083d966fe7817e40eec8f4d312f2149c92c44c4830789f, height=728712
electrs | [2022-03-23T22:32:45.074Z INFO electrs::index] indexing 1 blocks: [728713…728713]
electrs | [2022-03-23T22:32:45.184Z INFO electrs::chain] chain updated: tip=00000000000000000000441339dcfe42ff13a89d74d592627b4ee49cb2118759, height=728713
electrs | [2022-03-23T22:39:58.198Z INFO electrs::index] indexing 1 blocks: [728714…728714]
electrs | [2022-03-23T22:39:58.360Z INFO electrs::chain] chain updated: tip=00000000000000000004c87d2f3603b2ee4cd56cdd53c4ac527ead43ee559737, height=728714
electrs | [2022-03-23T22:53:31.588Z INFO electrs::index] indexing 1 blocks: [728715…728715]
electrs | [2022-03-23T22:53:31.751Z INFO electrs::chain] chain updated: tip=0000000000000000000064adfa51617917bca11881f7e06ac371af8b224fa5a6, height=728715
electrs | [2022-03-23T22:58:51.984Z INFO electrs::index] indexing 1 blocks: [728716…728716]
electrs | [2022-03-23T22:58:52.344Z INFO electrs::chain] chain updated: tip=0000000000000000000168c8e927fc60b76405f217e5af3c965f0a811007b9f8, height=728716
electrs | [2022-03-23T23:06:31.714Z INFO electrs::index] indexing 1 blocks: [728717…728717]
electrs | [2022-03-23T23:06:32.008Z INFO electrs::chain] chain updated: tip=00000000000000000003a6db487e6e3433a77d2a04a6f947c3cbe8181c7cdd05, height=728717
electrs | [2022-03-23T23:27:12.158Z INFO electrs::index] indexing 1 blocks: [728718…728718]
electrs | [2022-03-23T23:27:12.412Z INFO electrs::chain] chain updated: tip=000000000000000000052382ef683117553af74f390d5078716194d03fadcb33, height=728718
electrs | [2022-03-23T23:30:17.933Z INFO electrs::index] indexing 1 blocks: [728719…728719]
electrs | [2022-03-23T23:30:18.078Z INFO electrs::chain] chain updated: tip=000000000000000000013302b35e2d09ce23c85b4cfc9afe2a66846766771fba, height=728719
electrs | [2022-03-23T23:42:50.502Z INFO electrs::index] indexing 1 blocks: [728720…728720]
electrs | [2022-03-23T23:42:50.713Z INFO electrs::chain] chain updated: tip=000000000000000000053475f64d998b2d16445e740b45747965c4e635e94e36, height=728720
electrs | [2022-03-23T23:54:27.206Z INFO electrs::index] indexing 1 blocks: [728721…728721]
electrs | [2022-03-23T23:54:27.377Z INFO electrs::chain] chain updated: tip=00000000000000000003f7219641c414dc5121937b302c4f5d7f922e74a51292, height=728721
electrs | [2022-03-23T23:54:54.164Z INFO electrs::index] indexing 1 blocks: [728722…728722]
electrs | [2022-03-23T23:54:54.255Z INFO electrs::chain] chain updated: tip=00000000000000000005ee98e684888ead90b015bad61d39ab6034306308bbe6, height=728722
electrs | [2022-03-24T00:15:35.833Z INFO electrs::index] indexing 1 blocks: [728723…728723]
electrs | [2022-03-24T00:15:36.136Z INFO electrs::chain] chain updated: tip=0000000000000000000898906c526cf98234104a8bd587b76a93f6245c63c006, height=728723

Tor logs

Attaching to tor, umbrel_tor_server_1
tor | Mar 23 22:18:10.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Mar 23 22:20:56.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Mar 23 23:20:03.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Mar 24 00:01:43.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor_server_1 | Mar 23 21:09:08.000 [notice] Heartbeat: Tor’s uptime is 1 day 0:00 hours, with 79 circuits open. I’ve sent 57.37 MB and received 25.20 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 38 connections with IPv4 and 0 with IPv6.
tor_server_1 | Mar 23 21:09:08.000 [notice] While bootstrapping, fetched this many bytes: 643747 (consensus network-status fetch); 14096 (authority cert fetch); 5170486 (microdescriptor fetch)
tor_server_1 | Mar 23 21:09:08.000 [notice] While not bootstrapping, fetched this many bytes: 725396 (consensus network-status fetch); 202343 (microdescriptor fetch)
tor_server_1 | Mar 23 21:09:08.000 [notice] Heartbeat: Tor’s uptime is 1 day 0:00 hours, with 119 circuits open. I’ve sent 57.30 MB and received 25.42 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 56 connections with IPv4 and 0 with IPv6.
tor_server_1 | Mar 23 21:09:08.000 [notice] While bootstrapping, fetched this many bytes: 643339 (consensus network-status fetch); 13136 (authority cert fetch); 4935900 (microdescriptor fetch)
tor_server_1 | Mar 23 21:09:08.000 [notice] While not bootstrapping, fetched this many bytes: 667975 (consensus network-status fetch); 172667 (microdescriptor fetch)
tor_server_1 | Mar 23 22:17:53.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.

==== Result ====

The debug script did not automatically detect any issues with your Umbrel.

Lightning is a off-chain wallet, and the channels state are in the device you opened them. So you will only recover btc wallet (on-chain).
But you are not using recommended hardware, think you are in your own.

Interesting… I have the same thing happening. I started a new instance of umbrel about 6 days ago, I have no apps loaded on it, I have no wallets attached to it, no LND channels, just bare bones. Everything was fine once the ledger synced up and I logged in today to and LND says it’s running but Lightning Wallet is “syncing.”

I have the same “wallet not created” message in my logs. I’m planning on shutting everything down and reflashing the microSD. Luckily for me, I have nothing to lose, but it’s making me less likely to offer up liquidity to the LN via channels after seeing stuff like this.

He’s not talking about channel liquidity, he’s saying his wallets aren’t showing up.

Yeah. Again, maybe you read: using HD is not recommended. Good luck.

What does that have to do with his wallet being locked? HHD isn’t reccomended, but that doesn’t mean it won’t work. WD Passport should work. I’m having the same problem with mine and I’m running an SSD.

It looks like this has happened in the past… Failed to recover wallets, corruptions, and unable to reset - #5 by johnverman

@DarthCoin, do you know of a good way to get Umbrel to re-recognize the seed phrase without starting all over?

I always recommend to recover your funds from a dead umbrel node using tools like Blixt, Zap (onchain only), Voltage, Sparrow (onchain), BW onchain) and DO NOT restore your old seed into a new umbrel instance (after you rebuild it).

Why? For many reasons:

  • is good to start fresh with a new nodeid, that old nodeid is already “compromised”
  • cleanup UTXOs, consolidating etc
  • whatever other “magic” shit happening when you use same seed and get stuck, so better avoid that
  • you can always keep using that old nodeid in Blixt as a companion with private channels to your new umbrel node.
1 Like

Is there any reason you can think of that would make our seed file disappear from the directory?

Thank you all. I can’t think of why this is happening. I was able to access the BTC via Bluewallet.

After the first issue I used a new HD, SD and Pi.

1 Like

It would be nice if there was a “restore from seed” feature within the Ubrel GUI. It’s a pain in the ass to have to start everything over from scratch when this problem comes up. I’ve also noticed that things are a little finicky when starting a new instance of Umbrel (completely new AEZEED) while trying to keep the same user name. Not sure why that is.

Agreed, users need a simple fast way to recover a dead node.
You can use Voltage.cloud for example, to recover your dead node.

Once you have your funds back in onchain, you can send them to your new Umbrel instance and start over.
Remember: do not start a new Umbrel with the same seed! Just start from 0, new seed, new wallet, new nodeID, new user.

1 Like