# Can not access http://umbrel.local **URL:** \ **Category:** General Discussion\ **Created:** [July 2, 2023, 1:35pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951 "2023-07-02T13:35:59Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 2, 2023, 1:35pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/1 "2023-07-02T13:35:59Z")
I have successfully completed the following and receive the following…“Umbrel is now accessible at [http://umbrel.local](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](https://community.getumbrel.com/) or [Telegram chat](https://t.me/getumbrel). **Error: Failed to start containers** Something went wrong when starting Umbrel. Need help? Feel free to jump on our [community forum](https://community.getumbrel.com/) or [Telegram chat](https://t.me/getumbrel). **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](http://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](https://community.getumbrel.com/) or [Telegram chat](https://t.me/getumbrel). [Restart](http://192.168.0.168/#)[Shutdown](http://192.168.0.168/#)[community](https://community.getumbrel.com/) ---
**Author:** ![usernameisJim](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/usernameisjim/32/3309_2.png) [@usernameisJim](https://community.umbrel.com/u/usernameisJim)\ **Post date:** [July 2, 2023, 9:47pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/2 "2023-07-02T21:47:15Z")
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](https://umbrel.com/#start) and will result in no data loss [Steps to SSH are here](https://community.umbrel.com/t/official-umbrel-troubleshooting-guide-and-faq/9873) under How to SSH ---
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 3, 2023, 12:24pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/3 "2023-07-03T12:24:20Z")
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. ---
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 5, 2023, 4:57pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/4 "2023-07-05T16:57:32Z")
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](http://umbrel.local) Jul 03 20:20:28 umbrel umbrel startup[1070]: [http://192.168.0.168](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](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](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](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](http://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 ---
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 5, 2023, 6:43pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/5 "2023-07-05T18:43:11Z")
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 ---
**Author:** ![usernameisJim](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/usernameisjim/32/3309_2.png) [@usernameisJim](https://community.umbrel.com/u/usernameisJim)\ **Post date:** [July 12, 2023, 1:46am UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/6 "2023-07-12T01:46:55Z")
Can you share the output of this command? `~/umbrel/scripts/app compose bitcoin logs --tail 250` And can paste it to [www.pastebin.com](http://www.pastebin.com) and share a link for review You can also ping me on [Telegram: Contact @usernameisJim](https://t.me/usernameisJim) ---
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 12, 2023, 11:16am UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/7 "2023-07-12T11:16:34Z")
I am new to pastebin, so hoping this is the proper link [https://pastebin.com/fDx7Zfar](https://pastebin.com/fDx7Zfar) ---
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 12, 2023, 11:47am UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/8 "2023-07-12T11:47:25Z")
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’. ---
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 12, 2023, 2:18pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/9 "2023-07-12T14:18:38Z")
I ran sudo ~/umbrel/scripts/debug and pasted it in… [https://pastebin.com/DgkuuPCF](https://pastebin.com/DgkuuPCF) ---
**Author:** ![usernameisJim](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/usernameisjim/32/3309_2.png) [@usernameisJim](https://community.umbrel.com/u/usernameisJim)\ **Post date:** [July 12, 2023, 6:03pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/10 "2023-07-12T18:03:28Z")
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 ---
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 12, 2023, 6:57pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/11 "2023-07-12T18:57:57Z")
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… > **[umbrel@umbrel:~ $ sudo ~/umbrel/scripts/debug\[sudo\] password for umbrel:====...](https://pastebin.com/DgkuuPCF)** > > Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time. Only because there seems to be a lot of errors in this log. In the meantime I’ll reflash Thank you. ---
**Author:** ![zolds13](https://avatars.discourse-cdn.com/v4/letter/z/e36b37/32.png) [@zolds13](https://community.umbrel.com/u/zolds13)\ **Post date:** [July 12, 2023, 11:21pm UTC](https://community.umbrel.com/t/can-not-access-http-umbrel-local/12951/12 "2023-07-12T23:21:56Z")
I reflashed the Micro sd. Here is what happens, every time. [http://umbrel.local](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](https://pastebin.com/p7mv5JsD)