Umbrel on Elementary OS

Greetings everyone,

I’m currently in the process of testing the Umbrel software on a Linux-based system (Elementary OS) with generic hardware for an upcoming review to be featured on blockdyor.com. To install the Umbrel software, I’ve used an external HDD connected via USB (this is where the Umbrel folder is), as the internal disk proved insufficient in terms of storage capacity. It’s worth noting that at the time of setup, I was unaware of the possibility to mount it using the fstab function.

So far, I’ve successfully synchronized both the Bitcoin Node and Electrs. However, I have encountered an issue with the Sparrow Wallet, specifically with regards to its TOR connectivity. Currently, I am only able to establish a local connection with the Electrs server, as Tor gives an error. Below, you can find the log detailing this issue:

electrs Attaching to electrs_app_1, electrs_app_proxy_1, electrs_electrs_1, electrs_tor_1
app_1 | umbrel-middleware
app_1 | ::ffff:10.21.0.14 - - [Mon, 18 Sep 2023 08:17:00 GMT] “GET /v1/electrs/syncPercent HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36”
app_1 |
app_1 | umbrel-middleware
app_1 | ::ffff:10.21.0.14 - - [Mon, 18 Sep 2023 08:17:16 GMT] “GET /v1/electrs/syncPercent HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36”
app_1 |
app_1 | umbrel-middleware
app_1 | ::ffff:10.21.0.14 - - [Mon, 18 Sep 2023 08:52:03 GMT] “GET /v1/electrs/syncPercent HTTP/1.1” 200 3 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
app_1 |
app_1 | umbrel-middleware
app_proxy_1 | Validating token: ac04a40bc9e5 …
app_proxy_1 | Validating token: ac04a40bc9e5 …
app_proxy_1 | Validating token: ac04a40bc9e5 …
app_proxy_1 | Validating token: ac04a40bc9e5 …
app_proxy_1 | Validating token: c66db4051aea …
app_proxy_1 | Validating token: c66db4051aea …
app_proxy_1 | Validating token: c66db4051aea …
app_proxy_1 | Validating token: c66db4051aea …
app_proxy_1 | Validating token: c66db4051aea …
app_proxy_1 | Validating token: ac04a40bc9e5 …
electrs_1 | [2023-09-18T08:36:39.705Z WARN electrs::server] 88: failed to shutdown TCP connection Transport endpoint is not connected (os error 107)
electrs_1 | [2023-09-18T08:50:58.498Z INFO electrs::index] indexing 1 blocks: [808270…808270]
electrs_1 | [2023-09-18T08:50:59.499Z INFO electrs::chain] chain updated: tip=0000000000000000000403c43da53163030ae1a3ff4a2ca2d706e5fb1a6a8c4c, height=808270
electrs_1 | [2023-09-18T08:59:26.826Z INFO electrs::index] indexing 1 blocks: [808271…808271]
electrs_1 | [2023-09-18T08:59:27.549Z INFO electrs::chain] chain updated: tip=0000000000000000000477c5ffd51644d0d36bad766c030450d7c847e243eb39, height=808271
electrs_1 | [2023-09-18T09:01:41.424Z INFO electrs::index] indexing 1 blocks: [808272…808272]
electrs_1 | [2023-09-18T09:01:43.338Z INFO electrs::chain] chain updated: tip=000000000000000000025b3e617f3f88f16389b67b94863a74f810f0436f14d0, height=808272
electrs_1 | [2023-09-18T09:07:46.152Z WARN electrs::server] 89: failed to shutdown TCP receiving Transport endpoint is not connected (os error 107)
electrs_1 | [2023-09-18T09:07:46.169Z WARN electrs::thread] recv_loop thread failed: 89: recv failed
electrs_1 | [2023-09-18T09:07:46.169Z WARN electrs::thread] because: Connection timed out (os error 110)
tor_1 | Sep 18 09:19:02.191 [notice] Read configuration file “/etc/tor/torrc”.
tor_1 | Sep 18 09:19:02.196 [warn] /data/app-electrs-rpc is not owned by this user (, 1000) but by root (0). Perhaps you are running Tor as the wrong user?
tor_1 | Sep 18 09:19:02.197 [warn] Failed to parse/validate config: Failed to configure rendezvous options. See logs for details.
tor_1 | Sep 18 09:19:02.197 [err] Reading config failed–see warnings above.
tor_1 | Sep 18 09:20:03.677 [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 | Sep 18 09:20:03.677 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
tor_1 | Sep 18 09:20:03.678 [notice] Read configuration file “/etc/tor/torrc”.
tor_1 | Sep 18 09:20:03.684 [warn] /data/app-electrs-rpc is not owned by this user (, 1000) but by root (0). Perhaps you are running Tor as the wrong user?
tor_1 | Sep 18 09:20:03.684 [warn] Failed to parse/validate config: Failed to configure rendezvous options. See logs for details.
tor_1 | Sep 18 09:20:03.685 [err] Reading config failed–see warnings above.

Thanks in advance!

Hi @blockdyor

Excited to see your review!

In regards to your issue, just to clarify, when you open the Electrs dashboard from umbrel.local, is there a TOR .onion address specified under ‘TOR’?
And in that case, I assume when you try to make a connection with Sparrow it just says it is unable to connect?

Also, while this connection should work regardless, can you please check if TOR Remote Access is enabled under umbrel.local’s settings
Let me know how you go with that

Hi @smolgrrr, in the end, I decided not to review this one—it was just too outdated in terms of hardware. It actually took me over six months to fully sync the blockchain! Now I’m working on a different kind of experiment, which will serve as the base for my first Umbrel review. Stay tuned for more updates!