Bitcoin node started, but losing sync after time

Hi guys, this is the last time I will try to fix the shitty umbrel node. If nobody can help, I will switch to RaspiBlitz.

Filesystem information
----------------------
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G  4.7G   24G  17% /
/dev/sda1       916G  588G  282G  68% /home/umbrel/umbrel

Startup service logs
--------------------
-- Logs begin at Tue 2023-12-19 16:36:29 UTC, end at Wed 2023-12-20 13:49:40 UTC. --
-- No entries --

External storage service logs
-----------------------------
-- Logs begin at Tue 2023-12-19 16:36:29 UTC, end at Wed 2023-12-20 13:49:40 UTC. --
-- No entries --

External storage SD card update service logs
--------------------------------------------
-- Logs begin at Tue 2023-12-19 16:36:29 UTC, end at Wed 2023-12-20 13:49:40 UTC. --
-- No entries --

Karen logs
----------

karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: 
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: debug
karen is getting triggered!
Debug result file generated
Got signal: backup
karen is getting triggered!
Deriving keys...
Creating backup...
Adding random padding...
1+0 records in
1+0 records out
3415 bytes (3.4 kB, 3.3 KiB) copied, 0.00045457 s, 7.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 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
100  6110    0     0  100  6110      0   2868  0:00:02  0:00:02 --:--:--  2868
100  6256  100   146  100  6110     56   2365  0:00:02  0:00:02 --:--:--  2421
{"message":"Successfully uploaded backup 1703021704676.tar.gz.pgp for backup ID 18f813c9b82a56b0170a796e758c3dd9edd7a8fe5711a8d7657a5fc5467f6c10"}
=============================
====== Backup success =======
=============================
Got signal: backup
karen is getting triggered!
Deriving keys...
Creating backup...
Adding random padding...
1+0 records in
1+0 records out
553 bytes copied, 0.000445792 s, 1.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 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0
100  3398  100   146  100  3252     28    640  0:00:05  0:00:05 --:--:--   669
100  3398  100   146  100  3252     28    640  0:00:05  0:00:05 --:--:--   668
{"message":"Successfully uploaded backup 1703062543452.tar.gz.pgp for backup ID 18f813c9b82a56b0170a796e758c3dd9edd7a8fe5711a8d7657a5fc5467f6c10"}
=============================
====== Backup success =======
=============================
Got signal: debug
karen is getting triggered!

Docker containers
-----------------
NAMES                          STATUS
electrs_app_1                  Up 24 hours
electrs_electrs_1              Up 2 seconds
electrs_app_proxy_1            Up 24 hours
electrs_tor_1                  Up 24 hours
electrs_tor_server_1           Up 24 hours
bitcoin_server_1               Up 24 hours
bitcoin_bitcoind_1             Up 1 second
bitcoin_i2pd_daemon_1          Up 24 hours
bitcoin_tor_server_1           Up 24 hours
bitcoin_tor_1                  Up 24 hours
bitcoin_app_proxy_1            Up 24 hours
bluewallet_lndhub_1            Restarting (4) 41 seconds ago
bluewallet_app_proxy_1         Up 24 hours
bluewallet_redis_1             Up 24 hours
bluewallet_tor_server_1        Up 24 hours
btcpay-server_web_1            Up 24 hours
btcpay-server_nbxplorer_1      Up 24 hours
btcpay-server_app_proxy_1      Up 24 hours
btcpay-server_tor_server_1     Up 24 hours
btcpay-server_postgres_1       Up 24 hours
lightning_tor_server_1         Up 24 hours
lightning_lnd_1                Up 6 hours
lightning_app_proxy_1          Up 24 hours
lightning_tor_1                Up 24 hours
lightning_app_1                Up 24 hours
snowflake_web_1                Up 24 hours
snowflake_proxy_1              Up 24 hours
snowflake_tor_server_1         Up 24 hours
snowflake_app_proxy_1          Up 24 hours
lightning-shell_web_1          Up 24 hours
lightning-shell_tor_server_1   Up 24 hours
lightning-shell_app_proxy_1    Up 24 hours
nginx                          Up 24 hours
manager                        Up 24 hours
dashboard                      Up 24 hours
auth                           Up 24 hours
tor_server                     Up 24 hours
tor_proxy                      Up 24 hours

Umbrel logs
-----------

