Can not access http://umbrel.local

1

I have successfully completed the following and receive the following…“Umbrel is now accessible at
http://umbrel.local” Yet I receive a page full of errors.

Step 1 - Enter using SSH into your Umbrel node:

Step 2 - stop Umbrel node with:

cd umbrel

sudo ./scripts/stop

Step 3 - clean / reconfigure the broken container:

sudo rm -f .env && sudo ./scripts/configure

Step 4 - Restart your node:

sudo ./scripts/start

Here is what I see…

Starting Umbrel…

Restarting…

Please do not disconnect the power supply while the restart is in progress.

Shutting down…

Please do not disconnect the power supply until the shutdown is complete.

Shutdown complete

Error: External drive disconnected

The external drive was disconnected while Umbrel was running. This can sometimes happen when using an unofficial Raspberry Pi power supply.

Error: Version mismatch

The version of UmbrelOS on your microSD card is not compatible with the version of Umbrel on your external drive.

Error: System service failed

Something went wrong when starting Umbrel. Need help? Feel free to jump on our community forum or Telegram chat.

Error: Failed to start containers

Something went wrong when starting Umbrel. Need help? Feel free to jump on our community forum or Telegram chat.

Error: No external drive found

Please connect an external drive (at least 1TB) to a USB 3.0 port (blue color) on your Raspberry Pi and restart your Umbrel.

Note: If it’s not an external drive that you have used with Umbrel previously, all of the data on it (if any) will be erased.

Error: Multiple external drives found

Umbrel only works with one external drive of atleast 1TB size. Please disconnect any additional external drives and restart your Umbrel.

Error: Failed to connect external drive

There was an error connecting your external drive. Please consider using the recommended hardware listed on getumbrel.com.

Error: Failed to mount external drive

This normally happens if you’ve experienced filesystem corruption. Need help? Feel free to jump on our community forum or Telegram chat.

Restart Shutdown community

2

If you get this screen just try to reboot via SSH and: sudo reboot

If that gives you a new error let me know, otherwise reflashing your MicroSD card will fix the issue

Steps to reflash are here and will result in no data loss

Steps to SSH are here under How to SSH

3

After running the above steps, again, I was finally able to access umbrel.local. That’s the good news. However I see that my Bitcoin node says “Synchronized” but no data appears: no blocks, no connections. My mempool is not complete either. My research says this is due to a corrupt peer.dat file. I attempted the following with no luck.

Solution: delete / rename peers.dat

umbrel@umbrel:~ $ mv /mnt/data/umbrel/app-data/bitcoin/data/bitcoin/peers.dat /mnt/data/umbrel/app-data/bitcoin/data/bitcoin/peers.dat.bad

My problems all started with a power outage and then a tripped GFI on the circuit for my computer and raspberry pi4. I reflashed the Micro SD card multiple times before I discovered the tripped GFI.

So if I can address the peer.dat situation, assuming that is the problem, I think I’ll be good.

Should I run the Umbrel logs and post here?

Thanks for the help.

4

Here is the Umbrel logs. Currently I can not sync my node.

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

Umbrel version

0.5.4

Flashed OS version

v0.5.4

Raspberry Pi Model

Revision : d03115
Serial : 100000007decb32e
Model : Raspberry Pi 4 Model B Rev 1.5

Firmware

May 9 2023 12:16:34
Copyright (c) 2012 Broadcom
version 30aa0d70ab280427ba04ebc718c81d4350b9d394 (clean) (release) (start)

Temperature

temp=54.5’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 2.0G 3.9G 18M 1.9G 5.7G
Swap: 4.1G 0B 4.1G

total: 25.8%
electrs: 5.4%
lightning: 4.8%
mempool: 3.6%
bitcoin: 3.2%
system: 2.7%
lnbits: 2.4%
core-lightning: 2.2%
chatpad-ai: 1.5%

Memory monitor logs

