Bitcoin & Lightening Wallet are not working in Umbrel


I have recently set up Umbrel App in Raspberry pi 4. I am unable to use bitcoin & lightening wallet as the UI is still not loading up.
I have left it running more than 2 days after blockchain 100% completion sync. My blockchain is syncing very good it is validating new blocks. But the Bitcoin wallet and Lightning Wallet UI are not working also either they are not showing the bitcoin deposit address.

Earlier I was able to see those wallet addresses. I had Power cuts few times as there was a storm in my location. but as I left it connected to the power supply, My raspberry & internet started again, hence doing its own booting and startup.

As per Guide, I did a troubleshoot.

  1. SSH umbrel@umbrel and password
    2)Run the command ~/umbrel/scripts/debug --upload
  2. I got a link - https://umbrel-paste.vercel.app/35cda6b9-3da1-4c20-9330-2a5d88ba767b

Please Admin’s of this community help me figure out the problem to fix it asap. My dream was to run a full node with block explorer. I tried to search on forums and Google search but couldn’t figure it.

1 Like

Hello,
power cuts are really bad. The blockchain data could be damaged and maybe needs reindexing.
I cannot view the logs you uploaded to vercel.app to dig deeper into this. It’s showing “page not found” on my end. (@aarondewes ?)

This script could not automatically detect an issue with your Umbrel.
Please share the following links and paste it in the Umbrel Telegram group (Telegram: Contact @getumbrel) so we can help you with your problem.
https://umbrel-paste.vercel.app/35cda6b9-3da1-4c20-9330-2a5d88ba767b
umbrel@umbrel:~ $ ~/umbrel/scripts/debug --upload

= Umbrel debug info =

Umbrel version

0.3.10

Umbrel OS version

v0.3.10

Raspberry Pi Model

Revision : d03114
Serial : 10000000b802453e
Model : Raspberry Pi 4 Model B Rev 1.4

Firmware

Feb 25 2021 12:10:40
Copyright (c) 2012 Broadcom
version 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) (release) (start)

Temperature

temp=48.7’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 4.0G 1.4G 39M 2.4G 3.6G
Swap: 4.1G 680M 3.4G

total: 51.6%
electrs: 34.3%
system: 10.5%
bitcoin: 6.5%
tor: 0.3%
lnd: 0%

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 29G 2.8G 26G 10% /
/dev/sda1 916G 482G 388G 56% /home/umbrel/umbrel

Startup service logs

May 11 17:46:44 umbrel umbrel startup[2429]: ======================================
May 11 17:46:44 umbrel umbrel startup[2429]: Setting environment variables…
May 11 17:46:44 umbrel umbrel startup[2429]: Starting karen…
May 11 17:46:44 umbrel umbrel startup[2429]: Starting backup monitor…
May 11 17:46:44 umbrel umbrel startup[2429]: Starting decoy backup trigger…
May 11 17:46:44 umbrel umbrel startup[2429]: Starting Docker services…
May 11 17:46:48 umbrel umbrel startup[2429]: dashboard is up-to-date
May 11 17:46:48 umbrel umbrel startup[2429]: tor is up-to-date
May 11 17:46:48 umbrel umbrel startup[2429]: electrs is up-to-date
May 11 17:46:48 umbrel umbrel startup[2429]: manager is up-to-date
May 11 17:46:48 umbrel umbrel startup[2429]: Starting lnd …
May 11 17:46:48 umbrel umbrel startup[2429]: nginx is up-to-date
May 11 17:46:48 umbrel umbrel startup[2429]: bitcoin is up-to-date
May 11 17:46:52 umbrel umbrel startup[2429]: Starting lnd … done
May 11 17:46:52 umbrel umbrel startup[2429]: middleware is up-to-date
May 11 17:46:52 umbrel umbrel startup[2429]: Starting neutrino-switcher …
May 11 17:46:56 umbrel umbrel startup[2429]: Starting neutrino-switcher … done
May 11 17:46:57 umbrel umbrel startup[2429]: Starting installed apps…
May 11 17:46:57 umbrel umbrel startup[2429]: Umbrel is now accessible at
May 11 17:46:57 umbrel umbrel startup[2429]: http://umbrel.local
May 11 17:46:57 umbrel umbrel startup[2429]: http://192.168.0.100
May 11 17:46:57 umbrel systemd[1]: Started Umbrel Startup Service.
May 11 18:05:09 umbrel passwd[20110]: pam_unix(passwd:chauthtok): password changed for umbrel
May 11 19:07:47 umbrel passwd[32216]: pam_unix(passwd:chauthtok): password changed for umbrel
May 11 20:21:25 umbrel passwd[19930]: pam_unix(passwd:chauthtok): password changed for umbrel
May 12 05:38:42 umbrel passwd[23566]: pam_unix(passwd:chauthtok): password changed for umbrel
May 12 06:04:47 umbrel passwd[9477]: pam_unix(passwd:chauthtok): password changed for umbrel
May 12 06:09:06 umbrel passwd[12459]: pam_unix(passwd:chauthtok): password changed for umbrel
May 12 08:03:15 umbrel passwd[27922]: pam_unix(passwd:chauthtok): password changed for umbrel

