Lightning app stuck in launch

Support and Troubleshooting
1

image
image2697×1962 87.1 KB

The lightning app gets stuck whenever I try to open it.

My Bitcoin node is 100% synced. My channel.db is 161MB.

I have tried:

  • rebooting Umbrel
  • restarting Lightning via CLI
  • restarting just LND
  • restarting just Bitcoin
  • rm’ing bitcoin/settings.json

…yet nothing has changed.

LND conf:

This file is automatically generated by Umbrel, any changes will be overwritten.

Generated at: 2023-11-20T14:32:40.386Z

tlsautorefresh=true
sync-freelist=false
payments-expiration-grace-period=30m
maxpendingchannels=2
minchansize=200000
maxchansize=16777215
coop-close-target-confs=6
stagger-initial-reconnect=false
max-cltv-expiry=2016
max-commit-fee-rate-anchors=20
accept-keysend=true
accept-amp=true
gc-canceled-invoices-on-startup=true
gc-canceled-invoices-on-the-fly=false
allow-circular-route=false
alias=[redacted]
color=[redacted]
bitcoin.defaultchanconfs=2
bitcoin.basefee=1000
bitcoin.feerate=1
bitcoin.timelockdelta=80
tor.skip-proxy-for-clearnet-targets=true
tor.streamisolation=false
watchtower.active=false
wtclient.active=false
wtclient.sweep-fee-rate=10
routerrpc.minrtprob=0.01
routerrpc.apriori.hopprob=0.6
routerrpc.apriori.weight=0.5
routerrpc.apriori.penaltyhalflife=1h
routerrpc.attemptcost=100
routerrpc.attemptcostppm=1000
routerrpc.maxmchistory=1000
caches.channel-cache-size=20000
protocol.wumbo-channels=false
db.bolt.auto-compact=false
db.bolt.auto-compact-min-age=168h
rpcmiddleware.enable=true
routing.strictgraphpruning=false(base)

Debug info:

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

Umbrel version

0.5.4

Flashed OS version

v0.5.3

Raspberry Pi Model

Revision : c03111
Serial : 100000007dce7c10
Model : Raspberry Pi 4 Model B Rev 1.1

Firmware

Dec 1 2021 15:01:54
Copyright (c) 2012 Broadcom
version 71bd3109023a0c8575585ba87cbb374d2eeb038f (clean) (release) (start)

Temperature

temp=56.9’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 3.8G 1.9G 483M 5.0M 1.4G 1.8G
Swap: 4.1G 47M 4.0G

total: 49.2%
bitcoin: 18.3%
lightning: 13.1%
system: 7.2%
uptime-kuma: 5.2%
transmission: 2.7%
file-browser: 2.7%
electrs: 0%

Memory monitor logs

2023-11-16 12:29:21 Memory monitor running!
2023-11-16 13:36:04 Memory monitor running!
2023-11-16 13:43:43 Memory monitor running!
2023-11-16 13:48:21 Memory monitor running!
2023-11-16 22:37:28 Warning memory usage at 92%
2023-11-16 22:53:31 Warning memory usage at 91%
2023-11-16 23:26:35 Warning memory usage at 92%
2023-11-24 09:02:44 Memory monitor running!
2023-11-24 21:29:50 Memory monitor running!
2023-11-24 21:58:16 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 117G 3.9G 109G 4% /
/dev/sda1 1.8T 636G 1.1T 37% /home/umbrel/umbrel

Startup service logs