2023-07-02 13:30:57 Memory monitor running!
2023-07-02 14:01:08 Memory monitor running!
3074 ? S 0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2023-07-02 15:19:33 Memory monitor running!
2023-07-02 23:40:34 Memory monitor running!
2023-07-03 19:41:13 Memory monitor running!
2023-07-03 19:45:02 Memory monitor running!
2023-07-03 19:51:01 Memory monitor running!
2023-07-03 20:17:24 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 119G 5.2G 110G 5% /
/dev/sda1 1.8T 624G 1.1T 36% /home/umbrel/umbrel

Startup service logs

Jul 03 20:18:41 umbrel umbrel startup[1070]: Creating bitcoin_bitcoind_1 … done
Jul 03 20:18:41 umbrel umbrel startup[1070]: Creating bitcoin_server_1 …
Jul 03 20:18:43 umbrel umbrel startup[1070]: Creating core-lightning_app_proxy_1 … done
Jul 03 20:18:43 umbrel umbrel startup[1070]: Creating core-lightning_tor_1 … done
Jul 03 20:18:53 umbrel umbrel startup[1070]: Creating chatpad-ai_web_1 … done
Jul 03 20:18:56 umbrel umbrel startup[1070]: Creating core-lightning_app_1 … done
Jul 03 20:19:01 umbrel umbrel startup[1070]: Creating core-lightning_c-lightning-rest_1 … done
Jul 03 20:19:06 umbrel umbrel startup[1070]: Creating lightning_app_1 … done
Jul 03 20:19:11 umbrel umbrel startup[1070]: Creating lightning_app_proxy_1 … done
Jul 03 20:19:14 umbrel umbrel startup[1070]: Creating lnbits_web_1 … done
Jul 03 20:19:14 umbrel umbrel startup[1070]: Creating lightning_lnd_1 … done
Jul 03 20:19:14 umbrel umbrel startup[1070]: Creating electrs_app_proxy_1 … done
Jul 03 20:19:15 umbrel umbrel startup[1070]: Creating electrs_tor_1 … done
Jul 03 20:19:16 umbrel umbrel startup[1070]: Creating bitcoin_tor_1 … done
Jul 03 20:19:17 umbrel umbrel startup[1070]: Creating electrs_electrs_1 … done
Jul 03 20:19:17 umbrel umbrel startup[1070]: Creating electrs_app_1 …
Jul 03 20:19:17 umbrel umbrel startup[1070]: Creating chatpad-ai_app_proxy_1 … done
Jul 03 20:19:23 umbrel umbrel startup[1070]: Creating lightning_tor_1 … done
Jul 03 20:19:24 umbrel umbrel startup[1070]: Creating lnbits_app_proxy_1 … done
Jul 03 20:19:35 umbrel umbrel startup[1070]: Creating mempool_web_1 … done
Jul 03 20:19:35 umbrel umbrel startup[1070]: Creating mempool_mariadb_1 … done
Jul 03 20:19:39 umbrel umbrel startup[1070]: Creating bitcoin_i2pd_daemon_1 … done
Jul 03 20:19:40 umbrel umbrel startup[1070]: Creating core-lightning_lightningd_1 … done
Jul 03 20:19:41 umbrel umbrel startup[1070]: Creating bitcoin_server_1 … done
Jul 03 20:19:54 umbrel umbrel startup[1070]: Creating mempool_api_1 … done
Jul 03 20:20:28 umbrel umbrel startup[1070]: Creating electrs_app_1 … done
Jul 03 20:20:28 umbrel umbrel startup[1070]: Umbrel is now accessible at
Jul 03 20:20:28 umbrel umbrel startup[1070]: http://umbrel.local
Jul 03 20:20:28 umbrel umbrel startup[1070]: http://192.168.0.168
Jul 03 20:20:28 umbrel systemd[1]: Started Umbrel Startup Service.

External storage service logs

