Node Stuck at Syncing w/ 1 peer for 6 days - RPI4 w/ Ethernet connection- and flashed and updated sd card

Stuck at 99.48% as of 5 days ago and now at 99.32% as blocks keep churning.
Synchronized 99.32% (709,493 of 711,883 blocks)
Restarted Node.
Followed the troubleshooting guide and was able to run the log below, but being blue in looking the log, I havent been able to properly the diagnose the issue.
Please help

I couldn’t upload the entire debug log :
https://drive.google.com/file/d/1ZudOivFEWWmOKr4g-66JUFnIisevHRxI/view?usp=sharing

Any ideas and suggestions appreciated, even if its starting from the begining which I hope is not the only option.

= Umbrel debug info =

Umbrel version

0.4.9

Flashed OS version

v0.4.9

Raspberry Pi Model

Revision : c03112
Serial : 10000000c7d06976
Model : Raspberry Pi 4 Model B Rev 1.2

Firmware

Oct 29 2021 10:47:33
Copyright © 2012 Broadcom
version b8a114e5a9877e91ca8f26d1a5ce904b2ad3cf13 (clean) (release) (start)

Temperature

temp=46.7’C

Docker containers

NAMES STATUS
btc-rpc-explorer_web_1 Up 28 hours
specter-desktop_web_1 Up 28 hours
middleware Up 28 hours
bitcoin Up 6 seconds
nginx Up 28 hours
lnd Up 28 hours
manager Up 28 hours
dashboard Up 28 hours
electrs Up 29 seconds
umbrel_app_tor_1 Up 28 hours
umbrel_app_3_tor_1 Up 28 hours
umbrel_app_2_tor_1 Up 28 hours
tor Up 28 hours

Umbrel logs

middleware | umbrel-middleware
middleware | LndUnlocker: Wallet failed to unlock!
manager |
manager | umbrel-manager

Bitcoin Core logs

Attaching to bitcoin
bitcoin | 2021-12-05T16:59:32Z Using at most 125 automatic connections (1048576 file descriptors available)
bitcoin | 2021-12-05T16:59:33Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
bitcoin | 2021-12-05T16:59:33Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
bitcoin | 2021-12-05T16:59:33Z Script verification uses 3 additional threads
bitcoin | 2021-12-05T16:59:33Z scheduler thread start
bitcoin | 2021-12-05T16:59:33Z HTTP: creating work queue of depth 64
bitcoin | 2021-12-05T16:59:33Z Using random cookie authentication.
bitcoin | 2021-12-05T16:59:33Z Generated RPC authentication cookie /data/.bitcoin/.cookie
bitcoin | 2021-12-05T16:59:33Z Using rpcauth authentication.
bitcoin | 2021-12-05T16:59:33Z HTTP: starting 4 worker threads
bitcoin | 2021-12-05T16:59:33Z Using wallet directory /data/.bitcoin
bitcoin | 2021-12-05T16:59:33Z init message: Verifying wallet(s)…
bitcoin | 2021-12-05T16:59:33Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
bitcoin | 2021-12-05T16:59:33Z Using wallet /data/.bitcoin/wallet.dat
bitcoin | 2021-12-05T16:59:33Z BerkeleyEnvironment::Open: LogDir=/data/.bitcoin/database ErrorFile=/data/.bitcoin/db.log
bitcoin | 2021-12-05T16:59:33Z init message: Loading banlist…
bitcoin | 2021-12-05T16:59:33Z SetNetworkActive: true
bitcoin | 2021-12-05T16:59:33Z Using /16 prefix for IP bucketing
bitcoin | 2021-12-05T16:59:33Z Cache configuration:
bitcoin | 2021-12-05T16:59:33Z * Using 2.0 MiB for block index database
bitcoin | 2021-12-05T16:59:33Z * Using 24.8 MiB for transaction index database
bitcoin | 2021-12-05T16:59:33Z * Using 21.7 MiB for basic block filter index database
bitcoin | 2021-12-05T16:59:33Z * Using 8.0 MiB for chain state database
bitcoin | 2021-12-05T16:59:33Z * Using 143.6 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
bitcoin | 2021-12-05T16:59:33Z init message: Loading block index…
bitcoin | 2021-12-05T16:59:33Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
bitcoin | 2021-12-05T16:59:33Z Opening LevelDB in /data/.bitcoin/blocks/index
bitcoin | 2021-12-05T16:59:33Z Opened LevelDB successfully
bitcoin | 2021-12-05T16:59:33Z Using obfuscation key for /data/.bitcoin/blocks/index: 0000000000000000
bitcoin | 2021-12-05T16:59:33Z ThreadRPCServer incorrect password attempt from 10.21.21.10:45674

