# Cannot open Bitcoin/Lightning Nodes!

**URL:** <https://community.umbrel.com/t/cannot-open-bitcoin-lightning-nodes/14014>\
**Category:** Support and Troubleshooting\
**Created:** [October 22, 2023, 7:06pm UTC](https://community.umbrel.com/t/cannot-open-bitcoin-lightning-nodes/14014 "2023-10-22T19:06:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sylvanscott](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sylvanscott](https://community.umbrel.com/u/sylvanscott)\
**Post date:** [October 22, 2023, 7:06pm UTC](https://community.umbrel.com/t/cannot-open-bitcoin-lightning-nodes/14014/1 "2023-10-22T19:06:42Z")

</div>

cannot access bitcoin node or lightning node. will not connect to mempool. i reflashed latest umbrel OS. i have funds in bitcoin wallet. i must access them!! please help

## Startup service logs

Oct 22 18:42:30 umbrel umbrel startup[2235]: Creating lightning\_tor\_1 … done  
Oct 22 18:42:30 umbrel umbrel startup[2235]: Creating lightning\_tor\_server\_1 … done  
Oct 22 18:42:30 umbrel umbrel startup[2235]: Creating mempool\_app\_proxy\_1 … done  
Oct 22 18:42:30 umbrel umbrel startup[2235]: Creating mempool\_mariadb\_1 … done  
Oct 22 18:42:30 umbrel umbrel startup[2235]: Creating lightning\_app\_proxy\_1 … done  
Oct 22 18:42:35 umbrel umbrel startup[2235]: Creating electrs\_app\_proxy\_1 … done  
Oct 22 18:42:37 umbrel umbrel startup[2235]: Creating electrs\_tor\_1 … done  
Oct 22 18:42:39 umbrel umbrel startup[2235]: Creating lightning-terminal\_web\_1 … done  
Oct 22 18:42:39 umbrel umbrel startup[2235]: Creating bitcoin\_i2pd\_daemon\_1 … done  
Oct 22 18:42:40 umbrel umbrel startup[2235]: Creating bitcoin\_bitcoind\_1 … done  
Oct 22 18:42:40 umbrel umbrel startup[2235]: Creating lightning-terminal\_tor\_server\_1 … done  
Oct 22 18:42:40 umbrel umbrel startup[2235]: Creating bitcoin\_tor\_1 … done  
Oct 22 18:42:40 umbrel umbrel startup[2235]: Creating electrs\_electrs\_1 … done  
Oct 22 18:42:40 umbrel umbrel startup[2235]: Creating bitcoin\_server\_1 …  
Oct 22 18:42:40 umbrel umbrel startup[2235]: Creating electrs\_app\_1 …  
Oct 22 18:42:41 umbrel umbrel startup[2235]: Creating bitcoin\_tor\_server\_1 … done  
Oct 22 18:42:41 umbrel umbrel startup[2235]: Creating lightning-terminal\_app\_proxy\_1 … done  
Oct 22 18:42:41 umbrel umbrel startup[2235]: Creating electrs\_tor\_server\_1 … done  
Oct 22 18:42:42 umbrel umbrel startup[2235]: Creating lightning\_app\_1 … done  
Oct 22 18:42:42 umbrel umbrel startup[2235]: Creating lightning\_lnd\_1 … done  
Oct 22 18:42:42 umbrel umbrel startup[2235]: Creating bitcoin\_app\_proxy\_1 … done  
Oct 22 18:42:47 umbrel umbrel startup[2235]: Creating bitcoin\_server\_1 … done  
Oct 22 18:42:48 umbrel umbrel startup[2235]: Creating electrs\_app\_1 … done  
Oct 22 18:42:49 umbrel umbrel startup[2235]: Umbrel is now accessible at  
Oct 22 18:42:49 umbrel umbrel startup[2235]: [http://umbrel.local](http://umbrel.local)  
Oct 22 18:42:49 umbrel umbrel startup[2235]: [http://10.0.0.190](http://10.0.0.190)  
Oct 22 18:42:49 umbrel systemd[1]: Started Umbrel Startup Service.  
Oct 22 18:45:52 umbrel passwd[22174]: pam\_unix(passwd:chauthtok): password changed for umbrel  
Oct 22 18:47:23 umbrel passwd[27896]: pam\_unix(passwd:chauthtok): password changed for umbrel

## External storage service logs

Oct 16 13:26:03 umbrel external storage mounter[511]: Waiting for USB devices…  
Oct 16 13:26:04 umbrel external storage mounter[511]: Checking if the device is ext4…  
Oct 16 13:26:05 umbrel external storage mounter[511]: Yes, it is ext4  
Oct 16 13:26:05 umbrel external storage mounter[511]: Checking filesystem for corruption…  
Oct 16 13:26:05 umbrel external storage mounter[511]: e2fsck 1.44.5 (15-Dec-2018)  
Oct 16 13:26:05 umbrel external storage mounter[511]: umbrel: recovering journal  
Oct 16 13:26:13 umbrel external storage mounter[511]: Clearing orphaned inode 12714043 (uid=1000, gid=1000, mode=0100600, size=0)  
Oct 16 13:26:13 umbrel external storage mounter[511]: Clearing orphaned inode 12714042 (uid=1000, gid=1000, mode=0100600, size=0)  
Oct 16 13:26:13 umbrel external storage mounter[511]: Clearing orphaned inode 12714041 (uid=1000, gid=1000, mode=0100600, size=0)  
Oct 16 13:26:13 umbrel external storage mounter[511]: Clearing orphaned inode 12714000 (uid=1000, gid=1000, mode=0100600, size=0)  
Oct 16 13:26:13 umbrel external storage mounter[511]: Setting free inodes count to 60771795 (was 60773662)  
Oct 16 13:26:13 umbrel external storage mounter[511]: Setting free blocks count to 75425784 (was 76844487)  
Oct 16 13:26:13 umbrel external storage mounter[511]: umbrel: clean, 283181/61054976 files, 168764424/244190208 blocks  
Oct 16 13:26:13 umbrel external storage mounter[511]: Mounting partition…  
Oct 16 13:26:13 umbrel external storage mounter[511]: Checking if device contains an Umbrel install…  
Oct 16 13:26:13 umbrel external storage mounter[511]: Yes, it contains an Umbrel install  
Oct 16 13:26:13 umbrel external storage mounter[511]: Bind mounting external storage over local Umbrel installation…  
Oct 16 13:26:13 umbrel external storage mounter[511]: Bind mounting external storage over local Docker data dir…  
Oct 16 13:26:13 umbrel external storage mounter[511]: Bind mounting external storage to /swap  
Oct 16 13:26:13 umbrel external storage mounter[511]: Bind mounting SD card root at /sd-card…  
Oct 16 13:26:13 umbrel external storage mounter[511]: Checking Umbrel root is now on external storage…  
Oct 16 13:26:16 umbrel external storage mounter[511]: Checking /var/lib/docker is now on external storage…  
Oct 16 13:26:16 umbrel external storage mounter[511]: Checking /swap is now on external storage…  
Oct 16 13:26:16 umbrel external storage mounter[511]: Setting up swapfile  
Oct 16 13:26:16 umbrel external storage mounter[511]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)  
Oct 16 13:26:16 umbrel external storage mounter[511]: no label, UUID=20e42c6b-ff99-4c56-89fd-af9686450bfd  
Oct 16 13:26:16 umbrel external storage mounter[511]: Checking SD Card root is bind mounted at /sd-root…  
Oct 16 13:26:16 umbrel external storage mounter[511]: Starting external drive mount monitor…  
Oct 16 13:26:16 umbrel external storage mounter[511]: Mount script completed successfully!  
Oct 16 13:26:16 umbrel systemd[1]: Started External Storage Mounter.

## External storage SD card update service logs

– Logs begin at Mon 2023-10-16 13:25:49 UTC, end at Sun 2023-10-22 18:51:51 UTC. –  
Oct 22 18:41:47 umbrel systemd[1]: Starting External Storage SDcard Updater…  
Oct 22 18:41:47 umbrel external storage updater[2157]: Checking if SD card Umbrel is newer than external storage…  
Oct 22 18:41:47 umbrel external storage updater[2157]: No, SD version is not newer, exiting.  
Oct 22 18:41:47 umbrel systemd[1]: Started External Storage SDcard Updater.

## Karen logs

1+0 records in  
1+0 records out  
3895 bytes (3.9 kB, 3.8 KiB) copied, 0.000251405 s, 15.5 MB/s  
Creating encrypted tarball…  
backup/  
backup/.padding  
backup/channel.backup  
Uploading backup…  
% Total % Received % Xferd Average Speed Time Time Time Current  
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0curl: (6) Could not resolve host: [pvf3ozmmfl.execute-api.us-east-1.amazonaws.com](http://pvf3ozmmfl.execute-api.us-east-1.amazonaws.com)

# ============================= ====== Backup failed =======

Got signal: backup  
karen is getting triggered!  
Deriving keys…  
Creating backup…  
Adding random padding…  
1+0 records in  
1+0 records out  
7753 bytes (7.8 kB, 7.6 KiB) copied, 0.000365663 s, 21.2 MB/s  
Creating encrypted tarball…  
backup/  
backup/.padding  
backup/channel.backup  
Uploading backup…  
% Total % Received % Xferd Average Speed Time Time Time Current  
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0curl: (6) Could not resolve host: [pvf3ozmmfl.execute-api.us-east-1.amazonaws.com](http://pvf3ozmmfl.execute-api.us-east-1.amazonaws.com)

# ============================= ====== Backup failed =======

karen is running in /home/umbrel/umbrel/events  
Got signal:  
karen is getting triggered!  
Got signal:  
karen is getting triggered!  
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory  
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory  
Got signal: change-password  
karen is getting triggered!  
New password: Retype new password: passwd: password updated successfully  
Got signal: change-password  
karen is getting triggered!  
New password: Retype new password: passwd: password updated successfully  
Got signal: debug  
karen is getting triggered!

## Docker containers

NAMES STATUS  
electrs\_app\_1 Up 9 minutes  
bitcoin\_server\_1 Up 9 minutes  
bitcoin\_app\_proxy\_1 Up 9 minutes  
lightning-terminal\_web\_1 Up 9 minutes  
bitcoin\_tor\_server\_1 Up 9 minutes  
lightning-terminal\_app\_proxy\_1 Up 9 minutes  
lightning-terminal\_tor\_server\_1 Up 9 minutes  
bitcoin\_bitcoind\_1 Restarting (1) 56 seconds ago  
bitcoin\_i2pd\_daemon\_1 Up 9 minutes  
bitcoin\_tor\_1 Up 9 minutes  
electrs\_tor\_server\_1 Up 9 minutes  
electrs\_electrs\_1 Up 9 seconds  
electrs\_tor\_1 Up 9 minutes  
lightning\_tor\_server\_1 Up 9 minutes  
electrs\_app\_proxy\_1 Up 9 minutes  
lightning\_app\_1 Up 9 minutes  
lightning\_lnd\_1 Up 9 minutes  
lightning\_tor\_1 Up 9 minutes  
lightning\_app\_proxy\_1 Up 9 minutes  
mempool\_app\_proxy\_1 Up 9 minutes  
mempool\_tor\_server\_1 Up 9 minutes  
mempool\_api\_1 Up 6 seconds  
mempool\_mariadb\_1 Up 9 minutes  
mempool\_web\_1 Up 9 minutes  
snowflake\_web\_1 Up 9 minutes  
vaultwarden\_server\_1 Up 9 minutes (healthy)  
vaultwarden\_app\_proxy\_1 Up 9 minutes  
vaultwarden\_tor\_server\_1 Up 9 minutes  
snowflake\_proxy\_1 Up 9 minutes  
snowflake\_app\_proxy\_1 Up 9 minutes  
snowflake\_tor\_server\_1 Up 9 minutes  
nginx Up 9 minutes  
tor\_proxy Up 9 minutes  
dashboard Up 9 minutes  
auth Up 9 minutes  
tor\_server Up 9 minutes  
manager Up 9 minutes

## Umbrel logs

Attaching to manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:55 GMT] “GET /v1/system/storage HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:55 GMT] “GET /v1/system/temperature HTTP/1.0” 200 2 “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:55 GMT] “GET /v1/system/is-sd-card-failing HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:56 GMT] “GET /v1/system/info HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:56 GMT] “GET /v1/apps HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:56 GMT] “GET /v1/apps?installed=1 HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:56 GMT] “GET /v1/system/get-update HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:56 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:51:58 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager  
manager | ::ffff:10.21.21.2 - - [Sun, 22 Oct 2023 18:52:00 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
manager |  
manager | umbrel-manager

## Tor Proxy logs

Attaching to tor\_proxy  
tor\_proxy | Oct 22 18:42:14.000 [notice] Bootstrapped 55% (loading\_descriptors): Loading relay descriptors  
tor\_proxy | Oct 22 18:42:14.000 [notice] Bootstrapped 63% (loading\_descriptors): Loading relay descriptors  
tor\_proxy | Oct 22 18:42:15.000 [notice] Bootstrapped 71% (loading\_descriptors): Loading relay descriptors  
tor\_proxy | Oct 22 18:42:15.000 [notice] Bootstrapped 75% (enough\_dirinfo): Loaded enough directory info to build circuits  
tor\_proxy | Oct 22 18:42:15.000 [notice] Bootstrapped 80% (ap\_conn): Connecting to a relay to build circuits  
tor\_proxy | Oct 22 18:42:15.000 [notice] Bootstrapped 85% (ap\_conn\_done): Connected to a relay to build circuits  
tor\_proxy | Oct 22 18:42:15.000 [notice] Bootstrapped 89% (ap\_handshake): Finishing handshake with a relay to build circuits  
tor\_proxy | Oct 22 18:42:16.000 [notice] Bootstrapped 90% (ap\_handshake\_done): Handshake finished with a relay to build circuits  
tor\_proxy | Oct 22 18:42:16.000 [notice] Bootstrapped 95% (circuit\_create): Establishing a Tor circuit  
tor\_proxy | Oct 22 18:42:17.000 [notice] Bootstrapped 100% (done): Done

## App logs

bitcoin

Attaching to bitcoin\_server\_1, bitcoin\_app\_proxy\_1, bitcoin\_tor\_server\_1, bitcoin\_bitcoind\_1, bitcoin\_i2pd\_daemon\_1, bitcoin\_tor\_1  
bitcoind\_1 | Error: Settings file could not be read:  
bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json  
bitcoind\_1 | Error: Settings file could not be read:  
bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json  
bitcoind\_1 | Error: Settings file could not be read:  
bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json  
bitcoind\_1 | Error: Settings file could not be read:  
bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json  
bitcoind\_1 | Error: Settings file could not be read:  
bitcoind\_1 | - Unable to parse settings file /data/.bitcoin/settings.json  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t select next hop for phRQrMwNkNUgLF–HHwmmO~N8BByQ8RlcQkp5cH1WbI=  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t create outbound tunnel, no peers available  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t select next hop for phRQrMwNkNUgLF–HHwmmO~N8BByQ8RlcQkp5cH1WbI=  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t create outbound tunnel, no peers available  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t select next hop for QGWIAAybxcU~zps6YmGGNEklZNaf6CJn5PSrs~zfWkQ=  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t create inbound tunnel, no peers available  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t select next hop for xlo9a5ceiiK137Ypk3Pz25NiBVSI4–GX4D~JjMwphc=  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t create inbound tunnel, no peers available  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t select next hop for NA~k5oM21ZQBTI3TlsHX4CfNKKxqL6tqN9ORCJF5HTc=  
i2pd\_daemon\_1 | 18:51:54@858/error - Tunnels: Can’t create inbound tunnel, no peers available  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
app\_proxy\_1 | Validating token: 45b9749b58d6 …  
server\_1 | umbrel-middleware  
server\_1 | ::ffff:10.21.0.21 - - [Sun, 22 Oct 2023 18:51:46 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
server\_1 |  
server\_1 | umbrel-middleware  
server\_1 | ::ffff:10.21.0.21 - - [Sun, 22 Oct 2023 18:51:52 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
server\_1 |  
server\_1 | umbrel-middleware  
server\_1 | ::ffff:10.21.0.21 - - [Sun, 22 Oct 2023 18:52:04 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0”  
server\_1 |  
server\_1 | umbrel-middleware  
tor\_1 | Oct 22 18:43:17.000 [notice] Bootstrapped 60% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:18.000 [notice] Bootstrapped 66% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:18.000 [notice] Bootstrapped 71% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:20.000 [notice] Bootstrapped 75% (enough\_dirinfo): Loaded enough directory info to build circuits  
tor\_1 | Oct 22 18:43:20.000 [notice] Bootstrapped 80% (ap\_conn): Connecting to a relay to build circuits  
tor\_1 | Oct 22 18:43:20.000 [notice] Bootstrapped 85% (ap\_conn\_done): Connected to a relay to build circuits  
tor\_1 | Oct 22 18:43:20.000 [notice] Bootstrapped 89% (ap\_handshake): Finishing handshake with a relay to build circuits  
tor\_1 | Oct 22 18:43:21.000 [notice] Bootstrapped 90% (ap\_handshake\_done): Handshake finished with a relay to build circuits  
tor\_1 | Oct 22 18:43:21.000 [notice] Bootstrapped 95% (circuit\_create): Establishing a Tor circuit  
tor\_1 | Oct 22 18:43:21.000 [notice] Bootstrapped 100% (done): Done

electrs

Attaching to electrs\_app\_1, electrs\_tor\_server\_1, electrs\_electrs\_1, electrs\_tor\_1, electrs\_app\_proxy\_1  
electrs\_1 | [2023-10-22T18:52:01.906Z INFO electrs::db] closing DB at /data/db/bitcoin  
electrs\_1 | Error: electrs failed  
electrs\_1 |  
electrs\_1 | Caused by:  
electrs\_1 | 0: failed to open bitcoind cookie file: /data/.bitcoin/.cookie  
electrs\_1 | 1: No such file or directory (os error 2)  
electrs\_1 | Starting electrs 0.9.14 on aarch64 linux with Config { network: Bitcoin, db\_path: “/data/db/bitcoin”, daemon\_dir: “/data/.bitcoin”, daemon\_auth: CookieFile(“/data/.bitcoin/.cookie”), daemon\_rpc\_addr: 10.21.21.8:8332, daemon\_p2p\_addr: 10.21.21.8:8333, electrum\_rpc\_addr: 0.0.0.0:50001, monitoring\_addr: 127.0.0.1:4224, wait\_duration: 10s, jsonrpc\_timeout: 15s, index\_batch\_size: 10, index\_lookup\_limit: None, reindex\_last\_blocks: 0, auto\_reindex: true, ignore\_mempool: false, sync\_once: false, skip\_block\_download\_wait: false, disable\_electrum\_rpc: false, server\_banner: “Umbrel Electrs (0.9.14)”, signet\_magic: f9beb4d9, args: }  
app\_1 | \> umbrel-electrs@1.0.1 dev:backend  
app\_1 | \> npm run start -w umbrel-electrs-backend  
app\_1 |  
app\_1 |  
app\_1 | \> umbrel-electrs-backend@0.1.12 start  
app\_1 | \> node ./bin/www  
app\_1 |  
app\_1 | Sun, 22 Oct 2023 18:43:23 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:28:9  
app\_1 | Sun, 22 Oct 2023 18:43:23 GMT morgan deprecated default format: use combined format at app.js:28:9  
app\_1 | Listening on port 3006  
electrs\_1 | [2023-10-22T18:52:03.871Z INFO electrs::metrics::metrics\_impl] serving Prometheus metrics on 127.0.0.1:4224  
electrs\_1 | [2023-10-22T18:52:03.871Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001  
electrs\_1 | [2023-10-22T18:52:03.955Z INFO electrs::db] “/data/db/bitcoin”: 171 SST files, 41.249813719 GB, 5.170234361 Grows  
app\_proxy\_1 | yarn run v1.22.19  
app\_proxy\_1 | $ node ./bin/www  
app\_proxy\_1 | [HPM] Proxy created: / → [http://10.21.22.4:3006](http://10.21.22.4:3006)  
app\_proxy\_1 | Waiting for 10.21.22.4:3006 to open…  
app\_proxy\_1 | Electrs is now ready…  
app\_proxy\_1 | Listening on port: 2102  
tor\_1 | Oct 22 18:43:14.000 [notice] Bootstrapped 55% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:16.000 [notice] Bootstrapped 62% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:17.000 [notice] Bootstrapped 71% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:19.000 [notice] Bootstrapped 75% (enough\_dirinfo): Loaded enough directory info to build circuits  
tor\_1 | Oct 22 18:43:19.000 [notice] Bootstrapped 80% (ap\_conn): Connecting to a relay to build circuits  
tor\_1 | Oct 22 18:43:19.000 [notice] Bootstrapped 85% (ap\_conn\_done): Connected to a relay to build circuits  
tor\_1 | Oct 22 18:43:19.000 [notice] Bootstrapped 89% (ap\_handshake): Finishing handshake with a relay to build circuits  
tor\_1 | Oct 22 18:43:20.000 [notice] Bootstrapped 90% (ap\_handshake\_done): Handshake finished with a relay to build circuits  
tor\_1 | Oct 22 18:43:20.000 [notice] Bootstrapped 95% (circuit\_create): Establishing a Tor circuit  
tor\_1 | Oct 22 18:43:20.000 [notice] Bootstrapped 100% (done): Done

lightning

Attaching to lightning\_tor\_server\_1, lightning\_app\_1, lightning\_lnd\_1, lightning\_tor\_1, lightning\_app\_proxy\_1  
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  
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…  
lnd\_1 | 2023-10-22 18:50:38.538 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:50:38.555 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:50:59.613 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:50:59.632 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:51:21.869 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:51:21.897 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:51:46.953 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:51:46.980 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:52:11.754 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
lnd\_1 | 2023-10-22 18:52:11.774 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access  
app\_1 | Checking LND status…  
tor\_1 | Oct 22 18:43:12.000 [notice] Bootstrapped 57% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:14.000 [notice] Bootstrapped 62% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:14.000 [notice] Bootstrapped 71% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Oct 22 18:43:15.000 [notice] Bootstrapped 75% (enough\_dirinfo): Loaded enough directory info to build circuits  
tor\_1 | Oct 22 18:43:16.000 [notice] Bootstrapped 80% (ap\_conn): Connecting to a relay to build circuits  
tor\_1 | Oct 22 18:43:16.000 [notice] Bootstrapped 85% (ap\_conn\_done): Connected to a relay to build circuits  
tor\_1 | Oct 22 18:43:16.000 [notice] Bootstrapped 89% (ap\_handshake): Finishing handshake with a relay to build circuits  
tor\_1 | Oct 22 18:43:16.000 [notice] Bootstrapped 90% (ap\_handshake\_done): Handshake finished with a relay to build circuits  
tor\_1 | Oct 22 18:43:16.000 [notice] Bootstrapped 95% (circuit\_create): Establishing a Tor circuit  
tor\_1 | Oct 22 18:43:17.000 [notice] Bootstrapped 100% (done): Done

lightning-terminal

Attaching to lightning-terminal\_web\_1, lightning-terminal\_app\_proxy\_1, lightning-terminal\_tor\_server\_1  
app\_proxy\_1 | yarn run v1.22.19  
app\_proxy\_1 | $ node ./bin/www  
app\_proxy\_1 | [HPM] Proxy created: / → http://lightning-terminal\_web\_1:3004  
app\_proxy\_1 | Waiting for lightning-terminal\_web\_1:3004 to open…  
app\_proxy\_1 | Lightning Terminal is now ready…  
app\_proxy\_1 | Listening on port: 3004  
web\_1 | LiT Version 0.10.5-alpha commit=v0.10.5-alpha  
web\_1 | Web interface 127.0.0.1:8443, 0.0.0.0:3004 (open [https://127.0.0.1:8443](https://127.0.0.1:8443) or [http://localhost:3004](http://localhost:3004) in your browser)   
web\_1 | ----------------------------------------------------------  
web\_1 | 2023-10-22 18:42:52.426 [INF] LITD: Connecting basic lnd client  
web\_1 | 2023-10-22 18:42:52.630 [INF] LITD: Connecting full lnd client  
web\_1 | 2023-10-22 18:42:52.630 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009  
web\_1 | 2023-10-22 18:42:52.630 [INF] LNDC: Connected to lnd  
web\_1 | 2023-10-22 18:42:52.710 [INF] LNDC: Waiting for lnd to unlock  
web\_1 | 2023-10-22 18:42:52.863 [INF] LNDC: Wallet state of lnd is now: Lnd is waiting to start  
web\_1 | 2023-10-22 18:43:04.219 [INF] LNDC: Wallet state of lnd is now: Wallet is locked

mempool

Attaching to mempool\_app\_proxy\_1, mempool\_tor\_server\_1, mempool\_api\_1, mempool\_mariadb\_1, mempool\_web\_1  
mariadb\_1 | 2023-10-22 18:50:41 34 [Warning] Aborted connection 34 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets)  
mariadb\_1 | 2023-10-22 18:50:43 35 [Warning] Aborted connection 35 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication)  
mariadb\_1 | 2023-10-22 18:51:02 36 [Warning] Aborted connection 36 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets)  
mariadb\_1 | 2023-10-22 18:51:03 37 [Warning] Aborted connection 37 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication)  
mariadb\_1 | 2023-10-22 18:51:25 38 [Warning] Aborted connection 38 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets)  
mariadb\_1 | 2023-10-22 18:51:26 39 [Warning] Aborted connection 39 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication)  
mariadb\_1 | 2023-10-22 18:51:50 40 [Warning] Aborted connection 40 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets)  
mariadb\_1 | 2023-10-22 18:51:51 41 [Warning] Aborted connection 41 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication)  
mariadb\_1 | 2023-10-22 18:52:15 42 [Warning] Aborted connection 42 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets)  
mariadb\_1 | 2023-10-22 18:52:16 43 [Warning] Aborted connection 43 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication)  
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  
api\_1 | Error: connect EHOSTUNREACH 10.21.21.8:8332  
api\_1 | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16) {  
api\_1 | errno: -113,  
api\_1 | code: ‘EHOSTUNREACH’,  
api\_1 | syscall: ‘connect’,  
api\_1 | address: ‘10.21.21.8’,  
api\_1 | port: 8332  
api\_1 | }  
api\_1 | wait-for-it.sh: waiting 720 seconds for mariadb:3306  
api\_1 | wait-for-it.sh: mariadb:3306 is available after 0 seconds  
web\_1 | /var/www/mempool/browser/resources

