# Electrs never syncs, stalls at 21-23%

**URL:** <https://community.umbrel.com/t/electrs-never-syncs-stalls-at-21-23/14033>\
**Category:** Support and Troubleshooting\
**Created:** [October 25, 2023, 3:12am UTC](https://community.umbrel.com/t/electrs-never-syncs-stalls-at-21-23/14033 "2023-10-25T03:12:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![node\_noob](https://avatars.discourse-cdn.com/v4/letter/n/c89c15/32.png) [@node\_noob](https://community.umbrel.com/u/node_noob)\
**Post date:** [October 25, 2023, 3:12am UTC](https://community.umbrel.com/t/electrs-never-syncs-stalls-at-21-23/14033/1 "2023-10-25T03:12:16Z")

</div>

My BTC node is 100% synced, but Electrs (v 0.9.14) will not sync. The progress will not go past 22 or 23%. I’ve removed/reinstalled it, waited several days. Sometimes it just says that it’s waiting for the node to sync, which it has already done for weeks now. I’m stuck! I’m on a mac running Umbrel on a Raspberry Pi.

Any help for a BTC node/non-tech noob would be much appreciated!

[Screen Shot 2023-10-24 at 8.04.40 PM|690x479](https://community.umbrel.com/uploads/short-url/ua3GTyjgUMEfYVBzl5MFyk6LvQf.png)

---

<div class="post-metadata">

**Author:** ![smolgrrr](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/smolgrrr/32/2825_2.png) [@smolgrrr](https://community.umbrel.com/u/smolgrrr)\
**Post date:** [October 25, 2023, 3:38am UTC](https://community.umbrel.com/t/electrs-never-syncs-stalls-at-21-23/14033/2 "2023-10-25T03:38:08Z")

</div>

Hi there

Can you please try the following and share the output here:

> [@Official Umbrel Troubleshooting Guide and FAQ](https://community.umbrel.com/t/official-umbrel-troubleshooting-guide-and-faq/9873/1):
>
> SSH (Secure Shell) is a way to access and control a device, such as your Umbrel server running on a Umbrel Home or Raspberry Pi, via the command line. To access Umbrel via SSH, follow these steps:
> 
> 1. Open a terminal window on your computer. On macOS, you can open the Terminal app that’s installed by default on every Mac. On Windows, you can open Command Prompt or the PowerShell app.
> 2. Type in the following command\* and press the `Enter` key:`ssh -t umbrel@umbrel.local`\*In the command given above, you can replace `umbrel.local` with the local IP of your Umbrel if you prefer. If you are using PowerShell on Windows 10, you may need to run `ssh umbrel@umbrel` instead of the command given above.
> 3. You will then be prompted to enter your password. This is the same password you use to access your Umbrel through a browser. The default password before you have created an account on your Umbrel is `moneyprintergobrrr` on Raspberry Pi, and `umbrel` on Umbrel Home. You will not be able to see your password as you type it into the terminal. Once you have typed in your password, press the `Enter` key.
> 
> This will established an SSH connection to your Umbrel server. You can now begin using the command line interface to perform various actions and troubleshoot issues that require SSH.

then run the following

> ~/umbrel/scripts/app compose electrs logs --tail 250

---

<div class="post-metadata">

**Author:** ![node\_noob](https://avatars.discourse-cdn.com/v4/letter/n/c89c15/32.png) [@node\_noob](https://community.umbrel.com/u/node_noob)\
**Post date:** [October 25, 2023, 9:15pm UTC](https://community.umbrel.com/t/electrs-never-syncs-stalls-at-21-23/14033/3 "2023-10-25T21:15:33Z")

</div>

> [@smolgrrr](#):
>
> ~/umbrel/scripts/app compose electrs logs --tail 250

Thanks for your guidance. Below is about 10% of the output

umbrel@umbrel:~ $ ~/umbrel/scripts/app compose electrs logs --tail 250  
Attaching to electrs\_app\_1, electrs\_app\_proxy\_1, electrs\_tor\_server\_1, electrs\_tor\_1, electrs\_electrs\_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\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_1 | at TCP. (node:net:709:12)  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:49:03.290 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.  
tor\_1 | Oct 25 20:49:03.290 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at [https://support.torproject.org/faq/staying-anonymous/](https://support.torproject.org/faq/staying-anonymous/)  
tor\_1 | Oct 25 20:49:03.290 [notice] Read configuration file “/etc/tor/torrc”.  
tor\_1 | Oct 25 20:49:03.316 [notice] Opening Socks listener on 127.0.0.1:9050  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:49:03.317 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050  
app\_1 | ::ffff:10.21.0.4 - - [Wed, 25 Oct 2023 21:08:23 GMT] “GET /v1/electrs/syncPercent HTTP/1.1” 500 2 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Firefox/102.0”  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:49:03.000 [notice] Bootstrapped 0% (starting): Starting  
tor\_1 | Oct 25 20:49:03.000 [notice] Starting with guard context “default”  
electrs\_1 | , 6, 140, 155, 226, 81, 152, 43, 188, 187, 211, 240, 23, 191, 29, 136, 172, 160, 134, 1, 0, 0, 0, 0, 0, 25, 118, 169, 20, 171, 255, 235, 80, 255, 73, 1, 10, 77, 161, 113, 43, 134, 5, 208, 195, 106, 197, 171, 54, 136, 172, 160, 134, 1, 0, 0, 0, 0, 0, 25, 118, 169, 20, 172, 34, 214, 12, 162, 36, 138, 40, 156, 227, 217, 214, 187, 239, 129, 50, 97, 135, 11, 160, 136, 172, 224, 147, 4, 0, 0, 0, 0, 0, 25, 118, 169, 20,

A HUGE PILE OF NUMBERS DELETED TO GET UNDER THE CHARACTER LIMIT

253, 111, 211, 136, 172, 48, 246, 41, 0, 0, 0, 0, 0, 25, 118, 169, 20, 218, 203, 25, 240, 59, 2, 177, 140, 82, 58, 221, 204, 17, 255, 131, 13, 247, 187, 190, 224, 136, 172, 0, 0, 0, 0])': unsupported segwit version: 0  
electrs\_1 | Error: electrs failed  
app\_1 |  
tor\_1 | Oct 25 20:49:04.000 [notice] Bootstrapped 5% (conn): Connecting to a relay  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 |  
tor\_1 | Oct 25 20:51:04.000 [notice] Bootstrapped 10% (conn\_done): Connected to a relay  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | Caused by:  
app\_1 | umbrel-middleware  
tor\_1 | Oct 25 20:51:04.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay  
tor\_1 | Oct 25 20:51:05.000 [notice] Bootstrapped 15% (handshake\_done): Handshake with a relay done  
electrs\_1 | 0: sync failed  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:51:05.000 [notice] Bootstrapped 20% (onehop\_create): Establishing an encrypted directory connection  
tor\_1 | Oct 25 20:51:05.000 [notice] Bootstrapped 25% (requesting\_status): Asking for networkstatus consensus  
app\_1 | Electrum attempting reconnect…  
electrs\_1 | 1: failed to get block 0000000000000233a5d1b66b716e53e8b774bf689c9a8a59c174abb84f268b7b  
tor\_1 | Oct 25 20:51:05.000 [notice] Bootstrapped 30% (loading\_status): Loading networkstatus consensus  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | 2: receiving on an empty and disconnected channel  
tor\_server\_1 | Oct 25 20:49:03.306 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.  
tor\_1 | Oct 25 20:51:05.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.  
electrs\_1 | Starting electrs 0.9.14 on aarch64 linux with Config { network: Bitcoin, db\_path: “/data/db/bitcoin”, daemon\_dir: “/data/.bitcoin”, daemon\_auth: CookieFile(“/data/.bitcoin/.cookie”), daemon\_rpc\_addr: 10.21.21.8:8332, daemon\_p2p\_addr: 10.21.21.8:8333, electrum\_rpc\_addr: 0.0.0.0:50001, monitoring\_addr: 127.0.0.1:4224, wait\_duration: 10s, jsonrpc\_timeout: 15s, index\_batch\_size: 10, index\_lookup\_limit: None, reindex\_last\_blocks: 0, auto\_reindex: true, ignore\_mempool: false, sync\_once: false, skip\_block\_download\_wait: false, disable\_electrum\_rpc: false, server\_banner: “Umbrel Electrs (0.9.14)”, signet\_magic: f9beb4d9, args: }  
tor\_server\_1 | Oct 25 20:49:03.306 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at [https://support.torproject.org/faq/staying-anonymous/](https://support.torproject.org/faq/staying-anonymous/)  
tor\_1 | Oct 25 20:51:05.000 [notice] Bootstrapped 40% (loading\_keys): Loading authority key certs  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | [2023-10-25T21:03:21.294Z INFO electrs::metrics::metrics\_impl] serving Prometheus metrics on 127.0.0.1:4224  
tor\_server\_1 | Oct 25 20:49:03.307 [notice] Read configuration file “/tmp/torrc”.  
tor\_1 | Oct 25 20:51:06.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | [2023-10-25T21:03:21.294Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001  
tor\_server\_1 | Oct 25 20:49:03.346 [notice] Opening Socks listener on 127.0.0.1:9050  
tor\_1 | Oct 25 20:51:06.000 [notice] Bootstrapped 45% (requesting\_descriptors): Asking for relay descriptors  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | [2023-10-25T21:03:21.328Z INFO electrs::db] “/data/db/bitcoin”: 22 SST files, 0.185650457 GB, 0.013350729 Grows  
tor\_server\_1 | Oct 25 20:49:03.347 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050  
tor\_1 | Oct 25 20:51:06.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/8069, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | [2023-10-25T21:03:22.266Z INFO electrs::chain] loading 172280 headers, tip=0000000000000043fbc211a98ecac9305cce590f70b3a864076f18d6c48f7fc6  
tor\_server\_1 | Oct 25 20:49:03.000 [notice] Bootstrapped 0% (starting): Starting  
tor\_1 | Oct 25 20:51:07.000 [notice] Bootstrapped 50% (loading\_descriptors): Loading relay descriptors  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | [2023-10-25T21:03:23.316Z INFO electrs::chain] chain updated: tip=0000000000000043fbc211a98ecac9305cce590f70b3a864076f18d6c48f7fc6, height=172280  
tor\_server\_1 | Oct 25 20:49:03.000 [notice] Starting with guard context “default”  
tor\_1 | Oct 25 20:51:13.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | [2023-10-25T21:03:23.392Z INFO electrs::index] indexing 2000 blocks: [172281…174280]  
tor\_server\_1 | Oct 25 20:49:04.000 [notice] Bootstrapped 5% (conn): Connecting to a relay  
tor\_1 | Oct 25 20:51:31.000 [notice] Bootstrapped 57% (loading\_descriptors): Loading relay descriptors  
app\_1 | Electrum attempting reconnect…  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | [2023-10-25T21:03:23.400Z WARN electrs::thread] p2p\_recv thread failed: sending on a disconnected channel  
tor\_server\_1 | Oct 25 20:49:05.000 [notice] Bootstrapped 10% (conn\_done): Connected to a relay  
tor\_1 | Oct 25 20:51:31.000 [notice] Bootstrapped 62% (loading\_descriptors): Loading relay descriptors  
app\_1 | Electrum attempting reconnect…  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
electrs\_1 | [2023-10-25T21:03:23.400Z INFO electrs::db] closing DB at /data/db/bitcoin  
tor\_server\_1 | Oct 25 20:49:05.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay  
tor\_1 | Oct 25 20:51:33.000 [notice] Bootstrapped 71% (loading\_descriptors): Loading relay descriptors  
app\_1 | Electrum attempting reconnect…  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:51:35.000 [notice] Bootstrapped 75% (enough\_dirinfo): Loaded enough directory info to build circuits  
app\_1 | Electrum attempting reconnect…  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:51:36.000 [notice] Bootstrapped 80% (ap\_conn): Connecting to a relay to build circuits  
app\_1 | Electrum attempting reconnect…  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:51:36.000 [notice] Bootstrapped 85% (ap\_conn\_done): Connected to a relay to build circuits  
app\_1 | Electrum attempting reconnect…  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:51:37.000 [notice] Bootstrapped 89% (ap\_handshake): Finishing handshake with a relay to build circuits  
app\_1 | Electrum attempting reconnect…  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:51:38.000 [notice] Bootstrapped 90% (ap\_handshake\_done): Handshake finished with a relay to build circuits  
app\_1 | Electrum attempting reconnect…  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:51:38.000 [notice] Bootstrapped 95% (circuit\_create): Establishing a Tor circuit  
app\_1 | Electrum attempting reconnect…  
tor\_server\_1 | Oct 25 20:49:06.000 [notice] Bootstrapped 15% (handshake\_done): Handshake with a relay done  
app\_proxy\_1 | Validating token: 399fb832abb9 …  
tor\_1 | Oct 25 20:51:38.000 [notice] Bootstrapped 100% (done): Done  
app\_1 | syncPercent error: Error: connect EHOSTUNREACH 10.21.21.10:50001  
tor\_server\_1 | Oct 25 20:49:06.000 [notice] Bootstrapped 20% (onehop\_create): Establishing an encrypted directory connection  
app\_proxy\_1 | Validating token: 399fb832abb9 …

---

<div class="post-metadata">

**Author:** ![captivating\_kitten\_4](https://avatars.discourse-cdn.com/v4/letter/c/97f17d/32.png) [@captivating\_kitten\_4](https://community.umbrel.com/u/captivating_kitten_4)\
**Post date:** [May 10, 2025, 6:13am UTC](https://community.umbrel.com/t/electrs-never-syncs-stalls-at-21-23/14033/4 "2025-05-10T06:13:32Z")

</div>

I am having exactly the same problem: Electrs is stuck at 21-22%.

Looking at the logs in the Troubleshooting functionality, after some time, it simply stops reporting…

I’ve tried deleting the app and reinstalling again, restarting several times, everything is updated, but no luck.

Any idea, guys? Thanks!