Jul 03 20:16:45 umbrel external storage mounter[489]: Running external storage mount script…
Jul 03 20:16:45 umbrel external storage mounter[489]: Found device “WD My Passport 2626”
Jul 03 20:16:45 umbrel external storage mounter[489]: Blacklisting USB device IDs against UAS driver…
Jul 03 20:16:45 umbrel external storage mounter[489]: Rebinding USB drivers…
Jul 03 20:16:46 umbrel external storage mounter[489]: Checking USB devices are back…
Jul 03 20:16:46 umbrel external storage mounter[489]: Waiting for USB devices…
Jul 03 20:16:47 umbrel external storage mounter[489]: Waiting for USB devices…
Jul 03 20:16:48 umbrel external storage mounter[489]: Waiting for USB devices…
Jul 03 20:16:49 umbrel external storage mounter[489]: Checking if the device is ext4…
Jul 03 20:16:49 umbrel external storage mounter[489]: Yes, it is ext4
Jul 03 20:16:49 umbrel external storage mounter[489]: Checking filesystem for corruption…
Jul 03 20:16:49 umbrel external storage mounter[489]: e2fsck 1.44.5 (15-Dec-2018)
Jul 03 20:16:50 umbrel external storage mounter[489]: umbrel: clean, 380787/122093568 files, 171338666/488369920 blocks
Jul 03 20:16:50 umbrel external storage mounter[489]: Mounting partition…
Jul 03 20:16:50 umbrel external storage mounter[489]: Checking if device contains an Umbrel install…
Jul 03 20:16:50 umbrel external storage mounter[489]: Yes, it contains an Umbrel install
Jul 03 20:16:51 umbrel external storage mounter[489]: Bind mounting external storage over local Umbrel installation…
Jul 03 20:16:51 umbrel external storage mounter[489]: Bind mounting external storage over local Docker data dir…
Jul 03 20:16:51 umbrel external storage mounter[489]: Bind mounting external storage to /swap
Jul 03 20:16:51 umbrel external storage mounter[489]: Bind mounting SD card root at /sd-card…
Jul 03 20:16:51 umbrel external storage mounter[489]: Checking Umbrel root is now on external storage…
Jul 03 20:16:52 umbrel external storage mounter[489]: Checking /var/lib/docker is now on external storage…
Jul 03 20:16:52 umbrel external storage mounter[489]: Checking /swap is now on external storage…
Jul 03 20:16:52 umbrel external storage mounter[489]: Setting up swapfile
Jul 03 20:16:59 umbrel external storage mounter[489]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
Jul 03 20:16:59 umbrel external storage mounter[489]: no label, UUID=020d0283-a2bc-4568-87b5-a7d2e0f07520
Jul 03 20:16:59 umbrel external storage mounter[489]: Checking SD Card root is bind mounted at /sd-root…
Jul 03 20:16:59 umbrel external storage mounter[489]: Starting external drive mount monitor…
Jul 03 20:16:59 umbrel external storage mounter[489]: Mount script completed successfully!
Jul 03 20:16:59 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Mon 2023-07-03 20:16:40 UTC, end at Mon 2023-07-03 21:07:26 UTC. –
Jul 03 20:17:11 umbrel systemd[1]: Starting External Storage SDcard Updater…
Jul 03 20:17:11 umbrel external storage updater[991]: Checking if SD card Umbrel is newer than external storage…
Jul 03 20:17:11 umbrel external storage updater[991]: No, SD version is not newer, exiting.
Jul 03 20:17:11 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

Removing electrs_electrs_1 … done
Removing electrs_app_1 … done
Removing electrs_app_proxy_1 … done
Removing electrs_tor_1 … done
Going to remove electrs_app_1, electrs_electrs_1, electrs_app_proxy_1, electrs_tor_1
Stopping core-lightning_app_1 … done
Removing core-lightning_app_1 …
Removing core-lightning_c-lightning-rest_1 …
Removing core-lightning_tor_1 …
Removing core-lightning_app_proxy_1 …
Removing core-lightning_lightningd_1 …
Removing core-lightning_tor_1 … done
Removing core-lightning_lightningd_1 … done
Removing core-lightning_app_1 … done
Removing core-lightning_app_proxy_1 … done
Removing core-lightning_c-lightning-rest_1 … done
Going to remove core-lightning_app_1, core-lightning_c-lightning-rest_1, core-lightning_tor_1, core-lightning_app_proxy_1, core-lightning_lightningd_1

Stopping Docker services…