Nov 24 21:30:47 umbrel umbrel startup[1136]: Creating bitcoin_app_proxy_1 …
Nov 24 21:31:25 umbrel umbrel startup[1136]: Creating uptime-kuma_tor_server_1 … done
Nov 24 21:31:26 umbrel umbrel startup[1136]: Creating uptime-kuma_server_1 … done
Nov 24 21:31:27 umbrel umbrel startup[1136]: Creating bitcoin_tor_1 … done
Nov 24 21:31:28 umbrel umbrel startup[1136]: Creating lndg_tor_server_1 … done
Nov 24 21:31:29 umbrel umbrel startup[1136]: Creating file-browser_server_1 … done
Nov 24 21:31:31 umbrel umbrel startup[1136]: Creating transmission_tor_server_1 … done
Nov 24 21:31:36 umbrel umbrel startup[1136]: Creating bitcoin_tor_server_1 … done
Nov 24 21:31:40 umbrel umbrel startup[1136]: Creating bitcoin_bitcoind_1 … done
Nov 24 21:31:40 umbrel umbrel startup[1136]: Creating bitcoin_server_1 …
Nov 24 21:31:44 umbrel umbrel startup[1136]: Creating lightning_tor_server_1 … done
Nov 24 21:31:45 umbrel umbrel startup[1136]: Creating transmission_server_1 … done
Nov 24 21:31:46 umbrel umbrel startup[1136]: Creating file-browser_tor_server_1 … done
Nov 24 21:31:46 umbrel umbrel startup[1136]: Creating lightning_tor_1 … done
Nov 24 21:31:49 umbrel umbrel startup[1136]: Creating lndg_web_1 … done
Nov 24 21:31:51 umbrel umbrel startup[1136]: Creating file-browser_app_proxy_1 … done
Nov 24 21:31:53 umbrel umbrel startup[1136]: Creating lightning_app_1 … done
Nov 24 21:32:05 umbrel umbrel startup[1136]: Creating bitcoin_i2pd_daemon_1 … done
Nov 24 21:32:16 umbrel umbrel startup[1136]: Creating lightning_lnd_1 … done
Nov 24 21:32:37 umbrel umbrel startup[1136]: Creating bitcoin_server_1 … done
Nov 24 21:33:56 umbrel umbrel startup[1136]: Creating transmission_app_proxy_1 … done
Nov 24 21:33:56 umbrel umbrel startup[1136]: Creating uptime-kuma_app_proxy_1 … done
Nov 24 21:33:56 umbrel umbrel startup[1136]: Creating bitcoin_app_proxy_1 … done
Nov 24 21:33:56 umbrel umbrel startup[1136]: Creating lndg_app_proxy_1 … done
Nov 24 21:33:57 umbrel umbrel startup[1136]: Creating lightning_app_proxy_1 … done
Nov 24 21:33:58 umbrel umbrel startup[1136]: Umbrel is now accessible at
Nov 24 21:33:58 umbrel umbrel startup[1136]: [redacted]
Nov 24 21:33:58 umbrel umbrel startup[1136]: [redacted]
Nov 24 21:33:58 umbrel systemd[1]: Started Umbrel Startup Service.

External storage service logs