External storage service logs

– Logs begin at Tue 2021-05-11 17:17:01 UTC, end at Wed 2021-05-12 08:50:43 UTC. –
May 11 17:29:15 umbrel systemd[1]: Starting External Storage Mounter…
May 11 17:29:15 umbrel external storage mounter[364]: Running external storage mount script…
May 11 17:29:15 umbrel external storage mounter[364]: Found device “WD Elements 25A2”
May 11 17:29:15 umbrel external storage mounter[364]: Blacklisting USB device IDs against UAS driver…
May 11 17:29:15 umbrel external storage mounter[364]: Rebinding USB drivers…
May 11 17:29:15 umbrel external storage mounter[364]: Checking USB devices are back…
May 11 17:29:15 umbrel external storage mounter[364]: Waiting for USB devices…
May 11 17:29:16 umbrel external storage mounter[364]: Waiting for USB devices…
May 11 17:29:17 umbrel external storage mounter[364]: Checking if the device is ext4…
May 11 17:29:17 umbrel external storage mounter[364]: Yes, it is ext4
May 11 17:29:22 umbrel external storage mounter[364]: Checking if device contains an Umbrel install…
May 11 17:29:22 umbrel external storage mounter[364]: Yes, it contains an Umbrel install
May 11 17:29:22 umbrel external storage mounter[364]: Bind mounting external storage over local Umbrel installation…
May 11 17:29:22 umbrel external storage mounter[364]: Bind mounting external storage over local Docker data dir…
May 11 17:29:22 umbrel external storage mounter[364]: Bind mounting external storage to /swap
May 11 17:29:22 umbrel external storage mounter[364]: Bind mounting SD card root at /sd-card…
May 11 17:29:22 umbrel external storage mounter[364]: Checking Umbrel root is now on external storage…
May 11 17:29:24 umbrel external storage mounter[364]: Checking /var/lib/docker is now on external storage…
May 11 17:29:24 umbrel external storage mounter[364]: Checking /swap is now on external storage…
May 11 17:29:24 umbrel external storage mounter[364]: Setting up swapfile
May 11 17:29:28 umbrel external storage mounter[364]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
May 11 17:29:28 umbrel external storage mounter[364]: no label, UUID=65f79c5f-1ce9-4b80-8495-dc304d8a73f1
May 11 17:29:28 umbrel external storage mounter[364]: Checking SD Card root is bind mounted at /sd-root…
May 11 17:29:28 umbrel external storage mounter[364]: Starting external drive mount monitor…
May 11 17:29:28 umbrel external storage mounter[364]: Mount script completed successfully!
May 11 17:29:28 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Tue 2021-05-11 17:17:01 UTC, end at Wed 2021-05-12 08:50:43 UTC. –
May 11 17:46:43 umbrel systemd[1]: Starting External Storage SDcard Updater…
May 11 17:46:43 umbrel external storage updater[2358]: Checking if SD card Umbrel is newer than external storage…
May 11 17:46:44 umbrel external storage updater[2358]: No, SD version is not newer, exiting.
May 11 17:46:44 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