Stopping nginx …
Stopping auth …
Stopping dashboard …
Stopping tor_proxy …
Stopping manager …
Stopping tor_proxy … done
Stopping auth … done
Stopping nginx … done
Stopping dashboard … done
Stopping manager … done
Removing nginx …
Removing auth …
Removing dashboard …
Removing tor_proxy …
Removing manager …
Removing auth … done
Removing nginx … done
Removing manager … done
Removing tor_proxy … done
Removing dashboard … done
Removing network umbrel_main_network
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
electrs_app_1 Up 46 minutes
bitcoin_server_1 Up 47 minutes
core-lightning_lightningd_1 Restarting (1) Less than a second ago
core-lightning_c-lightning-rest_1 Restarting (1) 1 second ago
mempool_app_proxy_1 Up 48 minutes
mempool_web_1 Up 47 minutes
mempool_api_1 Up 47 minutes
core-lightning_app_proxy_1 Up 48 minutes
mempool_mariadb_1 Up 47 minutes
core-lightning_tor_1 Up 48 minutes
core-lightning_app_1 Up 48 minutes
lightning_lnd_1 Up 48 minutes
lightning_app_proxy_1 Up 48 minutes
lightning_app_1 Up 48 minutes
lightning_tor_1 Up 48 minutes
bitcoin_i2pd_daemon_1 Up 47 minutes
bitcoin_bitcoind_1 Restarting (1) Less than a second ago
bitcoin_tor_1 Up 48 minutes
bitcoin_app_proxy_1 Up 48 minutes
electrs_app_proxy_1 Up 48 minutes
electrs_electrs_1 Restarting (1) Less than a second ago
electrs_tor_1 Up 48 minutes
lnbits_app_proxy_1 Up 48 minutes
lnbits_web_1 Up 48 minutes
chatpad-ai_app_proxy_1 Up 48 minutes
chatpad-ai_web_1 Up 48 minutes
nginx Up 49 minutes
auth Up 49 minutes
manager Up 49 minutes
dashboard Up 49 minutes
tor_proxy Up 49 minutes

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.21.2 - - [Mon, 03 Jul 2023 21:07:23 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/114.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 03 Jul 2023 21:07:24 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/114.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.3 - - [Mon, 03 Jul 2023 21:07:24 GMT] “GET /v1/account/token?token=1e1e15655236213d2a79730a4293cae13fb3d25cf39a4cd9542623852a9c7760 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 03 Jul 2023 21:07:25 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/114.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 03 Jul 2023 21:07:26 GMT] “GET /v1/system/update-status HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.3 - - [Mon, 03 Jul 2023 21:07:26 GMT] “GET /v1/account/token?token=1e1e15655236213d2a79730a4293cae13fb3d25cf39a4cd9542623852a9c7760 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 03 Jul 2023 21:07:26 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/114.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 03 Jul 2023 21:07:27 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/114.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.3 - - [Mon, 03 Jul 2023 21:07:28 GMT] “GET /v1/account/token?token=1e1e15655236213d2a79730a4293cae13fb3d25cf39a4cd9542623852a9c7760 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 03 Jul 2023 21:07:28 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/114.0.0.0 Safari/537.36”
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | Jul 03 21:04:19.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:04:39.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:04:59.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:05:22.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:05:42.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:06:02.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:06:23.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:06:44.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:07:06.000 [notice] New control connection opened from 10.21.21.96.
tor_proxy | Jul 03 21:07:29.000 [notice] New control connection opened from 10.21.21.96.

App logs

bitcoin