Nov 24 21:29:24 umbrel systemd[1]: Starting External Storage Mounter…
Nov 24 21:29:24 umbrel external storage mounter[482]: Running external storage mount script…
Nov 24 21:29:25 umbrel external storage mounter[482]: Found device “WD Elements 25A1”
Nov 24 21:29:25 umbrel external storage mounter[482]: Blacklisting USB device IDs against UAS driver…
Nov 24 21:29:25 umbrel external storage mounter[482]: Rebinding USB drivers…
Nov 24 21:29:25 umbrel external storage mounter[482]: Checking USB devices are back…
Nov 24 21:29:25 umbrel external storage mounter[482]: Waiting for USB devices…
Nov 24 21:29:26 umbrel external storage mounter[482]: Waiting for USB devices…
Nov 24 21:29:27 umbrel external storage mounter[482]: Checking if the device is ext4…
Nov 24 21:29:27 umbrel external storage mounter[482]: Yes, it is ext4
Nov 24 21:29:27 umbrel external storage mounter[482]: Checking filesystem for corruption…
Nov 24 21:29:27 umbrel external storage mounter[482]: e2fsck 1.44.5 (15-Dec-2018)
Nov 24 21:29:28 umbrel external storage mounter[482]: umbrel: clean, 335031/122093568 files, 174782841/488369920 blocks
Nov 24 21:29:28 umbrel external storage mounter[482]: Mounting partition…
Nov 24 21:29:28 umbrel external storage mounter[482]: Checking if device contains an Umbrel install…
Nov 24 21:29:28 umbrel external storage mounter[482]: Yes, it contains an Umbrel install
Nov 24 21:29:28 umbrel external storage mounter[482]: Bind mounting external storage over local Umbrel installation…
Nov 24 21:29:28 umbrel external storage mounter[482]: Bind mounting external storage over local Docker data dir…
Nov 24 21:29:28 umbrel external storage mounter[482]: Bind mounting external storage to /swap
Nov 24 21:29:28 umbrel external storage mounter[482]: Bind mounting SD card root at /sd-card…
Nov 24 21:29:28 umbrel external storage mounter[482]: Checking Umbrel root is now on external storage…
Nov 24 21:29:29 umbrel external storage mounter[482]: Checking /var/lib/docker is now on external storage…
Nov 24 21:29:29 umbrel external storage mounter[482]: Checking /swap is now on external storage…
Nov 24 21:29:29 umbrel external storage mounter[482]: Setting up swapfile
Nov 24 21:29:37 umbrel external storage mounter[482]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
Nov 24 21:29:37 umbrel external storage mounter[482]: no label, UUID=1fbff67d-8fb0-43ee-a5ff-e68c83d157f7
Nov 24 21:29:37 umbrel external storage mounter[482]: Checking SD Card root is bind mounted at /sd-root…
Nov 24 21:29:37 umbrel external storage mounter[482]: Starting external drive mount monitor…
Nov 24 21:29:37 umbrel external storage mounter[482]: Mount script completed successfully!
Nov 24 21:29:37 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Thu 2019-02-14 10:11:58 UTC, end at Fri 2023-11-24 22:49:06 UTC. –
Nov 24 21:29:49 umbrel systemd[1]: Starting External Storage SDcard Updater…
Nov 24 21:29:49 umbrel external storage updater[1080]: Checking if SD card Umbrel is newer than external storage…
Nov 24 21:29:49 umbrel external storage updater[1080]: No, SD version is not newer, exiting.
Nov 24 21:29:49 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: debug
karen is getting triggered!
cat: /home/umbrel/umbrel/app-data/electrs/umbrel-app.yml: No such file or directory
cat: /home/umbrel/umbrel/app-data/electrs/umbrel-app.yml: No such file or directory
cat: /home/umbrel/umbrel/app-data/electrs/docker-compose.yml: No such file or directory
Debug result file generated
Got signal: debug
karen is getting triggered!
cat: /home/umbrel/umbrel/app-data/electrs/umbrel-app.yml: No such file or directory
cat: /home/umbrel/umbrel/app-data/electrs/umbrel-app.yml: No such file or directory
cat: /home/umbrel/umbrel/app-data/electrs/docker-compose.yml: No such file or directory
Got signal: app-uninstall-lndg
karen is getting triggered!
Removing images for app lndg…
Stopping lndg_app_proxy_1 …
Stopping lndg_tor_server_1 …
Stopping lndg_web_1 …
Stopping lndg_app_proxy_1 … done
Stopping lndg_web_1 … done
Stopping lndg_tor_server_1 … done
Removing lndg_app_proxy_1 …
Removing lndg_tor_server_1 …
Removing lndg_web_1 …
Removing lndg_tor_server_1 … done
Removing lndg_app_proxy_1 … done
Removing lndg_web_1 … done
Network umbrel_main_network is external, skipping
Removing image getumbrel/tor:0.4.7.8@sha256:2ace83f22501f58857fa9b403009f595137fa2e7986c4fda79d82a8119072b6a
Failed to remove image for service tor_server: 409 Client Error for http+docker://localhost/v1.41/images/getumbrel/tor:0.4.7.8%40sha256:2ace83f22501f58857fa9b403009f595137fa2e7986c4fda79d82a8119072b6a?force=False&noprune=False: Conflict (“conflict: unable to remove repository reference “getumbrel/tor:0.4.7.8@sha256:2ace83f22501f58857fa9b403009f595137fa2e7986c4fda79d82a8119072b6a” (must force) - container 3668e86ee509 is using its referenced image 105438dd043f”)
Removing image ghcr.io/cryptosharks131/lndg:v1.7.0@sha256:30bb34fd735d6046fcaf7375ac32ad10b998b34798cb7d4d762c038284b5fc98
Debug result file generated
Got signal: debug
karen is getting triggered!
cat: /home/umbrel/umbrel/app-data/electrs/umbrel-app.yml: No such file or directory
cat: /home/umbrel/umbrel/app-data/electrs/umbrel-app.yml: No such file or directory
cat: /home/umbrel/umbrel/app-data/electrs/docker-compose.yml: No such file or directory
Debug result file generated
An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 240).
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
bitcoin_server_1 Up 48 minutes
lightning_lnd_1 Up 50 minutes
lightning_tor_1 Up 50 minutes
lightning_app_proxy_1 Up 50 minutes
lightning_app_1 Up 49 minutes
lightning_tor_server_1 Up 50 minutes
bitcoin_app_proxy_1 Up 49 minutes
bitcoin_tor_1 Up 49 minutes
bitcoin_i2pd_daemon_1 Up 50 minutes
bitcoin_bitcoind_1 Up 50 minutes
bitcoin_tor_server_1 Up 49 minutes
uptime-kuma_app_proxy_1 Up 50 minutes
uptime-kuma_tor_server_1 Up 50 minutes
uptime-kuma_server_1 Up 50 minutes (healthy)
file-browser_app_proxy_1 Up 50 minutes
file-browser_server_1 Up 50 minutes (healthy)
file-browser_tor_server_1 Up 50 minutes
transmission_server_1 Up 50 minutes
transmission_tor_server_1 Up 50 minutes
transmission_app_proxy_1 Up 50 minutes
nginx Up 50 minutes
tor_proxy Up 50 minutes
manager Up 50 minutes
dashboard Up 50 minutes
auth Up 50 minutes
tor_server Up 50 minutes

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.21.2 - - [Fri, 24 Nov 2023 22:49:09 GMT] “GET /v1/apps HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 24 Nov 2023 22:49:09 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/119.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 24 Nov 2023 22:49:09 GMT] “GET /v1/system/info HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 24 Nov 2023 22:49:09 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/119.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 24 Nov 2023 22:49:10 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/119.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.13 - - [Fri, 24 Nov 2023 22:49:10 GMT] “GET /v1/account/token?token=9f9f1f9409e676d3af60fdc4ad09b78c068a6ae4aafc0eea961f9cff4ae70be0 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 24 Nov 2023 22:49:12 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/119.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.13 - - [Fri, 24 Nov 2023 22:49:12 GMT] “GET /v1/account/token?token=9f9f1f9409e676d3af60fdc4ad09b78c068a6ae4aafc0eea961f9cff4ae70be0 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 24 Nov 2023 22:49:14 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/119.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.13 - - [Fri, 24 Nov 2023 22:49:14 GMT] “GET /v1/account/token?token=9f9f1f9409e676d3af60fdc4ad09b78c068a6ae4aafc0eea961f9cff4ae70be0 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | Nov 24 21:58:31.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor_proxy | Nov 24 21:58:32.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
tor_proxy | Nov 24 21:58:32.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
tor_proxy | Nov 24 21:58:33.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_proxy | Nov 24 21:58:33.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_proxy | Nov 24 21:58:33.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_proxy | Nov 24 21:58:33.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_proxy | Nov 24 21:58:33.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_proxy | Nov 24 21:58:33.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_proxy | Nov 24 21:58:34.000 [notice] Bootstrapped 100% (done): Done