snowflake

Attaching to snowflake\_web\_1, snowflake\_proxy\_1, snowflake\_app\_proxy\_1, snowflake\_tor\_server\_1  
proxy\_1 | 2023/10/22 18:42:22 snowflake-proxy 2.4.1  
proxy\_1 | 2023/10/22 18:42:22 Proxy starting  
proxy\_1 | 2023/10/22 18:42:22 WebRTC: Created offer  
proxy\_1 | 2023/10/22 18:42:22 WebRTC: Set local description  
proxy\_1 | 2023/10/22 18:42:27 Offer: {“type”:“offer”,“sdp”:“v=0\r\no=- 312483372449453396 1698000142 IN IP4 [scrubbed]\r\ns=-\r\nt=0 0\r\na=fingerprint:sha-256 17:03:9E:62:7F:34:3E:1F:3B:0D:53:7F:D3:DC:71:15:5E:E7:DD:25:08:F3:F6:C1:DF:69:9E:23:34:6F:1F:BD\r\na=extmap-allow-mixed\r\na=group:BUNDLE 0\r\nm=application 9 UDP/DTLS/SCTP webrtc-datachannel\r\nc=IN IP4 [scrubbed]\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=sctp-port:5000\r\na=ice-ufrag:gbyqQEzXMSHkwgZf\r\na=ice-pwd:qAoYwcucineUTJGNRSYGjVUwRrzLXoLX\r\na=candidate:935314439 1 udp 2130706431 [scrubbed] 35729 typ host\r\na=candidate:935314439 2 udp 2130706431 [scrubbed] 35729 typ host\r\na=end-of-candidates\r\n”}  
proxy\_1 | 2023/10/22 18:42:55 NAT Type measurement: unknown → restricted = restricted  
proxy\_1 | 2023/10/22 18:42:55 NAT type: restricted  
app\_proxy\_1 | yarn run v1.22.19  
web\_1 | 2023/10/22 18:42:26 Using index file at /snowflake/index.html  
web\_1 | 2023/10/22 18:42:27 Server is starting with command: bash -c tail -n 10000 -f /snowflake/snowflake.log | grep “Traffic Relayed”  
web\_1 | 2023/10/22 18:42:27 URL: [http://127.0.0.1:3800/](http://127.0.0.1:3800/)  
web\_1 | 2023/10/22 18:42:27 URL: [http://10.21.0.8:3800/](http://10.21.0.8:3800/)  
app\_proxy\_1 | $ node ./bin/www  
app\_proxy\_1 | [HPM] Proxy created: / → http://snowflake\_web\_1:3800  
app\_proxy\_1 | Waiting for snowflake\_web\_1:3800 to open…  
app\_proxy\_1 | Tor Snowflake Proxy is now ready…  
app\_proxy\_1 | Listening on port: 3800

vaultwarden

# Attaching to vaultwarden\_server\_1, vaultwarden\_app\_proxy\_1, vaultwarden\_tor\_server\_1 app\_proxy\_1 | yarn run v1.22.19 app\_proxy\_1 | $ node ./bin/www app\_proxy\_1 | [HPM] Proxy created: / → [http://10.21.21.46:8089](http://10.21.21.46:8089) app\_proxy\_1 | Waiting for 10.21.21.46:8089 to open… app\_proxy\_1 | Vaultwarden is now ready… app\_proxy\_1 | Listening on port: 8089 server\_1 | | official channels to report bugs/features, regardless of client. | server\_1 | | Send usage/configuration questions or feature requests to: | server\_1 | | [https://vaultwarden.discourse.group/](https://vaultwarden.discourse.group/) | server\_1 | | Report suspected bugs/issues in the software itself at: | server\_1 | | [Sign in to GitHub · GitHub](https://github.com/dani-garcia/vaultwarden/issues/new) | server\_1 | --------------------------------------------------------------------/ server\_1 | server\_1 | [INFO] No .env file found. server\_1 | server\_1 | [2023-10-22 18:42:27.385][start][INFO] Rocket has launched from [http://0.0.0.0:8089](http://0.0.0.0:8089)

# ==== Result ====

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

---

<div class="post-metadata">

**Author:** ![smolgrrr](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/smolgrrr/32/2825_2.png) [@smolgrrr](https://community.umbrel.com/u/smolgrrr)\
**Post date:** [October 23, 2023, 12:58pm UTC](https://community.umbrel.com/t/cannot-open-bitcoin-lightning-nodes/14014/2 "2023-10-23T12:58:07Z")

</div>

Hi can I ask what you have Umbrel set-up on? It almost seems like it is having trouble connecting to the internet outside of your local network.

Also please try the following:

> [@Official Umbrel Troubleshooting Guide and FAQ](https://community.umbrel.com/t/official-umbrel-troubleshooting-guide-and-faq/9873/1):
>
> If you check your debug logs you may have the following:
> 
> "`Error: Failed loading settings file:`
> 
> `bitcoind_1 | - Unable to parse settings file /data/.bitcoin/settings.json` "
> 
> To resolve, first connect to your Umbrel server by following the instructions in _How to SSH into umbrelOS on Umbrel Home or Rasberry Pi_ or by accessing a terminal on your Linux machine
> 
> This command is the quickest way to resolve the error, by deleting the file first:  
> `sudo rm ~/umbrel/app-data/bitcoin/data/bitcoin/settings.json` (replace `~/umbrel` with path to your umbrelOS installation directory if not on a Raspberry Pi or Umbrel Home).
> 
> Then you should restart Bitcoin:
> 
> `sudo ~/umbrel/scripts/app restart bitcoin`
> 
> Upon restarting, wait ~5 minutes and this will resolve the error with the settings.json file.

---

<div class="post-metadata">

**Author:** ![smolgrrr](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/smolgrrr/32/2825_2.png) [@smolgrrr](https://community.umbrel.com/u/smolgrrr)\
**Post date:** [October 23, 2023, 12:59pm UTC](https://community.umbrel.com/t/cannot-open-bitcoin-lightning-nodes/14014/3 "2023-10-23T12:59:29Z")

</div>

BTW if you have your seed phrase written down, there shouldn’t be any issue restoring this onto other wallet software in the meantime while we resolve this

---

<div class="post-metadata">

**Author:** ![sylvanscott](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sylvanscott](https://community.umbrel.com/u/sylvanscott)\
**Post date:** [October 24, 2023, 12:35pm UTC](https://community.umbrel.com/t/cannot-open-bitcoin-lightning-nodes/14014/4 "2023-10-24T12:35:42Z")

</div>

Thanks for your response. Below is software version, and my hardware device. I can access my node from anywhere, but it is not syncing. Both BTC and LND nodes are not accessible. I wrote down the 8-word seed phrase a couple years ago. What type of BTC wallet is recommended to restore my old wallet?

## Umbrel version

0.5.4

## Flashed OS version

v0.5.4-patch-1

## Raspberry Pi Model

Revision : d03114  
Serial : 1000000064f19306  
Model : Raspberry Pi 4 Model B Rev 1.4

---

<div class="post-metadata">

**Author:** ![sylvanscott](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sylvanscott](https://community.umbrel.com/u/sylvanscott)\
**Post date:** [October 31, 2023, 12:14pm UTC](https://community.umbrel.com/t/cannot-open-bitcoin-lightning-nodes/14014/5 "2023-10-31T12:14:42Z")

</div>

The above commands worked. I was able to access my wallets after 6 months of being locked out.  
Thank you!

---

<div class="post-metadata">

**Author:** ![brianoflondon](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/brianoflondon/32/1595_2.png) [@brianoflondon](https://community.umbrel.com/u/brianoflondon)\
**Post date:** [April 7, 2024, 8:02am UTC](https://community.umbrel.com/t/cannot-open-bitcoin-lightning-nodes/14014/6 "2024-04-07T08:02:30Z")

</div>

Thanks this seemed to solve my issue.

For some reason the `~/umbrel/app-data/bitcoin/data/bitcoin/settings.json` file was empty but present.

Removing it and restarting all the containers worked (I’m still catching up a day’s worth of missed blocks).