Attaching to bitcoin_server_1, bitcoin_i2pd_daemon_1, bitcoin_bitcoind_1, bitcoin_tor_1, bitcoin_app_proxy_1
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
app_proxy_1 | Validating token: 1e1e15655236 …
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.3 - - [Mon, 03 Jul 2023 21:07:28 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.3 - - [Mon, 03 Jul 2023 21:07:30 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.3 - - [Mon, 03 Jul 2023 21:07:32 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36”
server_1 |
server_1 | umbrel-middleware
tor_1 | Jul 03 20:20:43.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:20:43.000 [notice] Bootstrapped 63% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:20:43.000 [notice] Bootstrapped 68% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:20:44.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Jul 03 20:20:44.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Jul 03 20:20:44.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Jul 03 20:20:46.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Jul 03 20:20:46.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Jul 03 20:20:46.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Jul 03 20:20:48.000 [notice] Bootstrapped 100% (done): Done
bitcoind_1 | 2023-07-03T21:07:28Z * Using 53.4 MiB for transaction index database
bitcoind_1 | 2023-07-03T21:07:28Z * Using 46.7 MiB for basic block filter index database
bitcoind_1 | 2023-07-03T21:07:28Z * Using 8.0 MiB for chain state database
bitcoind_1 | 2023-07-03T21:07:28Z * Using 318.9 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
bitcoind_1 | 2023-07-03T21:07:28Z init message: Loading block index…
bitcoind_1 | 2023-07-03T21:07:28Z Assuming ancestors of block 000000000000000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
bitcoind_1 | 2023-07-03T21:07:28Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
bitcoind_1 | 2023-07-03T21:07:28Z Opening LevelDB in /data/.bitcoin/blocks/index
bitcoind_1 | 2023-07-03T21:07:28Z Opened LevelDB successfully
bitcoind_1 | 2023-07-03T21:07:28Z Using obfuscation key for /data/.bitcoin/blocks/index: 0000000000000000
i2pd_daemon_1 | 20:38:07@158/error - Tunnel: Tunnel with id 672967073 already exists
i2pd_daemon_1 | 20:40:04@502/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 20:41:37@55/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:43:31@55/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:56:39@55/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:56:58@55/error - Streaming: No packets have been received yet
i2pd_daemon_1 | 20:57:06@55/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 21:05:59@502/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 21:06:46@158/error - Tunnels: Can’t select next hop for JAUAarUxr65F776Npkst1kpzN12OuiH~EMDX-lC0j24=
i2pd_daemon_1 | 21:06:46@158/error - Tunnels: Can’t create inbound tunnel, no peers available

core-lightning

Attaching to core-lightning_lightningd_1, core-lightning_c-lightning-rest_1, core-lightning_app_proxy_1, core-lightning_tor_1, core-lightning_app_1
app_1 | 2023/07/03 21:07:37 socat[29403] E connect(5, AF=1 “/root/.lightning/bitcoin/lightning-rpc”, 40): Connection refused
app_1 |
app_1 | Waiting for lightningd
app_1 | 2023/07/03 21:07:37 socat[29408] E connect(5, AF=1 “/root/.lightning/bitcoin/lightning-rpc”, 40): Connection refused
app_1 |
app_1 | Waiting for lightningd
app_1 | 2023/07/03 21:07:38 socat[29414] E connect(5, AF=1 “/root/.lightning/bitcoin/lightning-rpc”, 40): Connection refused
app_1 |
app_1 | Waiting for lightningd
app_1 | 2023/07/03 21:07:38 socat[29419] E connect(5, AF=1 “/root/.lightning/bitcoin/lightning-rpc”, 40): Connection refused
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.21.94:2103
app_proxy_1 | Waiting for 10.21.21.94:2103 to open…
c-lightning-rest_1 | at Socket. (/usr/src/app/lightning-client-js.js:82:23)
c-lightning-rest_1 | at Socket.emit (node:events:513:28)
c-lightning-rest_1 | at emitErrorNT (node:internal/streams/destroy:157:8)
c-lightning-rest_1 | at emitErrorCloseNT (node:internal/streams/destroy:122:3)
c-lightning-rest_1 | at processTicksAndRejections (node:internal/process/task_queues:83:21) {
c-lightning-rest_1 | errno: -111,
c-lightning-rest_1 | code: ‘ECONNREFUSED’,
c-lightning-rest_1 | syscall: ‘connect’,
c-lightning-rest_1 | address: ‘/root/.lightning/bitcoin/lightning-rpc’
c-lightning-rest_1 | }
lightningd_1 |
lightningd_1 | You can verify that your Bitcoin Core installation is ready for use by running:
lightningd_1 |
lightningd_1 | $ bitcoin-cli -rpcconnect=10.21.21.8 -rpcuser=… -stdinrpcpass echo ‘hello world’
lightningd_1 | 2023-07-03T21:07:25.921Z UNUSUAL plugin-bcli: Waiting for bitcoind to warm up…
lightningd_1 | 2023-07-03T21:07:25.921Z BROKEN plugin-bcli: \nCould not connect to bitcoind using bitcoin-cli. Is bitcoind running?\n\nMake sure you have bitcoind running and that bitcoin-cli is able to connect to bitcoind.\n\nYou can verify that your Bitcoin Core installation is ready for use by running:\n\n $ bitcoin-cli -rpcconnect=10.21.21.8 -rpcuser=… -stdinrpcpass echo ‘hello world’\n
lightningd_1 | The Bitcoin backend died.
lightningd_1 | 2023-07-03T21:07:25.928Z INFO plugin-bcli: Killing plugin: exited before we sent init
lightningd_1 | 2023-07-03T21:07:29.952Z UNUSUAL connectd: Bound to websocket 10.21.21.96:2106, but we cannot announce the websocket as we don’t announce anything else!
tor_1 | Jul 03 20:18:53.000 [notice] Bootstrapped 57% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:19:22.000 [notice] Bootstrapped 64% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:19:22.000 [notice] Bootstrapped 69% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:19:23.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Jul 03 20:19:23.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Jul 03 20:19:23.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Jul 03 20:19:23.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Jul 03 20:19:23.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Jul 03 20:19:23.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Jul 03 20:19:23.000 [notice] Bootstrapped 100% (done): Done

lightning

Attaching to lightning_lnd_1, lightning_app_proxy_1, lightning_app_1, lightning_tor_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 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.22.3:3006
app_proxy_1 | Waiting for 10.21.22.3:3006 to open…
app_proxy_1 | Lightning Node is now ready…
app_proxy_1 | Listening on port: 2101
lnd_1 | 2023-07-03 20:20:16.270 [INF] RPCS: RPC server listening on 0.0.0.0:10009
lnd_1 | 2023-07-03 20:20:17.324 [INF] RPCS: gRPC proxy started at 0.0.0.0:8080
lnd_1 | 2023-07-03 20:20:17.325 [INF] LTND: Opening the main database, this might take a few minutes…
lnd_1 | 2023-07-03 20:20:17.325 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
lnd_1 | 2023-07-03 20:20:18.244 [INF] LTND: Creating local graph and channel state DB instances
lnd_1 | 2023-07-03 20:20:19.243 [INF] CHDB: Checking for schema update: latest_version=29, db_version=29
lnd_1 | 2023-07-03 20:20:19.244 [INF] CHDB: Checking for optional update: prune_revocation_log=false, db_version=empty
lnd_1 | 2023-07-03 20:20:19.244 [INF] LTND: Database(s) now open (time_to_open=1.918579637s)!
lnd_1 | 2023-07-03 20:20:19.244 [INF] LTND: We’re not running within systemd or the service type is not ‘notify’
lnd_1 | 2023-07-03 20:20:19.244 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
tor_1 | Jul 03 20:19:32.000 [notice] Bootstrapped 57% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:19:32.000 [notice] Bootstrapped 64% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:19:33.000 [notice] Bootstrapped 69% (loading_descriptors): Loading relay descriptors
tor_1 | Jul 03 20:19:33.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Jul 03 20:19:33.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Jul 03 20:19:33.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Jul 03 20:19:33.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Jul 03 20:19:33.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Jul 03 20:19:33.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Jul 03 20:19:36.000 [notice] Bootstrapped 100% (done): Done

mempool

Attaching to mempool_app_proxy_1, mempool_web_1, mempool_api_1, mempool_mariadb_1
api_1 | at IncomingMessage. (/backend/package/rpc-api/jsonrpc.js:125:25)
api_1 | at IncomingMessage.emit (node:events:539:35)
api_1 | at endReadableNT (node:internal/streams/readable:1345:12)
api_1 | at processTicksAndRejections (node:internal/process/task_queues:83:21)
api_1 | Jul 3 21:07:02 [204] INFO: Disconnected from Electrum Server at 10.21.21.10:50001
api_1 | Jul 3 21:07:02 [204] ERR: Electrum error: {}
api_1 | Jul 3 21:07:25 [204] ERR: Electrum error: {}
api_1 | Jul 3 21:07:25 [204] INFO: Disconnected from Electrum Server at 10.21.21.10:50001
api_1 | Jul 3 21:07:47 [204] INFO: Disconnected from Electrum Server at 10.21.21.10:50001
api_1 | Jul 3 21:07:47 [204] ERR: Electrum error: {}
web_1 | /var/www/mempool/browser/resources
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.21.26:3006
app_proxy_1 | Waiting for 10.21.21.26:3006 to open…
app_proxy_1 | mempool is now ready…
app_proxy_1 | Listening on port: 3006
mariadb_1 | 2023-07-03 20:20:58 0 [Note] Plugin ‘FEEDBACK’ is disabled.
mariadb_1 | 2023-07-03 20:20:59 0 [Note] Server socket created on IP: ‘::’.
mariadb_1 | 2023-07-03 20:21:03 0 [Warning] ‘proxies_priv’ entry ‘@% root@1237f163a0b8’ ignored in --skip-name-resolve mode.
mariadb_1 | 2023-07-03 20:21:09 0 [Note] Reading of all Master_info entries succeeded
mariadb_1 | 2023-07-03 20:21:09 0 [Note] Added new Master_info ‘’ to hash table
mariadb_1 | 2023-07-03 20:21:09 0 [Note] mysqld: ready for connections.
mariadb_1 | Version: ‘10.5.12-MariaDB-1:10.5.12+maria~focal’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
mariadb_1 | 2023-07-03 20:21:09 4 [Warning] Aborted connection 4 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication)
mariadb_1 | 2023-07-03 20:21:09 3 [Warning] Aborted connection 3 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.26’ (This connection closed normally without authentication)
mariadb_1 | 2023-07-03 20:21:25 0 [Note] InnoDB: Buffer pool(s) load completed at 230703 20:21:25

==== Result ====

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

I suspect the…
i2pd_daemon_1 | 21:06:46@158/error - Tunnels: Can’t create inbound tunnel, no peers available

5

Hi, I have not had any luck restarting my node. It is still stuck, for lack of a technical term. I have tried to read through all the previous help topics yet I still can not get my node to update after a power outage. I’m passionate about Bitcoin and want to run my own node and clear all transactions, including lightning, through my node.

I have posted my logs.

I am willing to pay or contribute to an organization of your choice, to get my node back up. Obviously my attempts are not working.

Any assistance is appreciated.

Thanks you

6

Can you share the output of this command?

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

And can paste it to www.pastebin.com and share a link for review

You can also ping me on Telegram: Contact @usernameisJim

7

I am new to pastebin, so hoping this is the proper link

https://pastebin.com/fDx7Zfar

8

I also see this error, a lot…

docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See ‘docker run --help’.

9

I ran sudo ~/umbrel/scripts/debug and pasted it in…

https://pastebin.com/DgkuuPCF

10

It looks like the logs are not populating correctly, maybe there is still a corruption, I know it may be redundant but can we try to reflash the MicroSD card again and reconnect - if you have another one it may be worth to swap it in and then can repaste a new log once your dashboard is loading, if Bitcoin Node app is blank - the log should then populate correctly to show us any Bitcoin Core errors

11

I can re-flash.
I’d just like to confirm the when you are referring to “It looks like the logs are not populating correctly” that you have seen…

Only because there seems to be a lot of errors in this log.

In the meantime I’ll reflash

Thank you.

12

I reflashed the Micro sd. Here is what happens, every time.
http://umbrel.local results in This site can’t be reached

umbrel.local took too long to respond.

Then I attempt to ssh into umbrel@umbrel.local

=> ssh: connect to host umbrel.local port 22: Connection timed out
Then I attempt to ssh into umbrel@umbrel => WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
Then I go into the ssh hosts file and delete everyone.
Now I can get into umbrel@umbrel
I run ~/umbrel/scripts/app compose bitcoin logs --tail 250 => /home/umbrel/umbrel/scripts/app: line 79: NETWORK_IP: unbound variable
I run sudo ~/umbrel/scripts/debug and paste into…https://pastebin.com/p7mv5JsD