App logs

bitcoin

Attaching to bitcoin_server_1, bitcoin_app_proxy_1, bitcoin_tor_1, bitcoin_i2pd_daemon_1, bitcoin_bitcoind_1, bitcoin_tor_server_1
bitcoind_1 | 2023-11-24T22:41:30Z Saw new header hash=000000000000000000025d8b92fbd44642d4f6845be725ecfcf9f1fb6dbd57d5 height=818324
bitcoind_1 | 2023-11-24T22:41:48Z New outbound peer connected: version: 70015, blocks=818324, peer=28 (outbound-full-relay)
bitcoind_1 | 2023-11-24T22:41:54Z New outbound peer connected: version: 70016, blocks=818323, peer=25 (outbound-full-relay)
bitcoind_1 | 2023-11-24T22:43:30Z UpdateTip: new best=000000000000000000025d8b92fbd44642d4f6845be725ecfcf9f1fb6dbd57d5 height=818324 version=0x23ef0000 log2_work=94.560094 tx=925420469 date=‘2023-11-24T22:39:52Z’ progress=0.999999 cache=19.4MiB(137158txo)
bitcoind_1 | 2023-11-24T22:43:50Z New outbound peer connected: version: 70016, blocks=818323, peer=32 (outbound-full-relay)
bitcoind_1 | 2023-11-24T22:44:09Z New outbound peer connected: version: 70016, blocks=818324, peer=33 (outbound-full-relay)
bitcoind_1 | 2023-11-24T22:44:14Z New outbound peer connected: version: 70016, blocks=818324, peer=31 (outbound-full-relay)
bitcoind_1 | 2023-11-24T22:44:14Z New outbound peer connected: version: 70016, blocks=818324, peer=35 (outbound-full-relay)
bitcoind_1 | 2023-11-24T22:45:09Z New outbound peer connected: version: 70016, blocks=818323, peer=36 (outbound-full-relay)
bitcoind_1 | 2023-11-24T22:47:13Z New outbound peer connected: version: 70016, blocks=818324, peer=37 (outbound-full-relay)
i2pd_daemon_1 | 22:14:00@810/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 22:14:00@36/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 22:21:27@982/error - Addressbook: Can’t find domain for reg.i2p
i2pd_daemon_1 | 22:21:28@982/error - Addressbook: Can’t resolve reg.i2p
i2pd_daemon_1 | 22:34:59@810/error - Tunnels: Can’t select next hop for PuXzegzJ2HNkdaATz~ps~Y2fukJMNIcGXad4Jbz2jwg=
i2pd_daemon_1 | 22:35:00@810/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 22:36:28@982/error - Addressbook: Can’t find domain for reg.i2p
i2pd_daemon_1 | 22:36:28@982/error - Addressbook: Can’t resolve reg.i2p
i2pd_daemon_1 | 22:48:14@810/error - Tunnels: Can’t select next hop for WMOHOp~hHzLo7NRBQyQ5QYR3kcdAtkaTNudlBSdowVc=
i2pd_daemon_1 | 22:48:15@810/error - Tunnels: Can’t create inbound tunnel, no peers available
tor_1 | Nov 24 22:00:00.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
tor_1 | Nov 24 22:00:28.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
tor_1 | Nov 24 22:00:31.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
tor_1 | Nov 24 22:00:32.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Nov 24 22:00:32.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Nov 24 22:00:32.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Nov 24 22:00:32.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Nov 24 22:00:32.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Nov 24 22:00:32.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Nov 24 22:00:33.000 [notice] Bootstrapped 100% (done): Done
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → [redacted]
app_proxy_1 | Waiting for 10.21.22.2:3005 to open…
app_proxy_1 | Bitcoin Node is now ready…
app_proxy_1 | Listening on port: 2100
server_1 | yarn run v1.22.18
server_1 | $ node ./bin/www
server_1 | Fri, 24 Nov 2023 22:01:06 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:33:9
server_1 | Fri, 24 Nov 2023 22:01:06 GMT morgan deprecated default format: use combined format at app.js:33:9
server_1 | Listening on port 3005