Removing network umbrel_main_network
karen is running in /home/umbrel/umbrel/events
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
karen is running in /home/umbrel/umbrel/events
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
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…
Creating backup…
Adding random padding…
1+0 records in
1+0 records out
400 bytes copied, 0.000262181 s, 1.5 MB/s
Creating encrypted tarball…
backup/
backup/channel.backup
backup/.padding
Uploading backup…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1146 100 146 100 1000 36 250 0:00:04 0:00:03 0:00:01 287
{“message”:“Successfully uploaded backup 1620786278446.tar.gz.pgp for backup ID 549a43de63d7b79104ddb0f366f3e7dff7ae9fa8c5a437eb67e3163c227b43d6”}

====== Backup success =======

Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
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: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully

Docker containers

NAMES STATUS
middleware Up 15 hours
bitcoin Up 15 hours
nginx Up 15 hours
lnd Restarting (2) 17 seconds ago
manager Up 15 hours
dashboard Up 15 hours
electrs Up 15 hours
tor Up 15 hours

Bitcoin Core logs

Attaching to bitcoin
bitcoin | 2021-05-12T06:58:45Z Socks5() connect to 176.189.105.146:8333 failed: general failure
bitcoin | 2021-05-12T07:04:13Z Socks5() connect to 2a01:4f9:c010:e14b::1:8333 failed: general failure
bitcoin | 2021-05-12T07:06:29Z Socks5() connect to 46.142.8.226:8333 failed: general failure
bitcoin | 2021-05-12T07:06:37Z UpdateTip: new best=000000000000000000090eaec79e42aecd341ec859c3c54998fc167e1dc01bee height=683227 version=0x20000000 log2_work=92.872482 tx=641536798 date=‘2021-05-12T07:06:28Z’ progress=1.000000 cache=102.6MiB(772088txo)
bitcoin | 2021-05-12T07:07:18Z Socks5() connect to 85.206.165.170:8333 failed: general failure
bitcoin | 2021-05-12T07:14:28Z Socks5() connect to 92.193.140.249:8333 failed: host unreachable
bitcoin | 2021-05-12T07:14:33Z UpdateTip: new best=0000000000000000000362f6fd4089b59b75b48306afc31a74adc9434188fe42 height=683228 version=0x20000004 log2_work=92.872496 tx=641538458 date=‘2021-05-12T07:14:18Z’ progress=1.000000 cache=102.8MiB(773524txo)
bitcoin | 2021-05-12T07:30:25Z Socks5() connect to 81.200.90.20:8333 failed: general failure
bitcoin | 2021-05-12T07:37:42Z UpdateTip: new best=000000000000000000007e56f9d30a55170464fa346e38d628398c0cf329f2c3 height=683229 version=0x20000004 log2_work=92.872510 tx=641541190 date=‘2021-05-12T07:37:33Z’ progress=1.000000 cache=104.1MiB(784813txo)
bitcoin | 2021-05-12T07:41:19Z Socks5() connect to 46.80.103.93:8333 failed: general failure
bitcoin | 2021-05-12T07:41:40Z Socks5() connect to 2605:a601:a923:2300:a845:c0b5:dd2c:486b:8333 failed: connection refused
bitcoin | 2021-05-12T07:55:59Z Socks5() connect to 172.98.92.113:8333 failed: connection refused
bitcoin | 2021-05-12T07:56:03Z Pre-allocating up to position 0x200000 in rev02578.dat
bitcoin | 2021-05-12T07:56:03Z UpdateTip: new best=0000000000000000000800cc5e256dd67a2a80be25ce0f2d0953b622f0fb9eb8 height=683230 version=0x20c00004 log2_work=92.872524 tx=641544036 date=‘2021-05-12T07:55:38Z’ progress=1.000000 cache=105.3MiB(794243txo)
bitcoin | 2021-05-12T08:02:29Z UpdateTip: new best=0000000000000000000b4b72ae9f3b8f8b5907dff25f5cdc53c97b2636bbaafc height=683231 version=0x20000000 log2_work=92.872538 tx=641544949 date=‘2021-05-12T08:02:11Z’ progress=1.000000 cache=107.4MiB(811564txo)
bitcoin | 2021-05-12T08:09:30Z UpdateTip: new best=0000000000000000000bce39b405325172ed99eb671ea45e4491bea41ddf2d4b height=683232 version=0x20a00004 log2_work=92.872552 tx=641546322 date=‘2021-05-12T08:08:59Z’ progress=1.000000 cache=107.7MiB(813693txo)
bitcoin | 2021-05-12T08:12:21Z UpdateTip: new best=0000000000000000000232b04e0b5c583b465542f7d40344410c5209d92e092d height=683233 version=0x27ffe000 log2_work=92.872566 tx=641548347 date=‘2021-05-12T08:11:52Z’ progress=1.000000 cache=108.1MiB(816789txo)
bitcoin | 2021-05-12T08:14:37Z Socks5() connect to 91.248.117.131:8333 failed: general failure
bitcoin | 2021-05-12T08:16:27Z Socks5() connect to 92.60.40.251:8333 failed: general failure
bitcoin | 2021-05-12T08:20:12Z Socks5() connect to 193.138.218.167:8333 failed: general failure
bitcoin | 2021-05-12T08:25:40Z UpdateTip: new best=000000000000000000073b8ae923ba4ecfab8a421b1a33ee852bef190f401e19 height=683234 version=0x20800004 log2_work=92.872580 tx=641550750 date=‘2021-05-12T08:25:36Z’ progress=1.000000 cache=110.5MiB(836451txo)
bitcoin | 2021-05-12T08:26:02Z Socks5() connect to 104.244.73.13:8333 failed: connection refused
bitcoin | 2021-05-12T08:30:51Z UpdateTip: new best=0000000000000000000a92321c673d960dd3aaeca82171b7f181302fb764f10d height=683235 version=0x20800000 log2_work=92.872594 tx=641553414 date=‘2021-05-12T08:30:27Z’ progress=1.000000 cache=111.9MiB(848543txo)
bitcoin | 2021-05-12T08:30:51Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
bitcoin | 2021-05-12T08:33:02Z Pre-allocating up to position 0x300000 in rev02578.dat
bitcoin | 2021-05-12T08:33:02Z UpdateTip: new best=000000000000000000021cf014832c5a1561a5f6d420105e192a6a157d3fe869 height=683236 version=0x36e6e004 log2_work=92.872608 tx=641556112 date=‘2021-05-12T08:32:35Z’ progress=1.000000 cache=112.9MiB(856354txo)
bitcoin | 2021-05-12T08:38:18Z Pre-allocating up to position 0x2000000 in blk02578.dat
bitcoin | 2021-05-12T08:38:18Z UpdateTip: new best=0000000000000000000beb5c41b866e7c1d25c5e8c7ec0f31ecad7157f0176ae height=683237 version=0x20000004 log2_work=92.872622 tx=641558760 date=‘2021-05-12T08:38:02Z’ progress=1.000000 cache=113.6MiB(862084txo)
bitcoin | 2021-05-12T08:49:24Z Socks5() connect to 2600:3c03::f03c:91ff:fe28:1445:8333 failed: general failure
bitcoin | 2021-05-12T08:49:50Z UpdateTip: new best=0000000000000000000568dc1c487c0777fd55fd8e9a29c61c659cc65f756e96 height=683238 version=0x21170004 log2_work=92.872636 tx=641561134 date=‘2021-05-12T08:49:44Z’ progress=1.000000 cache=115.1MiB(873984txo)