LND logs

Attaching to lnd
lnd | 2021-12-05 16:58:45.172 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:58:45.203 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:58:45.346 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:58:49.419 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:58:59.439 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:05.096 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:05.099 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:05.100 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:05.100 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:05.100 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:05.101 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:05.187 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:09.466 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:20.501 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:24.381 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:24.381 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:24.404 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:24.406 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:24.406 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:24.437 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:24.499 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:30.524 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:40.551 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:44.407 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:44.407 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:44.407 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:44.417 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:44.420 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:44.423 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: wallet not created, create one to enable full RPC access
lnd | 2021-12-05 16:59:44.493 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: wallet not created, create one to enable full RPC access

electrs logs

Attaching to electrs
electrs |
electrs | Caused by:
electrs | 0: bitcoind RPC polling failed
electrs | 1: daemon not available
electrs | 2: JSON-RPC error: transport error: Didn’t receive response data in time, timed out.
electrs | Starting electrs 0.9.1 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: V4(10.21.21.8:8332), daemon_p2p_addr: V4(10.21.21.8:8333), electrum_rpc_addr: V4(0.0.0.0:50001), monitoring_addr: V4(127.0.0.1:4224), wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: Some(200), reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, disable_electrum_rpc: false, server_banner: “Umbrel v0.4.9”, args: [] }
electrs | [2021-12-05T16:59:09.942Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs | [2021-12-05T16:59:10.264Z INFO electrs::db] “/data/db/bitcoin”: 6612 SST files, 0.00532266 GB, 0.000000021 Grows
electrs | [2021-12-05T16:59:10.374Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:11.376Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:12.378Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:13.380Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:14.382Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:15.384Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:16.386Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:17.389Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:18.391Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:19.393Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:20.396Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:21.398Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:22.400Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:23.402Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:24.405Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2021-12-05T16:59:25.408Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-12-05T16:59:26.410Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-12-05T16:59:27.412Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-12-05T16:59:28.414Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-12-05T16:59:29.416Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-12-05T16:59:30.418Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2021-12-05T16:59:31.420Z INFO electrs::daemon] waiting for RPC warmup: Loading wallet…

Tor logs

Attaching to umbrel_app_tor_1, umbrel_app_3_tor_1, umbrel_app_2_tor_1, tor
app_2_tor_1 | Dec 05 01:10:03.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 1000 buildtimes.
app_2_tor_1 | Dec 05 01:57:56.000 [notice] Heartbeat: Tor’s uptime is 12:00 hours, with 82 circuits open. I’ve sent 31.80 MB and received 12.00 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 51 connections with IPv4 and 0 with IPv6.
app_2_tor_1 | Dec 05 01:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 340857 (consensus network-status fetch); 614445 (microdescriptor fetch)
app_2_tor_1 | Dec 05 07:57:56.000 [notice] Heartbeat: Tor’s uptime is 18:00 hours, with 104 circuits open. I’ve sent 45.37 MB and received 17.03 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 51 connections with IPv4 and 0 with IPv6.
app_2_tor_1 | Dec 05 07:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 503371 (consensus network-status fetch); 659437 (microdescriptor fetch)
app_2_tor_1 | Dec 05 13:57:56.000 [notice] Heartbeat: Tor’s uptime is 1 day 0:00 hours, with 95 circuits open. I’ve sent 60.61 MB and received 22.32 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 53 connections with IPv4 and 0 with IPv6.
app_2_tor_1 | Dec 05 13:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 630704 (consensus network-status fetch); 694945 (microdescriptor fetch)
tor | Dec 05 15:15:41.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 15:36:12.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 15:45:09.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 15:49:00.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 15:54:11.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 15:55:58.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 16:20:03.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 16:49:21.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 16:54:05.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Dec 05 16:54:32.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 1000 buildtimes.
app_3_tor_1 | Dec 05 01:57:56.000 [notice] Heartbeat: Tor’s uptime is 11:59 hours, with 226 circuits open. I’ve sent 35.21 MB and received 12.57 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 52 connections with IPv4 and 0 with IPv6.
app_3_tor_1 | Dec 05 01:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 338507 (consensus network-status fetch); 451062 (microdescriptor fetch)
app_3_tor_1 | Dec 05 07:57:56.000 [notice] Heartbeat: Tor’s uptime is 17:59 hours, with 77 circuits open. I’ve sent 46.64 MB and received 17.90 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 54 connections with IPv4 and 0 with IPv6.
app_3_tor_1 | Dec 05 07:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 482616 (consensus network-status fetch); 487473 (microdescriptor fetch)
app_3_tor_1 | Dec 05 08:19:05.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 982 buildtimes.
app_3_tor_1 | Dec 05 13:57:56.000 [notice] Heartbeat: Tor’s uptime is 23:59 hours, with 109 circuits open. I’ve sent 63.69 MB and received 24.25 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 56 connections with IPv4 and 0 with IPv6.
app_3_tor_1 | Dec 05 13:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 653692 (consensus network-status fetch); 526803 (microdescriptor fetch)
app_tor_1 | Dec 05 01:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 316133 (consensus network-status fetch); 472304 (microdescriptor fetch)
app_tor_1 | Dec 05 07:57:56.000 [notice] Heartbeat: Tor’s uptime is 17:59 hours, with 87 circuits open. I’ve sent 46.68 MB and received 18.58 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 63 connections with IPv4 and 0 with IPv6.
app_tor_1 | Dec 05 07:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 453399 (consensus network-status fetch); 509405 (microdescriptor fetch)
app_tor_1 | Dec 05 11:32:05.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 1000 buildtimes.
app_tor_1 | Dec 05 13:57:56.000 [notice] Heartbeat: Tor’s uptime is 23:59 hours, with 79 circuits open. I’ve sent 61.73 MB and received 23.99 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 66 connections with IPv4 and 0 with IPv6.
app_tor_1 | Dec 05 13:57:56.000 [notice] While not bootstrapping, fetched this many bytes: 616577 (consensus network-status fetch); 554277 (microdescriptor fetch)
app_tor_1 | Dec 05 16:35:30.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 834 buildtimes.

App logs

btc-rpc-explorer

web_1 | 2021-12-05T09:31:09.358Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T09:31:09.358Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T10:01:09.359Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T10:01:09.360Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T10:31:09.359Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T10:31:09.359Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T11:01:09.359Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T11:01:09.359Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T11:31:09.359Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T11:31:09.359Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T12:01:09.359Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T12:01:09.359Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T12:31:09.360Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T12:31:09.360Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T13:01:09.359Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T13:01:09.360Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T13:31:09.363Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T13:31:09.363Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T14:01:09.366Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T14:01:09.366Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T14:31:09.367Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T14:31:09.367Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T15:01:09.371Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T15:01:09.371Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T15:31:09.375Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T15:31:09.375Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T16:01:09.375Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T16:01:09.375Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T16:31:09.376Z btcexp:app Skipping performance-intensive task: fetch UTXO set summary. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.
web_1 | 2021-12-05T16:31:09.376Z btcexp:app Skipping performance-intensive task: fetch last 24 hrs of blockstats to calculate transaction volume. This is skipped due to the flag ‘slowDeviceMode’ which defaults to ‘true’ to protect slow nodes. Set this flag to ‘false’ to enjoy UTXO set summary details.

specter-desktop

web_1 | File “/usr/local/lib/python3.8/site-packages/requests/sessions.py”, line 555, in get
web_1 | return self.request(‘GET’, url, **kwargs)
web_1 | File “/usr/local/lib/python3.8/site-packages/requests/sessions.py”, line 542, in request
web_1 | resp = self.send(prep, **send_kwargs)
web_1 | File “/usr/local/lib/python3.8/site-packages/requests/sessions.py”, line 655, in send
web_1 | r = adapter.send(request, **kwargs)
web_1 | File “/usr/local/lib/python3.8/site-packages/requests/adapters.py”, line 516, in send
web_1 | raise ConnectionError(e, request=request)
web_1 | requests.exceptions.ConnectionError: SOCKSHTTPSConnectionPool(host=‘pypi.org’, port=443): Max retries exceeded with url: /pypi/cryptoadvance.specter/json (Caused by NewConnectionError(’<urllib3.contrib.socks.SOCKSHTTPSConnection object at 0x7faab858e0>: Failed to establish a new connection: [Errno 111] Connection refused’))
web_1 | [2021-12-05 16:58:06,749] INFO in version: version checked. upgrade: False
web_1 | [2021-12-05 16:58:15,550] INFO in rpc: Detected RPC-Config on Environment-Variables
web_1 | [2021-12-05 16:58:15,551] WARNING in rpc: /data/.bitcoin not found
web_1 | [2021-12-05 16:58:15,611] ERROR in wallet_manager: Prevented Trying to update wallet_Manager with broken <BitcoinRpc http://10.21.21.8:8332>
web_1 | [2021-12-05 16:58:15,612] INFO in wallet_manager: Specter seems to be disconnected from Bitcoin Core. Skipping wallets update.
web_1 | [2021-12-05 16:58:35,642] INFO in rpc: Detected RPC-Config on Environment-Variables
web_1 | [2021-12-05 16:58:35,643] WARNING in rpc: /data/.bitcoin not found
web_1 | [2021-12-05 16:58:35,693] ERROR in wallet_manager: Prevented Trying to update wallet_Manager with broken <BitcoinRpc http://10.21.21.8:8332>
web_1 | [2021-12-05 16:58:35,694] INFO in wallet_manager: Specter seems to be disconnected from Bitcoin Core. Skipping wallets update.
web_1 | [2021-12-05 16:58:55,723] INFO in rpc: Detected RPC-Config on Environment-Variables
web_1 | [2021-12-05 16:58:55,723] WARNING in rpc: /data/.bitcoin not found
web_1 | [2021-12-05 16:58:55,767] ERROR in wallet_manager: Prevented Trying to update wallet_Manager with broken <BitcoinRpc http://10.21.21.8:8332>
web_1 | [2021-12-05 16:58:55,768] INFO in wallet_manager: Specter seems to be disconnected from Bitcoin Core. Skipping wallets update.
web_1 | [2021-12-05 16:59:15,797] INFO in rpc: Detected RPC-Config on Environment-Variables
web_1 | [2021-12-05 16:59:15,798] WARNING in rpc: /data/.bitcoin not found
web_1 | [2021-12-05 16:59:15,845] ERROR in wallet_manager: Prevented Trying to update wallet_Manager with broken <BitcoinRpc http://10.21.21.8:8332>
web_1 | [2021-12-05 16:59:15,846] INFO in wallet_manager: Specter seems to be disconnected from Bitcoin Core. Skipping wallets update.
web_1 | [2021-12-05 16:59:35,878] INFO in rpc: Detected RPC-Config on Environment-Variables
web_1 | [2021-12-05 16:59:35,879] WARNING in rpc: /data/.bitcoin not found
web_1 | [2021-12-05 16:59:35,937] ERROR in wallet_manager: Prevented Trying to update wallet_Manager with broken <BitcoinRpc http://10.21.21.8:8332>
web_1 | [2021-12-05 16:59:35,937] INFO in wallet_manager: Specter seems to be disconnected from Bitcoin Core. Skipping wallets update.

==== Result ====

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

did you read the troubleshooting guide?
Follow the instructions to reset the user data and start a new wallet.

Thank You for responding! I did read the user guide, however didn’t know which was the optimal step to take in my case. I didn’t have any sats on lightning, so I see now how it makes sense to “reset user data & start a new wallet”…

By the does that mean the blocks have to start from the begining? crossing my fingers that is not the case.
Also, do you know if there is there anything I can do in future to avoid this particular issue?

Much appreciated!
Gracias…

If you do not have any funds in the node, resetting the user data will not wipe the blocks, will just re-inititate a new wallet with a new seed.