electrs

file-browser

Attaching to file-browser_app_proxy_1, file-browser_server_1, file-browser_tor_server_1
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://file-browser_server_1:80
app_proxy_1 | Waiting for file-browser_server_1:80 to open…
app_proxy_1 | File Browser is now ready…
app_proxy_1 | Listening on port: 7421
server_1 | 2023/11/24 21:59:05 Using config file: /.filebrowser.json
server_1 | 2023/11/24 21:59:05 Listening on [::]:80

lightning

Attaching to lightning_lnd_1, lightning_tor_1, lightning_app_proxy_1, lightning_app_1, lightning_tor_server_1
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | [backup-monitor] Checking channel backup…
app_1 | [backup-monitor] Sleeping…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
app_proxy_1 | Validating token: 9f9f1f9409e6 …
lnd_1 | 2023-11-24 22:49:16.967 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:18.037 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:18.798 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:19.097 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:20.172 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:20.782 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:21.226 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:22.282 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:23.346 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-11-24 22:49:24.402 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
tor_1 | Nov 24 21:59:10.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor_1 | Nov 24 21:59:12.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
tor_1 | Nov 24 21:59:15.000 [notice] Bootstrapped 71% (loading_descriptors): Loading relay descriptors
tor_1 | Nov 24 21:59:15.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Nov 24 21:59:16.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Nov 24 21:59:16.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Nov 24 21:59:16.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Nov 24 21:59:16.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Nov 24 21:59:16.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Nov 24 21:59:18.000 [notice] Bootstrapped 100% (done): Done