Attaching to manager
manager      | ::ffff:10.21.0.23 - - [Wed, 20 Dec 2023 13:49:37 GMT] "GET /v1/account/token?token=8ee5765e71e908259a23e6bf95767f49b7e73a3ce25b6f20778e3a4c23d6fddf HTTP/1.1" 200 16 "-" "app-proxy/0.0.1"
manager      | 
manager      | umbrel-manager
manager      | ::ffff:10.21.21.2 - - [Wed, 20 Dec 2023 13:49:37 GMT] "GET /v1/system/storage HTTP/1.0" 200 1054 "-" "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 - - [Wed, 20 Dec 2023 13:49:38 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 - - [Wed, 20 Dec 2023 13:49:38 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 - - [Wed, 20 Dec 2023 13:49:38 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 - - [Wed, 20 Dec 2023 13:49:40 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 - - [Wed, 20 Dec 2023 13:49:40 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 - - [Wed, 20 Dec 2023 13:49:40 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 - - [Wed, 20 Dec 2023 13:49:40 GMT] "GET /v1/system/update-status 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 - - [Wed, 20 Dec 2023 13:49:42 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    | Dec 19 22:34:09.000 [warn] Received http status code 404 ("Not found") from server 65.21.94.13:8443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_proxy    | Dec 20 00:17:10.000 [warn] Received http status code 404 ("Not found") from server 65.21.94.13:8443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_proxy    | Dec 20 01:55:04.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 0 circuits open. I've sent 1.46 MB and received 14.23 MB. I've received 12 connections on IPv4 and 0 on IPv6. I've made 13 connections with IPv4 and 0 with IPv6.
tor_proxy    | Dec 20 01:55:04.000 [notice] While bootstrapping, fetched this many bytes: 700409 (consensus network-status fetch); 14104 (authority cert fetch); 12616843 (microdescriptor fetch)
tor_proxy    | Dec 20 01:55:04.000 [notice] While not bootstrapping, fetched this many bytes: 79046 (consensus network-status fetch); 9981 (authority cert fetch); 57897 (microdescriptor fetch)
tor_proxy    | Dec 20 07:55:04.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 0 circuits open. I've sent 1.47 MB and received 14.33 MB. I've received 12 connections on IPv4 and 0 on IPv6. I've made 17 connections with IPv4 and 0 with IPv6.
tor_proxy    | Dec 20 07:55:04.000 [notice] While bootstrapping, fetched this many bytes: 700409 (consensus network-status fetch); 14104 (authority cert fetch); 12616843 (microdescriptor fetch)
tor_proxy    | Dec 20 07:55:04.000 [notice] While not bootstrapping, fetched this many bytes: 132959 (consensus network-status fetch); 23031 (authority cert fetch); 57897 (microdescriptor fetch)
tor_proxy    | Dec 20 08:55:57.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 125 buildtimes.
tor_proxy    | Dec 20 11:03:12.000 [warn] Received http status code 404 ("Not found") from server 65.21.94.13:8443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".

App logs
--------

bitcoin

Attaching to bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_i2pd_daemon_1, bitcoin_tor_server_1, bitcoin_tor_1, bitcoin_app_proxy_1
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
app_proxy_1    | Validating token: 8ee5765e71e9 ...
bitcoind_1     | 2023-12-20T13:49:41Z * Using 53.4 MiB for transaction index database
bitcoind_1     | 2023-12-20T13:49:41Z * Using 46.7 MiB for basic block filter index database
bitcoind_1     | 2023-12-20T13:49:41Z * Using 8.0 MiB for chain state database
bitcoind_1     | 2023-12-20T13:49:41Z * Using 318.9 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
bitcoind_1     | 2023-12-20T13:49:41Z init message: Loading block index…
bitcoind_1     | 2023-12-20T13:49:41Z Assuming ancestors of block 000000000000000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
bitcoind_1     | 2023-12-20T13:49:41Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
bitcoind_1     | 2023-12-20T13:49:41Z Opening LevelDB in /data/.bitcoin/blocks/index
bitcoind_1     | 2023-12-20T13:49:41Z Opened LevelDB successfully
bitcoind_1     | 2023-12-20T13:49:41Z Using obfuscation key for /data/.bitcoin/blocks/index: 0000000000000000
tor_1          | Dec 20 08:00:49.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 23 circuits open. I've sent 27.78 MB and received 84.60 MB. I've received 121 connections on IPv4 and 0 on IPv6. I've made 99 connections with IPv4 and 0 with IPv6.
tor_1          | Dec 20 08:00:49.000 [notice] While bootstrapping, fetched this many bytes: 700387 (consensus network-status fetch); 14104 (authority cert fetch); 12607472 (microdescriptor fetch)
tor_1          | Dec 20 08:00:49.000 [notice] While not bootstrapping, fetched this many bytes: 144206 (consensus network-status fetch); 32760 (authority cert fetch); 204008 (microdescriptor fetch)
tor_1          | Dec 20 08:00:49.000 [notice] Average packaged cell fullness: 74.568%. TLS write overhead: 2%
tor_1          | Dec 20 08:55:04.000 [warn] Received http status code 404 ("Not found") from server 82.165.215.69:443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_1          | Dec 20 08:56:08.000 [notice] No circuits are opened. Relaxed timeout for circuit 1945 (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 4860 seconds]
tor_1          | Dec 20 10:45:05.000 [warn] Received http status code 404 ("Not found") from server 82.165.215.69:443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_1          | Dec 20 10:59:26.000 [notice] No circuits are opened. Relaxed timeout for circuit 2102 (a Hidden service: Establishing introduction point 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 7440 seconds]
tor_1          | Dec 20 12:34:46.000 [notice] No circuits are opened. Relaxed timeout for circuit 2248 (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. [3 similar message(s) suppressed in last 5760 seconds]
i2pd_daemon_1  | 13:20:26@912/error - Tunnels: Can't create inbound tunnel, no peers available
i2pd_daemon_1  | 13:21:54@254/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1  | 13:24:27@26/error - SSU2: Runtime exception: cannot create std::vector larger than max_size()
i2pd_daemon_1  | 13:29:26@912/error - Tunnels: Can't select next hop for owK8lWcFqouCsZ2mskAdS8wK4pRxynR2nKEXWqowXyM=
i2pd_daemon_1  | 13:29:26@912/error - Tunnels: Can't create inbound tunnel, no peers available
i2pd_daemon_1  | 13:32:58@26/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1  | 13:33:14@202/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1  | 13:38:06@912/error - Tunnels: Can't select next hop for 27wfI1wBkp-5jDSPmtCiOuIBacgMxFbW0QxYpK1GpII=
i2pd_daemon_1  | 13:38:06@912/error - Tunnels: Can't create inbound tunnel, no peers available
i2pd_daemon_1  | 13:38:42@26/error - SSU2: RelayIntro unknown router to introduce
server_1       | umbrel-middleware
server_1       | ::ffff:10.21.0.23 - - [Wed, 20 Dec 2023 13:49:37 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.23 - - [Wed, 20 Dec 2023 13:49:44 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.23 - - [Wed, 20 Dec 2023 13:49:47 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

bluewallet

Attaching to bluewallet_lndhub_1, bluewallet_app_proxy_1, bluewallet_redis_1, bluewallet_tor_server_1
lndhub_1      |     at Object.onReceiveStatus (/lndhub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
lndhub_1      |     at /lndhub/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
lndhub_1      |     at processTicksAndRejections (node:internal/process/task_queues:78:11) {
lndhub_1      |   code: 2,
lndhub_1      |   details: 'wallet locked, unlock it to enable full RPC access',
lndhub_1      |   metadata: Metadata {
lndhub_1      |     internalRepr: Map(1) { 'content-type' => [Array] },
lndhub_1      |     options: {}
lndhub_1      |   }
lndhub_1      | }
app_proxy_1   | yarn run v1.22.19
app_proxy_1   | $ node ./bin/www
app_proxy_1   | [HPM] Proxy created: /  -> http://bluewallet_lndhub_1:3008
app_proxy_1   | Waiting for bluewallet_lndhub_1:3008 to open...
app_proxy_1   | BlueWallet Lightning is now ready...
app_proxy_1   | Listening on port: 3008
redis_1       | 7:C 19 Dec 2023 14:00:05.339 # Redis version=6.2.2, bits=64, commit=00000000, modified=0, pid=7, just started
redis_1       | 7:C 19 Dec 2023 14:00:05.339 # Configuration loaded
redis_1       | 7:M 19 Dec 2023 14:00:05.341 * monotonic clock: POSIX clock_gettime
redis_1       | 7:M 19 Dec 2023 14:00:05.345 * Running mode=standalone, port=6379.
redis_1       | 7:M 19 Dec 2023 14:00:05.345 # Server initialized
redis_1       | 7:M 19 Dec 2023 14:00:05.367 * Loading RDB produced by version 6.2.2
redis_1       | 7:M 19 Dec 2023 14:00:05.367 * RDB age 573 seconds
redis_1       | 7:M 19 Dec 2023 14:00:05.367 * RDB memory usage when created 0.81 Mb
redis_1       | 7:M 19 Dec 2023 14:00:05.368 * DB loaded from disk: 0.007 seconds
redis_1       | 7:M 19 Dec 2023 14:00:05.368 * Ready to accept connections


btcpay-server

Attaching to btcpay-server_web_1, btcpay-server_nbxplorer_1, btcpay-server_app_proxy_1, btcpay-server_tor_server_1, btcpay-server_postgres_1
app_proxy_1   | yarn run v1.22.19
app_proxy_1   | $ node ./bin/www
app_proxy_1   | [HPM] Proxy created: /  -> http://btcpay-server_web_1:3003
app_proxy_1   | Waiting for btcpay-server_web_1:3003 to open...
app_proxy_1   | BTCPay Server is now ready...
app_proxy_1   | Listening on port: 3003
nbxplorer_1   | fail: NBXplorer.Indexer.BTC: Unhandled exception in the indexer, retrying in 60 seconds
nbxplorer_1   | System.Net.Sockets.SocketException (111): Connection refused
nbxplorer_1   |    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
nbxplorer_1   |    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
nbxplorer_1   |    at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|277_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
nbxplorer_1   |    at NBitcoin.Protocol.Connectors.DefaultEndpointConnector.ConnectSocket(Socket socket, EndPoint endpoint, NodeConnectionParameters nodeConnectionParameters, CancellationToken cancellationToken)
nbxplorer_1   |    at NBitcoin.Protocol.Node.ConnectAsync(Network network, EndPoint endpoint, NetworkAddress peer, NodeConnectionParameters parameters)
nbxplorer_1   |    at NBXplorer.Backends.Postgres.PostgresIndexers.PostgresIndexer.ConnectNode(CancellationToken token, Boolean forceRestart) in /source/NBXplorer/Backends/Postgres/PostgresIndexers.cs:line 256
nbxplorer_1   |    at NBXplorer.Backends.Postgres.PostgresIndexers.PostgresIndexer.IndexerLoopCore(CancellationToken token) in /source/NBXplorer/Backends/Postgres/PostgresIndexers.cs:line 80
nbxplorer_1   |    at NBXplorer.Backends.Postgres.PostgresIndexers.PostgresIndexer.IndexerLoop() in /source/NBXplorer/Backends/Postgres/PostgresIndexers.cs:line 59
postgres_1    | 
postgres_1    | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1    | 
postgres_1    | 2023-12-19 13:59:34.272 UTC [1] LOG:  starting PostgreSQL 13.10 (Debian 13.10-1.pgdg110+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
postgres_1    | 2023-12-19 13:59:34.277 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres_1    | 2023-12-19 13:59:34.277 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1    | 2023-12-19 13:59:34.302 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1    | 2023-12-19 13:59:34.333 UTC [28] LOG:  database system was shut down at 2023-12-19 13:50:41 UTC
postgres_1    | 2023-12-19 13:59:34.439 UTC [1] LOG:  database system is ready to accept connections
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`
web_1         | fail: PayServer:      BTC: NBXplorer error `Response status code does not indicate success: 500 (Internal Server Error).`

electrs

Attaching to electrs_app_1, electrs_electrs_1, electrs_app_proxy_1, electrs_tor_1, electrs_tor_server_1
app_1         |     at IncomingMessage.emit (node:events:539:35)
app_1         |     at endReadableNT (node:internal/streams/readable:1345:12)
app_1         |     at /app/node_modules/async-listener/glue.js:188:31
app_1         |     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
app_1         |   error: { code: -28, message: 'Loading block index…' },
app_1         |   statusCode: undefined
app_1         | }
app_1         | ::ffff:10.21.0.26 - - [Wed, 20 Dec 2023 13:49:54 GMT] "GET /v1/electrs/syncPercent HTTP/1.1" 500 125 "-" "Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0"
app_1         | 
app_1         | umbrel-middleware
electrs_1     | Caused by:
electrs_1     |     0: bitcoind RPC polling failed
electrs_1     |     1: daemon not available
electrs_1     |     2: JSON-RPC error: transport error: Couldn't connect to host: Connection refused (os error 111)
electrs_1     | Starting electrs 0.10.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: 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.10.1)", signet_magic: f9beb4d9, args: [] }
electrs_1     | [2023-12-20T13:49:38.811Z INFO  electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs_1     | [2023-12-20T13:49:38.811Z INFO  electrs::server] serving Electrum RPC on 0.0.0.0:50001
electrs_1     | [2023-12-20T13:49:39.286Z INFO  electrs::db] "/data/db/bitcoin": 7093 SST files, 1.189495038 GB, 0.093564737 Grows
electrs_1     | [2023-12-20T13:49:40.657Z INFO  electrs::chain] loading 242960 headers, tip=00000000000000ccaf3c81432f2b44f22b4044eec02dd4434ec6898adef7593b
electrs_1     | [2023-12-20T13:49:42.048Z INFO  electrs::chain] chain updated: tip=00000000000000ccaf3c81432f2b44f22b4044eec02dd4434ec6898adef7593b, height=242960
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
app_proxy_1   | Validating token: fc5d52fa568a ...
tor_1         | Dec 20 02:45:19.000 [notice] No circuits are opened. Relaxed timeout for circuit 466 (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 7800 seconds]
tor_1         | Dec 20 05:36:17.000 [warn] Received http status code 404 ("Not found") from server 15.204.142.37:443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_1         | Dec 20 07:47:20.000 [notice] No circuits are opened. Relaxed timeout for circuit 676 (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 18120 seconds]
tor_1         | Dec 20 08:01:09.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 9 circuits open. I've sent 10.42 MB and received 22.72 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 12 connections with IPv4 and 0 with IPv6.
tor_1         | Dec 20 08:01:09.000 [notice] While bootstrapping, fetched this many bytes: 700387 (consensus network-status fetch); 11096 (authority cert fetch); 12616843 (microdescriptor fetch)
tor_1         | Dec 20 08:01:09.000 [notice] While not bootstrapping, fetched this many bytes: 139182 (consensus network-status fetch); 23094 (authority cert fetch); 195208 (microdescriptor fetch)
tor_1         | Dec 20 11:11:18.000 [warn] Received http status code 404 ("Not found") from server 15.204.142.37:443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_1         | Dec 20 11:48:30.000 [warn] Received http status code 404 ("Not found") from server 15.204.142.37:443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".

lightning

Attaching to lightning_tor_server_1, lightning_lnd_1, lightning_app_proxy_1, lightning_tor_1, lightning_app_1
app_1         | Checking LND status...
app_1         | Waiting for LND...
app_1         | Checking LND status...
app_1         | Waiting for LND...
app_1         | Checking LND status...
app_1         | Waiting for LND...
app_1         | Checking LND status...
app_1         | Waiting for LND...
app_1         | Checking LND status...
app_1         | Waiting for LND...
app_proxy_1   | yarn run v1.22.19
app_proxy_1   | $ node ./bin/www
app_proxy_1   | [HPM] Proxy created: /  -> http://10.21.22.3:3006
app_proxy_1   | Waiting for 10.21.22.3:3006 to open...
app_proxy_1   | Lightning Node is now ready...
app_proxy_1   | Listening on port: 2101
lnd_1         | 2023-12-20 13:46:43.288 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd_1         | 2023-12-20 13:46:43.289 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd_1         | 2023-12-20 13:47:51.162 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
lnd_1         | 2023-12-20 13:47:51.162 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd_1         | 2023-12-20 13:47:51.163 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd_1         | 2023-12-20 13:47:51.163 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: wallet locked, unlock it to enable full RPC access
lnd_1         | 2023-12-20 13:48:59.304 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
tor_1         | Dec 20 03:18:59.000 [notice] No circuits are opened. Relaxed timeout for circuit 982 (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. [3 similar message(s) suppressed in last 8520 seconds]
tor_1         | Dec 20 07:49:56.000 [warn] Received http status code 404 ("Not found") from server 151.115.79.119:443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_1         | Dec 20 07:58:45.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 52 circuits open. I've sent 17.01 MB and received 24.51 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 17 connections with IPv4 and 0 with IPv6.
tor_1         | Dec 20 07:58:45.000 [notice] While bootstrapping, fetched this many bytes: 700409 (consensus network-status fetch); 14360 (authority cert fetch); 12616843 (microdescriptor fetch)
tor_1         | Dec 20 07:58:45.000 [notice] While not bootstrapping, fetched this many bytes: 144077 (consensus network-status fetch); 10356 (authority cert fetch); 196790 (microdescriptor fetch)
tor_1         | Dec 20 09:05:57.000 [warn] Received http status code 404 ("Not found") from server 151.115.79.119:443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
lnd_1         | 2023-12-20 13:48:59.305 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
lnd_1         | 2023-12-20 13:48:59.305 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd_1         | 2023-12-20 13:48:59.304 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: wallet locked, unlock it to enable full RPC access
tor_1         | Dec 20 09:06:59.000 [notice] No circuits are opened. Relaxed timeout for circuit 1289 (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 20880 seconds]
tor_1         | Dec 20 10:00:56.000 [warn] Received http status code 404 ("Not found") from server 151.115.79.119:443 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566+EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97".
tor_1         | Dec 20 13:08:58.000 [notice] No circuits are opened. Relaxed timeout for circuit 1538 (a Measuring circuit timeout 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 14520 seconds]

lightning-shell

Attaching to lightning-shell_web_1, lightning-shell_tor_server_1, lightning-shell_app_proxy_1
app_proxy_1   | yarn run v1.22.19
app_proxy_1   | $ node ./bin/www
app_proxy_1   | [HPM] Proxy created: /  -> http://lightning-shell_web_1:7681
app_proxy_1   | Waiting for lightning-shell_web_1:7681 to open...
app_proxy_1   | Lightning Shell is now ready...
app_proxy_1   | Listening on port: 7681
web_1         | [2023/12/19 13:58:12:3740] N: LWS: 4.3.0-a5aae04, NET CLI SRV H1 H2 WS ConMon IPv6-absent
web_1         | [2023/12/19 13:58:12:4010] N: elops_init_pt_uv:  Using foreign event loop...
web_1         | [2023/12/19 13:58:12:4012] N:  ++ [wsi|0|pipe] (1)
web_1         | [2023/12/19 13:58:12:4014] N:  ++ [vh|0|netlink] (1)
web_1         | [2023/12/19 13:58:12:4015] N:  ++ [vh|1|default||7681] (2)
web_1         | [2023/12/19 13:58:12:4017] N: [null wsi]: lws_socket_bind: source ads 0.0.0.0
web_1         | [2023/12/19 13:58:12:4019] N:  ++ [wsi|1|listen|default||7681] (2)
web_1         | [2023/12/19 13:58:12:4019] N:  Listening on port: 7681
web_1         | [2023/12/19 13:58:15:4265] N:  ++ [wsisrv|0|adopted] (1)
web_1         | [2023/12/19 13:58:15:4365] N:  -- [wsisrv|0|adopted] (0) 9.977ms

snowflake

Attaching to snowflake_web_1, snowflake_proxy_1, snowflake_tor_server_1, snowflake_app_proxy_1
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
proxy_1       | 	a=sctp-port:5000
proxy_1       | 	a=ice-ufrag:hTzdyvUiXrntXgmK
proxy_1       | 	a=ice-pwd:trHNAJTqRrvtvVqOSLRghNMUyMvcYPeE
proxy_1       | 	a=candidate:935314439 1 udp 2130706431 [scrubbed] 57697 typ host
proxy_1       | 	a=candidate:935314439 2 udp 2130706431 [scrubbed] 57697 typ host
proxy_1       | 	a=candidate:3402972551 1 udp 1694498815 [scrubbed] 3875 typ srflx raddr [scrubbed] rport 55496
proxy_1       | 	a=candidate:3402972551 2 udp 1694498815 [scrubbed] 3875 typ srflx raddr [scrubbed] rport 55496
proxy_1       | 	a=end-of-candidates
proxy_1       | 	
proxy_1       | 2023/12/20 13:45:55 Timed out waiting for client to open data channel.
web_1         | 2023/12/19 13:58:39 Using index file at /snowflake/index.html
web_1         | 2023/12/19 13:58:39 Server is starting with command: bash -c tail -n 10000 -f /snowflake/snowflake.log | grep "Traffic Relayed"
web_1         | 2023/12/19 13:58:39 URL: http://127.0.0.1:3800/
web_1         | 2023/12/19 13:58:39 URL: http://10.21.0.6:3800/
================
==== Result ====
================
The debug script did not automatically detect any issues with your Umbrel.