LND logs

Attaching to lnd
lnd | bufio.(*Reader).ReadSlice(0x40000ceef0, 0xa, 0x1, 0x0, 0x0, 0x0, 0x0)
lnd | bufio/bufio.go:360 +0x38
lnd | bufio.(*Reader).ReadLine(0x40000ceef0, 0x181003e, 0x1, 0x1, 0x1, 0x0, 0x0)
lnd | bufio/bufio.go:389 +0x30
lnd | github.com/jrick/logrotate/rotator.(*Rotator).Run(0x400003ca80, 0x10f8ae0, 0x40000c2270, 0x77274, 0x0)
lnd | github.com/jrick/logrotate@v1.0.0/rotator/rotator.go:100 +0x74
lnd | github.com/lightningnetwork/lnd/build.(*RotatingLogWriter).InitLogRotator.func1(0x400049cc30, 0x40000c2270)
lnd | github.com/lightningnetwork/lnd/build/logrotator.go:83 +0x40
lnd | created by github.com/lightningnetwork/lnd/build.(*RotatingLogWriter).InitLogRotator
lnd | github.com/lightningnetwork/lnd/build/logrotator.go:82 +0x290
lnd |
lnd | goroutine 9 [syscall]:
lnd | os/signal.signal_recv(0x0)
lnd | runtime/sigqueue.go:147 +0xc4
lnd | os/signal.loop()
lnd | os/signal/signal_unix.go:23 +0x20
lnd | created by os/signal.Notify.func1.1
lnd | os/signal/signal.go:150 +0x44
lnd |
lnd | goroutine 33 [select]:
lnd | github.com/lightningnetwork/lnd/signal.mainInterruptHandler()
lnd | github.com/lightningnetwork/lnd/signal/signal.go:83 +0xcc
lnd | created by github.com/lightningnetwork/lnd/signal.Intercept
lnd | github.com/lightningnetwork/lnd/signal/signal.go:49 +0xfc
lnd |
lnd | goroutine 34 [chan receive]:
lnd | go.etcd.io/bbolt.(*DB).freepages.func2(0x400012e060)
lnd | go.etcd.io/bbolt@v1.3.5-0.20200615073812-232d8fc87f50/db.go:1002 +0x34
lnd | created by go.etcd.io/bbolt.(*DB).freepages
lnd | go.etcd.io/bbolt@v1.3.5-0.20200615073812-232d8fc87f50/db.go:1001 +0x134