transmission

Attaching to transmission_server_1, transmission_tor_server_1, transmission_app_proxy_1
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → [redacted]
app_proxy_1 | Waiting for transmission_server_1:9091 to open…
app_proxy_1 | Transmission is now ready…
app_proxy_1 | Listening on port: 9091
server_1 | ───────────────────────────────────────
server_1 | GID/UID
server_1 | ───────────────────────────────────────
server_1 |
server_1 | User UID: 1000
server_1 | User GID: 1000
server_1 | ───────────────────────────────────────
server_1 |
server_1 | [custom-init] No custom files found, skipping…
server_1 | [ls.io-init] done.

uptime-kuma

Attaching to uptime-kuma_app_proxy_1, uptime-kuma_tor_server_1, uptime-kuma_server_1
server_1 | 2023-11-24T22:04:59Z [DB] INFO: Your database version: 10
server_1 | 2023-11-24T22:04:59Z [DB] INFO: Latest database version: 10
server_1 | 2023-11-24T22:04:59Z [DB] INFO: Database patch not needed
server_1 | 2023-11-24T22:04:59Z [DB] INFO: Database Patch 2.0 Process
server_1 | 2023-11-24T22:04:59Z [SERVER] INFO: Load JWT secret from database.
server_1 | 2023-11-24T23:05:00+01:00 [SERVER] INFO: Adding route
server_1 | 2023-11-24T23:05:03+01:00 [SERVER] INFO: Adding socket handler
server_1 | 2023-11-24T23:05:03+01:00 [SERVER] INFO: Init the server
server_1 | 2023-11-24T23:05:03+01:00 [SERVER] INFO: Listening on 3001
server_1 | 2023-11-24T23:05:03+01:00 [SERVICES] INFO: Starting nscd
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → [redacted]
app_proxy_1 | Waiting for uptime-kuma_server_1:3001 to open…
app_proxy_1 | Uptime Kuma is now ready…
app_proxy_1 | Listening on port: 8385

==== Result ====

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