# Recovering Bitcoin Node funds **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [July 1, 2023, 6:31pm UTC](https://community.umbrel.com/t/recovering-bitcoin-node-funds/12944 "2023-07-01T18:31:11Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![sylvanscott](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sylvanscott](https://community.umbrel.com/u/sylvanscott)\ **Post date:** [July 1, 2023, 6:31pm UTC](https://community.umbrel.com/t/recovering-bitcoin-node-funds/12944/1 "2023-07-01T18:31:11Z")
it seems my Rasp Pi is no longer working. Home network says it hasn’t connected in over 24 hours. I cannot connect using SSH. I have an on-chain balance in my bitcoin node wallet. I don’t remember ever being prompted for a recovery phrase for the wallet. I do have an Umbrel node recovery phrase, but I’m assuming I cannot create a new wallet using that seed phrase. Can anyone let me know how to recover funds from my bitcoin node wallet? or maybe try to fire up my Node again? The lights are on, the fan is running, but I cannot connect to it! thanks ---
**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 1, 2023, 7:52pm UTC](https://community.umbrel.com/t/recovering-bitcoin-node-funds/12944/2 "2023-07-01T19:52:08Z")
Hey! If we can SSH you can grab your seed phrase with this command: `sudo nano ~/umbrel/app-data/lightning/data/lightning/state.json` If you can’t access the Pi 4 firstly we’ll need to make sure the green light is flashing next to the red power on light, if it’s not follow steps here to reflash: [https://umbrel.com/#start](https://umbrel.com/#start) Then let me know what else you’ve tried, we can likely get you connected - during this time avoid reformatting the drive we can likely at least grab the seed phrase off of it just in case Do you remember when you had updated last? In the earlier versions the wallet was in Bitcoin Node and it’s moved to Lightning Node app for your LND Recovery Phrase, if you have this we can also likely perform an Automated Recovery if necesssary by entering it in after installing this is how that process looks [demonstrated here](https://twitter.com/umbrel/status/1562099972547690501) Feel free to post in the [Help and Support channel](https://t.me/getumbrel/207765) on Telegram Or can [reach out to me directly too](https://t.me/usernameisJim) and I can assist you get up and running and recover easer in real-time ---
**Author:** ![sylvanscott](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sylvanscott](https://community.umbrel.com/u/sylvanscott)\ **Post date:** [July 1, 2023, 8:11pm UTC](https://community.umbrel.com/t/recovering-bitcoin-node-funds/12944/3 "2023-07-01T20:11:00Z")
Hi Jim. Thanks for your time. I had updated to the latest umbrel version. There is no green light like there normally is. Just a solid red light. I will try to SSH in again. JH ---
**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 1, 2023, 8:19pm UTC](https://community.umbrel.com/t/recovering-bitcoin-node-funds/12944/4 "2023-07-01T20:19:53Z")
Gotchya, you won’t be able to SSH if there is no green light so definitely should reflash the MicroSD card again let me know how it goes! Got my [Telegram here too whenever](https://t.me/usernameisJim) or you can [Twitter](https://twitter.com/usernameisJim) DM me or the [official Umbrel](https://twitter.com/Umbrel) account too if that’s easier for you to message immediatley instead of post on forum ---
**Author:** ![sylvanscott](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sylvanscott](https://community.umbrel.com/u/sylvanscott)\ **Post date:** [July 3, 2023, 9:08pm UTC](https://community.umbrel.com/t/recovering-bitcoin-node-funds/12944/5 "2023-07-03T21:08:29Z")
reflashed microSD. umbrel is now appearing on my laptop again, but both bitcoin node & lightning node apps will not open. It seems like they’re about to open but they just will not sync ---
**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 10, 2023, 3:00am UTC](https://community.umbrel.com/t/recovering-bitcoin-node-funds/12944/6 "2023-07-10T03:00:24Z")
Could you share a debug log? For reference check out FAQ under “Generating Troubleshooting Logs” here: [Official Umbrel Troubleshooting Guide and FAQ - Guides - Umbrel Community](https://community.getumbrel.com/t/official-umbrel-troubleshooting-guide-and-faq/9873) You can also just use the interface as the article describes via going System \> Troubleshoot \> Start and it will generate it from you right there within the dashboard and download it, then you can share it from [www.pastebin.com](http://www.pastebin.com) and paste a link If for any reason you are unable to generate from the UI You can SSH via the steps from “How to SSH” for reference in the guide and copy the output of this command for the log: `sudo ~/umbrel/scripts/debug` ---
**Author:** ![sylvanscott](https://avatars.discourse-cdn.com/v4/letter/s/5fc32e/32.png) [@sylvanscott](https://community.umbrel.com/u/sylvanscott)\ **Post date:** [July 16, 2023, 7:55pm UTC](https://community.umbrel.com/t/recovering-bitcoin-node-funds/12944/7 "2023-07-16T19:55:10Z")
# ===================== = Umbrel debug info = ## Umbrel version 0.5.4 ## Flashed OS version v0.5.4 ## Raspberry Pi Model Revision : d03114 Serial : 1000000064f19306 Model : Raspberry Pi 4 Model B Rev 1.4 ## Firmware May 9 2023 12:16:34 Copyright (c) 2012 Broadcom version 30aa0d70ab280427ba04ebc718c81d4350b9d394 (clean) (release) (start) ## Temperature temp=54.0’C ## Throttling throttled=0x0 ## Memory usage ``` total used free shared buff/cache available ``` Mem: 7.8G 4.7G 1.0G 377M 2.1G 2.6G Swap: 4.1G 3.1G 955M total: 60.1% system: 35.6% mempool: 10.2% lightning: 5% electrs: 4.4% lightning-terminal: 2.3% bitcoin: 1.4% vaultwarden: 0.6% snowflake: 0.6% ## Memory monitor logs 2022-10-13 17:33:38 Warning memory usage at 95% 2022-12-12 22:07:07 Memory monitor running! 2022-12-12 22:15:17 Memory monitor running! 2022-12-27 18:33:41 Memory monitor running! 2023-04-10 00:13:42 Memory monitor running! 3058 ? S 2:57 bash ./scripts/memory-monitor Memory monitor is already running 2023-06-21 23:07:51 Memory monitor running! 2023-07-03 20:39:27 Memory monitor running! 2023-07-03 21:34:28 Memory monitor running! ## Filesystem information Filesystem Size Used Avail Use% Mounted on /dev/root 30G 4.2G 24G 15% / /dev/sda1 916G 624G 246G 72% /home/umbrel/umbrel ## Startup service logs – Logs begin at Sat 2023-07-15 12:47:36 UTC, end at Sun 2023-07-16 19:47:09 UTC. – Jul 16 19:39:16 umbrel passwd[26679]: pam\_unix(passwd:chauthtok): password changed for umbrel Jul 16 19:42:21 umbrel passwd[6165]: pam\_unix(passwd:chauthtok): password changed for umbrel Jul 16 19:44:50 umbrel passwd[15351]: pam\_unix(passwd:chauthtok): password changed for umbrel Jul 16 19:45:33 umbrel passwd[17715]: pam\_unix(passwd:chauthtok): password changed for umbrel ## External storage service logs – Logs begin at Sat 2023-07-15 12:47:36 UTC, end at Sun 2023-07-16 19:47:09 UTC. – – No entries – ## External storage SD card update service logs – Logs begin at Sat 2023-07-15 12:47:36 UTC, end at Sun 2023-07-16 19:47:09 UTC. – – No entries – ## Karen logs Pulling electrs … digest: sha256:f215ca7163a3bd42ae… Pulling electrs … status: downloaded newer image fo… Pulling electrs … done Starting app electrs… Executing hook: /home/umbrel/umbrel/app-data/electrs/hooks/pre-start Creating lightning-terminal\_web\_1 … Creating lightning-terminal\_app\_proxy\_1 … Creating lightning-terminal\_tor\_server\_1 … Creating electrs\_tor\_server\_1 … Creating electrs\_electrs\_1 … Creating lightning-terminal\_web\_1 … done Creating electrs\_tor\_1 … Creating electrs\_app\_proxy\_1 … Creating lightning-terminal\_app\_proxy\_1 … done Creating lightning-terminal\_tor\_server\_1 … done Creating electrs\_app\_proxy\_1 … done Creating electrs\_tor\_server\_1 … done Creating electrs\_tor\_1 … done Creating electrs\_electrs\_1 … done Creating electrs\_app\_1 … Untagged: lightninglabs/lightning-terminal:v0.10.1-alpha@sha256:3e25ececbb127f975d414f2a81506fe688046cd26bf548112bb1e232e1d571eb Deleted: sha256:816e3aeeb2ee57880e9a2f36d54757bd89946f9a537626cac94935736d72dbb9 Deleted: sha256:daaf0586334b57506ad69b76ef08f740606e9c53e14fd9087c90014b034c48c9 Deleted: sha256:20fb77a24f2a67399ce611022fd8d124dcb0400c60851e04a540f3d41ebc54aa Deleted: sha256:8042a75a44410518b3bb92fe99af49d6fccd37ccbe31410e1e1dfcc9f439e758 Deleted: sha256:80f1ad73a4cf6c326681565bbdbce05f1c341990d32115d45eb9e6138168f2ef Deleted: sha256:ca97ebba28d98071cff17f8feb479d72c70537de7710d8b072497efe5c80cb67 Deleted: sha256:fb773fc8954a2e1bd684f8049a4709d9990c1f9dcd034fa33f9ac722eed314ee Deleted: sha256:233a6547564ce5b4b522a527c3842bf4c29e4610fbc8d787bbc389e4aaf4cc02 Deleted: sha256:cc21d797dac5d2385f360a2e400ac453c99b99c3b2bbd2700e6123ee76d3b44b Creating electrs\_app\_1 … done Untagged: getumbrel/electrs:v0.9.10@sha256:7b64bf93f2137fcd040fc512a302abda17dd1b4cad8181a14fa34c15361f1334 Deleted: sha256:c2ef36de8eaa79c8e4269b1447f21f49ecbf5b444ee73cfb8a3aeabf5ac3386e Deleted: sha256:8247e8eac8cd9151d0e41312f52e960c2b2d512f361c79c5f5eea1a145e58308 Deleted: sha256:a39fda8bc72e57708a9953011324d9e6065ca645947f138cc49d0d7cb1d3e419 Deleted: sha256:700a2417b36bd0fab057070338f607fa5b7a7fe709868b05ac6571aaf652ddd7 Deleted: sha256:d862f0dab9f3f61f6a8a8084b6fbfd852a2fa5a57e72fc5b10a024a87dbbb90c Error response from daemon: conflict: unable to remove repository reference “getumbrel/umbrel-electrs:v1.0.2@sha256:3dae686b22b1fdfd72ff058d022045f96cc5116e76f82f435d58f1cfe8f46418” (must force) - container e306e3d6f85a is using its referenced image 07d2927cee6f Error response from daemon: conflict: unable to remove repository reference “getumbrel/tor:0.4.7.8@sha256:2ace83f22501f58857fa9b403009f595137fa2e7986c4fda79d82a8119072b6a” (must force) - container 3c36d74e486f is using its referenced image 105438dd043f Got signal: change-password karen is getting triggered! New password: Retype new password: passwd: password updated successfully Got signal: change-password karen is getting triggered! New password: Retype new password: passwd: password updated successfully Got signal: change-password karen is getting triggered! New password: Retype new password: passwd: password updated successfully Got signal: debug karen is getting triggered! ## Docker containers NAMES STATUS electrs\_app\_1 Up 6 minutes electrs\_electrs\_1 Up 12 seconds electrs\_tor\_1 Up 6 minutes electrs\_app\_proxy\_1 Up 6 minutes electrs\_tor\_server\_1 Up 6 minutes lightning-terminal\_tor\_server\_1 Up 6 minutes lightning-terminal\_app\_proxy\_1 Up 6 minutes lightning-terminal\_web\_1 Up 6 minutes lightning\_tor\_1 Up 6 minutes lightning\_app\_1 Up 6 minutes lightning\_tor\_server\_1 Up 6 minutes lightning\_app\_proxy\_1 Up 6 minutes lightning\_lnd\_1 Up 6 minutes bitcoin\_server\_1 Up 12 days snowflake\_tor\_server\_1 Up 12 days snowflake\_web\_1 Up 12 days snowflake\_proxy\_1 Up 12 days snowflake\_app\_proxy\_1 Up 12 days bitcoin\_i2pd\_daemon\_1 Up 12 days bitcoin\_bitcoind\_1 Restarting (1) 29 seconds ago bitcoin\_tor\_server\_1 Up 12 days bitcoin\_tor\_1 Up 12 days bitcoin\_app\_proxy\_1 Up 12 days vaultwarden\_server\_1 Up 12 days (healthy) vaultwarden\_tor\_server\_1 Up 12 days vaultwarden\_app\_proxy\_1 Up 12 days mempool\_app\_proxy\_1 Up 12 days mempool\_tor\_server\_1 Up 12 days mempool\_web\_1 Up 12 days mempool\_api\_1 Up 10 seconds mempool\_mariadb\_1 Up 12 days nginx Up 12 days tor\_proxy Up 12 days auth Up 12 days tor\_server Up 12 days manager Up 12 days dashboard Up 12 days ## Umbrel logs Attaching to manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:08 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:10 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:12 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:13 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:15 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:17 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:17 GMT] “GET /v1/system/update-status HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:18 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:20 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Sun, 16 Jul 2023 19:47:22 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” manager | manager | umbrel-manager ## Tor Proxy logs Attaching to tor\_proxy tor\_proxy | Jul 16 03:34:50.000 [notice] While bootstrapping, fetched this many bytes: 632173 (consensus network-status fetch); 14101 (authority cert fetch); 8540696 (microdescriptor fetch) tor\_proxy | Jul 16 03:34:50.000 [notice] While not bootstrapping, fetched this many bytes: 13954349 (consensus network-status fetch); 104724 (authority cert fetch); 14203559 (microdescriptor fetch) tor\_proxy | Jul 16 05:09:48.000 [notice] Application request when we haven’t used client functionality lately. Optimistically trying directory fetches again. tor\_proxy | Jul 16 09:34:50.000 [notice] Heartbeat: Tor’s uptime is 12 days 12:00 hours, with 0 circuits open. I’ve sent 13.17 MB and received 50.75 MB. I’ve received 46 connections on IPv4 and 0 on IPv6. I’ve made 337 connections with IPv4 and 0 with IPv6. tor\_proxy | Jul 16 09:34:50.000 [notice] While bootstrapping, fetched this many bytes: 632173 (consensus network-status fetch); 14101 (authority cert fetch); 8540696 (microdescriptor fetch) tor\_proxy | Jul 16 09:34:50.000 [notice] While not bootstrapping, fetched this many bytes: 14106791 (consensus network-status fetch); 104724 (authority cert fetch); 14905963 (microdescriptor fetch) tor\_proxy | Jul 16 15:34:50.000 [notice] Heartbeat: Tor’s uptime is 12 days 18:00 hours, with 0 circuits open. I’ve sent 13.63 MB and received 51.44 MB. I’ve received 48 connections on IPv4 and 0 on IPv6. I’ve made 346 connections with IPv4 and 0 with IPv6. tor\_proxy | Jul 16 15:34:50.000 [notice] While bootstrapping, fetched this many bytes: 632173 (consensus network-status fetch); 14101 (authority cert fetch); 8540696 (microdescriptor fetch) tor\_proxy | Jul 16 15:34:50.000 [notice] While not bootstrapping, fetched this many bytes: 14255646 (consensus network-status fetch); 106497 (authority cert fetch); 14993972 (microdescriptor fetch) tor\_proxy | Jul 16 18:28:53.000 [warn] Received http status code 404 (“Not found”) from server 23.132.184.67:9000 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”. ## App logs bitcoin Attaching to bitcoin\_server\_1, bitcoin\_i2pd\_daemon\_1, bitcoin\_bitcoind\_1, bitcoin\_tor\_server\_1, bitcoin\_tor\_1, bitcoin\_app\_proxy\_1 app\_proxy\_1 | Validating token: 46738f46ef90 … app\_proxy\_1 | Validating token: 46738f46ef90 … app\_proxy\_1 | Validating token: 46738f46ef90 … app\_proxy\_1 | Validating token: 46738f46ef90 … i2pd\_daemon\_1 | 19:17:43@67/error - SSU2: RelayIntro unknown router to introduce i2pd\_daemon\_1 | 19:18:36@714/error - Tunnel: Tunnel with id 3615583273 already exists i2pd\_daemon\_1 | 19:28:33@634/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 19:41:01@145/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 19:41:09@634/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 19:42:36@634/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 19:42:37@634/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 19:43:22@145/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message i2pd\_daemon\_1 | 19:44:45@714/error - Tunnels: Can’t select next hop for rwDV9CuQgrybnSqujEi5jPfFDLrErhFJORD0y4AKhNY= i2pd\_daemon\_1 | 19:44:45@714/error - Tunnels: Can’t create inbound tunnel, no peers available app\_proxy\_1 | Validating token: 46738f46ef90 … app\_proxy\_1 | Validating token: 46738f46ef90 … app\_proxy\_1 | Validating token: 46738f46ef90 … app\_proxy\_1 | Validating token: 46738f46ef90 … app\_proxy\_1 | Validating token: 46738f46ef90 … app\_proxy\_1 | Validating token: 46738f46ef90 … tor\_1 | Jul 16 10:09:34.000 [warn] Received http status code 404 (“Not found”) from server 162.55.91.19:443 while fetching “/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97”. tor\_1 | Jul 16 10:10:39.000 [notice] No circuits are opened. Relaxed timeout for circuit 17688 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [5 similar message(s) suppressed in last 22380 seconds] tor\_1 | Jul 16 12:36:39.000 [notice] No circuits are opened. Relaxed timeout for circuit 17835 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 8760 seconds] tor\_1 | Jul 16 13:56:39.000 [notice] No circuits are opened. Relaxed timeout for circuit 17886 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 4800 seconds] tor\_1 | Jul 16 15:35:15.000 [notice] Heartbeat: Tor’s uptime is 12 days 18:00 hours, with 15 circuits open. I’ve sent 250.81 MB and received 214.50 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 156 connections with IPv4 and 0 with IPv6. tor\_1 | Jul 16 15:35:15.000 [notice] While bootstrapping, fetched this many bytes: 632173 (consensus network-status fetch); 14354 (authority cert fetch); 8540890 (microdescriptor fetch) tor\_1 | Jul 16 15:35:15.000 [notice] While not bootstrapping, fetched this many bytes: 8237231 (consensus network-status fetch); 61668 (authority cert fetch); 15694621 (microdescriptor fetch) tor\_1 | Jul 16 17:49:41.000 [notice] No circuits are opened. Relaxed timeout for circuit 18075 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 14040 seconds] tor\_1 | Jul 16 18:59:46.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes. server\_1 | umbrel-middleware server\_1 | ::ffff:10.21.0.10 - - [Sun, 16 Jul 2023 19:44:20 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” server\_1 | server\_1 | umbrel-middleware server\_1 | ::ffff:10.21.0.10 - - [Sun, 16 Jul 2023 19:44:26 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” server\_1 | server\_1 | umbrel-middleware server\_1 | ::ffff:10.21.0.10 - - [Sun, 16 Jul 2023 19:44:29 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” server\_1 | server\_1 | umbrel-middleware 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 electrs Attaching to electrs\_app\_1, electrs\_electrs\_1, electrs\_tor\_1, electrs\_app\_proxy\_1, electrs\_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.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 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, 16 Jul 2023 19:41:12 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:28:9 app\_1 | Sun, 16 Jul 2023 19:41:12 GMT morgan deprecated default format: use combined format at app.js:28:9 app\_1 | Listening on port 3006 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.10)”, signet\_magic: f9beb4d9, args: } electrs\_1 | [2023-07-16T19:47:22.566Z INFO electrs::metrics::metrics\_impl] serving Prometheus metrics on 127.0.0.1:4224 electrs\_1 | [2023-07-16T19:47:22.566Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001 electrs\_1 | [2023-07-16T19:47:22.666Z INFO electrs::db] “/data/db/bitcoin”: 171 SST files, 41.249792485 GB, 5.170234359 Grows electrs\_1 | [2023-07-16T19:47:29.664Z INFO electrs::chain] loading 795233 headers, tip=000000000000000000008e4cdb0d268b551dee70ba944b8cc57c4c3e13120da4 tor\_1 | Jul 16 19:41:05.000 [notice] Bootstrapped 56% (loading\_descriptors): Loading relay descriptors tor\_1 | Jul 16 19:41:07.000 [notice] Bootstrapped 64% (loading\_descriptors): Loading relay descriptors tor\_1 | Jul 16 19:41:08.000 [notice] Bootstrapped 69% (loading\_descriptors): Loading relay descriptors tor\_1 | Jul 16 19:41:08.000 [notice] Bootstrapped 75% (enough\_dirinfo): Loaded enough directory info to build circuits tor\_1 | Jul 16 19:41:09.000 [notice] Bootstrapped 80% (ap\_conn): Connecting to a relay to build circuits tor\_1 | Jul 16 19:41:09.000 [notice] Bootstrapped 85% (ap\_conn\_done): Connected to a relay to build circuits tor\_1 | Jul 16 19:41:09.000 [notice] Bootstrapped 89% (ap\_handshake): Finishing handshake with a relay to build circuits tor\_1 | Jul 16 19:41:09.000 [notice] Bootstrapped 90% (ap\_handshake\_done): Handshake finished with a relay to build circuits tor\_1 | Jul 16 19:41:09.000 [notice] Bootstrapped 95% (circuit\_create): Establishing a Tor circuit tor\_1 | Jul 16 19:41:09.000 [notice] Bootstrapped 100% (done): Done lightning Attaching to lightning\_tor\_1, lightning\_app\_1, lightning\_tor\_server\_1, lightning\_app\_proxy\_1, lightning\_lnd\_1 app\_1 | ::ffff:10.21.0.5 - - [Sun, 16 Jul 2023 19:45:47 GMT] “GET /v1/lnd/info/status HTTP/1.1” 200 38 “-” “Mozilla/5.0 (Windows NT 10.0; rv:102.0) Gecko/20100101 Firefox/102.0” app\_1 | app\_1 | umbrel-lightning app\_1 | Checking LND status… app\_1 | Waiting for LND… app\_1 | Checking LND status… app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_proxy\_1 | Validating token: 4cbe604eb47c … app\_1 | [backup-monitor] Checking channel backup… app\_1 | [backup-monitor] Sleeping… app\_1 | [backup-monitor] Checking channel backup… app\_1 | [backup-monitor] Sleeping… app\_proxy\_1 | Validating token: 4cbe604eb47c … tor\_1 | Jul 16 19:40:51.000 [notice] Bootstrapped 57% (loading\_descriptors): Loading relay descriptors tor\_1 | Jul 16 19:40:52.000 [notice] Bootstrapped 64% (loading\_descriptors): Loading relay descriptors tor\_1 | Jul 16 19:40:53.000 [notice] Bootstrapped 69% (loading\_descriptors): Loading relay descriptors tor\_1 | Jul 16 19:40:53.000 [notice] Bootstrapped 75% (enough\_dirinfo): Loaded enough directory info to build circuits tor\_1 | Jul 16 19:40:54.000 [notice] Bootstrapped 80% (ap\_conn): Connecting to a relay to build circuits tor\_1 | Jul 16 19:40:54.000 [notice] Bootstrapped 85% (ap\_conn\_done): Connected to a relay to build circuits tor\_1 | Jul 16 19:40:55.000 [notice] Bootstrapped 89% (ap\_handshake): Finishing handshake with a relay to build circuits tor\_1 | Jul 16 19:40:55.000 [notice] Bootstrapped 90% (ap\_handshake\_done): Handshake finished with a relay to build circuits tor\_1 | Jul 16 19:40:55.000 [notice] Bootstrapped 95% (circuit\_create): Establishing a Tor circuit tor\_1 | Jul 16 19:40:55.000 [notice] Bootstrapped 100% (done): Done lnd\_1 | 2023-07-16 19:45:57.204 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:45:57.219 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:46:18.187 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:46:18.206 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:46:38.789 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:46:38.809 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:47:04.482 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:47:04.532 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:47:31.586 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lnd\_1 | 2023-07-16 19:47:31.615 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access lightning-terminal Attaching to lightning-terminal\_tor\_server\_1, lightning-terminal\_app\_proxy\_1, lightning-terminal\_web\_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.2-alpha commit=v0.10.2-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-07-16 19:40:47.575 [INF] LITD: Connecting basic lnd client web\_1 | 2023-07-16 19:40:47.778 [INF] LITD: Connecting full lnd client web\_1 | 2023-07-16 19:40:47.778 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009 web\_1 | 2023-07-16 19:40:47.779 [INF] LNDC: Connected to lnd web\_1 | 2023-07-16 19:40:47.804 [INF] LNDC: Waiting for lnd to unlock web\_1 | 2023-07-16 19:40:47.828 [INF] LNDC: Wallet state of lnd is now: Lnd is waiting to start web\_1 | 2023-07-16 19:40:53.727 [INF] LNDC: Wallet state of lnd is now: Wallet is locked mempool Attaching to mempool\_app\_proxy\_1, mempool\_tor\_server\_1, mempool\_web\_1, mempool\_api\_1, mempool\_mariadb\_1 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 api\_1 | Jul 16 19:47:39 [110] NOTICE: Starting Mempool Server… (57eddac) web\_1 | /var/www/mempool/browser/resources mariadb\_1 | 2023-07-16 19:46:00 93535 [Warning] Aborted connection 93535 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets) mariadb\_1 | 2023-07-16 19:46:01 93536 [Warning] Aborted connection 93536 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication) mariadb\_1 | 2023-07-16 19:46:21 93537 [Warning] Aborted connection 93537 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets) mariadb\_1 | 2023-07-16 19:46:22 93538 [Warning] Aborted connection 93538 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication) mariadb\_1 | 2023-07-16 19:46:42 93539 [Warning] Aborted connection 93539 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets) mariadb\_1 | 2023-07-16 19:46:43 93540 [Warning] Aborted connection 93540 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication) mariadb\_1 | 2023-07-16 19:47:08 93541 [Warning] Aborted connection 93541 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets) mariadb\_1 | 2023-07-16 19:47:09 93542 [Warning] Aborted connection 93542 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication) mariadb\_1 | 2023-07-16 19:47:35 93543 [Warning] Aborted connection 93543 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got an error reading communication packets) mariadb\_1 | 2023-07-16 19:47:36 93544 [Warning] Aborted connection 93544 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication) app\_proxy\_1 | [HPM] Client disconnected app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] Upgrading to WebSocket snowflake Attaching to snowflake\_tor\_server\_1, snowflake\_web\_1, snowflake\_proxy\_1, snowflake\_app\_proxy\_1 proxy\_1 | 2023/07/16 19:42:25 Generating answer… proxy\_1 | 2023/07/16 19:42:51 Timed out waiting for client to open data channel. proxy\_1 | 2023/07/16 19:43:21 sdp offer successfully received. proxy\_1 | 2023/07/16 19:43:21 Generating answer… proxy\_1 | 2023/07/16 19:43:46 Timed out waiting for client to open data channel. proxy\_1 | 2023/07/16 19:44:57 sdp offer successfully received. proxy\_1 | 2023/07/16 19:44:57 Generating answer… proxy\_1 | 2023/07/16 19:45:23 Timed out waiting for client to open data channel. proxy\_1 | 2023/07/16 19:47:25 sdp offer successfully received. proxy\_1 | 2023/07/16 19:47:25 Generating answer… app\_proxy\_1 | yarn run v1.22.19 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 web\_1 | 2023/07/03 21:35:17 Using index file at /snowflake/index.html web\_1 | 2023/07/03 21:35:17 Server is starting with command: bash -c tail -n 10000 -f /snowflake/snowflake.log | grep “Traffic Relayed” web\_1 | 2023/07/03 21:35:17 URL: [http://127.0.0.1:3800/](http://127.0.0.1:3800/) web\_1 | 2023/07/03 21:35:17 URL: [http://10.21.0.20:3800/](http://10.21.0.20:3800/) vaultwarden # Attaching to vaultwarden\_server\_1, vaultwarden\_tor\_server\_1, vaultwarden\_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.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-07-03 21:35:12.009][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.