Tor logs

Attaching to tor
tor | May 12 02:16:57.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 02:27:39.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 02:35:35.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 03:19:23.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 03:31:46.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 03:38:08.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 03:43:21.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 03:48:30.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 03:59:29.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 04:39:40.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 05:07:55.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 05:24:11.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 05:36:29.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 05:38:06.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 05:46:52.000 [notice] Heartbeat: Tor’s uptime is 12:00 hours, with 158 circuits open. I’ve sent 177.60 MB and received 252.24 MB. I’ve received 2854 connections on IPv4 and 0 on IPv6. I’ve made 8 connections with IPv4 and 0 with IPv6.
tor | May 12 05:46:52.000 [notice] While not bootstrapping, fetched this many bytes: 350657 (consensus network-status fetch); 129165 (microdescriptor fetch)
tor | May 12 05:46:52.000 [notice] Average packaged cell fullness: 45.328%. TLS write overhead: 3%
tor | May 12 05:46:52.000 [notice] Our onion services received 0 v2 and 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits.
tor | May 12 06:01:39.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 06:41:26.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 06:45:19.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 06:47:44.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 07:06:29.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 07:07:18.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 07:14:28.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 07:30:25.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 07:41:19.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 08:14:37.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 08:16:27.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | May 12 08:20:12.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.

==== Result ====

This script could not automatically detect an issue with your Umbrel.
Please share the following links and paste it in the Umbrel Telegram group (Telegram: Contact @getumbrel) so we can help you with your problem.
https://umbrel-paste.vercel.app/d28ab895-f8ba-4471-9088-0442b31b3aa9

:sob: Here is Logs https://pastebin.com/D2K8k1cN

Thanks!

Did the node just finish downloading blockchain data? After downloading and validating the blockchain, electrum server needs another ~ 8-12hrs for indexing.

If that’s not the case, there’s something wrong with lnd service.

yes, it was more than 1 day finishing the blockchain data.

What should I do now?

Did you try to restart umbrel to see if LND catches up again?
If this doesn’t work, perhaps your sd card was damaged due to the power cuts. I’d try to reflash it or flash another sd card.

Ok, I will reflash it to umbrel os then I will tell you.

I did a reflash and started. it is still not loading the UI of the bitcoin & lightning wallet. What to do next? :disappointed_relieved:

What is LND service saying? Could you pls provide another overview of your logs?

here is the link = https://pastebin.com/WrFH21iT

Sorry, I meant the umbrel logs.

it is here
Logs raspberry - Pastebin.com

These are the logs after reflashing?

where can I find umbrel logs ?

You already did it in your first post.
The logs can be assembled on the settings page: Troubleshoot -> Start

ok I will try again now.

This is the new umbrel log - https://pastebin.com/XM1MueAG

Thanks! But I fear I can’t be of any help here.
LND service throws errors which I have never seen before and it seems to crash as well (restarted docker service). I think this needs deeper inspection of the lnd docker image. I’m sorry. Maybe the devs can help you out.

1 Like