Bitcoin + Electrum server + Block explorer under Windows (with WSL and Debian)

Flair14

newbie

Activity: 13

Merit: 0

Quote from: NeuroticFish on March 31, 2022, 02:06:52 AM

Quote from: HCP on March 30, 2022, 07:05:40 PM

Code:

Error: electrs failed

Caused by:
    0: bitcoind RPC polling failed
    1: daemon not available
    2: JSON-RPC error: transport error: Couldn't connect to host: Connection refused (os error 111)
hcp@HCP-PC:~/electrs$

Really not sure what is causing the issue... any one else come across this? Huh

I can easily reproduce this when bitcoin core is running, but it's not synced.
So I'd start with getting full sync.

If that's not the cause, maybe take a look at rpcbind or rpcallowip in bitcoin.conf...

I am having the exact same error on Debian 12. I have a node that is fully synced. Compiled romanz/electrs without fail but I am unable to run it.

bitcoin.conf has rpcbind and rpcallowip

rpcbind=127.0.0.1
rpcbind=the ip of the node
rpcallowip=127.0.0.1
rpcallowip=ip network of the node

Any idea how to fix it?

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

I've done some tests with having an username and a password for RPC in Bitcoin Core instead of cookie file and I will post them here in case somebody wants to do that.
I will comment out (not delete) the config lines related to RPC cookie file.
Let's say that the username will be UsErNaMe and the password will be PaSsWoRd (please use much better ones though, just I would avoid using # or : in them).

This would make x:\BitcoinDataDir\bitcoin.conf (see this post) look like:

Code: (bitcoin.conf)

txindex=1
server=1
rpcbind=127.0.0.1
rpcallow=127.0.0.1
#rpccookiefile=.mycookie
rpcuser=UsErNaMe
rpcpassword=PaSsWoRd

For Electrs, the content of $HOME/electrs/target/release/electrs.toml (see this post) will become:

Code: (electrs.toml)

#cookie_file = "/mnt/x/BitcoinDataDir/.mycookie"
auth="UsErNaMe:PaSsWoRd"
daemon_dir = "/mnt/x/BitcoinDataDir"
daemon_rpc_addr = "127.0.0.1:8332"
daemon_p2p_addr = "127.0.0.1:8333"
db_dir = "/mnt/y/ElectrsData"
network = "bitcoin"
electrum_rpc_addr = "127.0.0.1:50001"
#verbose = 2 -> obsolete, was working with version 0.9.0, no longer works in 0.9.3
#use log-filters for version 0.9.3+
log_filters = "INFO"
server_banner = "Electrs @ NeuroticFish, yay!"

And for BTC RPC Explorer, $HOME/btc-rpc-explorer/.env (see this post) becomes:

Code: (.env)

BTCEXP_BASEURL=/exp/
BTCEXP_BITCOIND_HOST=127.0.0.1
BTCEXP_BITCOIND_PORT=8332
#BTCEXP_BITCOIND_COOKIE=/mnt/X/BitcoinDataDir/.mycookie
BTCEXP_BITCOIND_USER=UsErNaMe
BTCEXP_BITCOIND_PASS=PaSsWoRd
BTCEXP_BITCOIND_RPC_TIMEOUT=5000
BTCEXP_ADDRESS_API=electrum
BTCEXP_ELECTRUM_SERVERS=tcp://127.0.0.1:50001
BTCEXP_ELECTRUM_TXINDEX=true
BTCEXP_SLOW_DEVICE_MODE=false
BTCEXP_PRIVACY_MODE=true
BTCEXP_NO_RATES=true

However, as said in Electrs pages, Electrs is meant for local networks, not exposed to the internet. So this setup is still not safe for the "outer world".
For that you'll probably need Blockstream's fork of electrs and maybe mempool space as explorer. And, clearly, SSL.
I wanted to make this clear, since some may expect that using Bitcoin Core RPC with user/password simply makes everything safe.

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: BlackHatCoiner on December 12, 2022, 02:15:03 PM

I've found the problem and it is, as in many similar cases, between the keyboard and the chair.
Yep, you were right and I am stupid. I managed to be careless with the config key.
I had, by mistake

Code:

log-filters = "INFO"

instead of the correct

Code:

log_filters = "INFO"

All fixed now. Thanks.

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: BlackHatCoiner on December 12, 2022, 02:15:03 PM

It should be showing it to you, because it does on raspibolt, and that uses v0.9.10.

What's your log? It should log you stuff if you've enabled it at the configuration (just add these two lines[1]). What is it showing you after you enter "./electrs"?

The config is the one from this post. I've added now your timestamp line, but no change.
After running electrs I see only the starting line containing basically the configuration (I've replaced this or that in case it's supposed to be private).

Starting electrs 0.9.10 on x86_64 linux with Config { network: Bitcoin, db_path: "/mnt/x/some/folder", daemon_dir: "/mnt/y/another/folder", daemon_auth: CookieFile("/mnt/x/some/folder/.somecookie"), daemon_rpc_addr: 127.0.0.1:8332, daemon_p2p_addr: 127.0.0.1:8333, electrum_rpc_addr: 127.0.0.1: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, disable_electrum_rpc: false, server_banner: "Electrs @ NeuroticFish", signet_magic: 3somenumber1, args: [] }

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: NeuroticFish on December 12, 2022, 02:06:27 PM

Does anybody know how to make it show up again? Is this a new feature? Can I enable it from config or command line?

It should be showing it to you, because it does on raspibolt, and that uses v0.9.10.

What's your log? It should log you stuff if you've enabled it at the configuration (just add these two lines[1]). What is it showing you after you enter "./electrs"?

[1]

Code:

log_filters = "INFO"
timestamp = true

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

I may need help from more experienced people.

It was not only my WSL affected by the badly configured/partitioned SSD and I had the opportunity to pretty much wipe everything and start anew.
I've installed everything per this tutorial - obviously the latest versions - and I've got a strange surprise I don't like: no matter how long I leave it running, Electrs doesn't want to show me the "serving Electrum RPC on 127.0.0.1:50001" message.

Electrum connects to it, BTC-RPC-Explorer also connects to it, all seem to be fine, but I am missing that message I knew it announced that everything is up and running.
Does anybody know how to make it show up again? Is this a new feature? Can I enable it from config or command line?
Thanks.

BlackHatCoiner

legendary

Activity: 1512

Merit: 7340

Farewell, Leo

Quote from: e8180kimo on November 26, 2022, 05:56:13 PM

Do you know how to setup with Tor or how to connect to my node with your setup remotely?

Update and install tor:

Code:

sudo apt update
sudo apt install tor

Check if Tor is installed:

Code:

tor --version
> Tor version 0.4.X
[...]

Edit the configuration file:

Code:

sudo nano /etc/tor/torrc

Add the following at the end of the file:

Code:

HiddenServiceDir /var/lib/tor/hidden_service_electrs/
HiddenServiceVersion 3
HiddenServicePort 50001 127.0.0.1:50002

(I think it needs to listen to 50001, because I see no SSL in this guide)

Reload tor:

Code:

sudo systemctl reload tor

Get the onion address with:

Code:

sudo cat /var/lib/tor/hidden_service_electrs/hostname

You connect to abc...xyz.onion:50002.

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: e8180kimo on November 26, 2022, 05:56:13 PM

Do you know how to setup with Tor or how to connect to my node with your setup remotely?

Sorry, I didn't do such tests, I use this configuration locally.
But if you install this Electrs and want to use from outside of the local computer, I think that a first step would be to set the correct address you're accessing it from, or, if you want to allow all addresses then probably

Code:

electrum_rpc_addr = "0.0.0.0:50001"

instead of

Code:

electrum_rpc_addr = "127.0.0.1:50001"

But I advise this only on LAN. If you go out of your LAN then you'll probably have to configure SSL too (and allow some port forwarding in your router too).

Tor, sorry, I really don't know...

e8180kimo

newbie

Activity: 1

Merit: 0

Do you know how to setup with Tor or how to connect to my node with your setup remotely?

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Maintenance: updating BTC RPC Explorer
Warning: it was not the nicest and cleanest update, but it works. You may want to read the warnings at the end.

Unlike Electrs, I didn't find any clear tutorial on how to update BTC RPC Explorer. But it's not difficult either.

Version
When you start your local BTC RPC Explorer it will show, at very start, its version. Or it can be seen at the bottom of web page. Mine is now 3.2.0.
In the git page of the project ( https://github.com/janoside/btc-rpc-explorer ) there's a combobox telling "master". If you click it, and click tags, you'll see all the versions; more important, you'll see which is the latest one. Now it shows 3.3.0, so I'll update to that.

Update OS
Well, this should be run more often and you may want to skip it if you've just done that when updating Electrs.

Code:

sudo apt update
sudo apt upgrade

Now.. let's go:

Code:

cd btc-rpc-explorer
git checkout master
git pull

Here I was told that I have local changes. If you don't, skip this part.

Code:

git reset --hard
git pull

Back on track; keep in mind that unlike Electrs, here I couldn't find a way to verify.

Code:

git checkout v3.3.0
npm install

It gave multiple warnings, but it seems to be installed (I've checked it and it works, so maybe you'll skip the fix warnings part.)

The Warnings
As I wrote, although it's well updated, it gave me warnings. Amongst those, it asked me to run

Code:

npm audit fix

and it didn't do much. So the next step I've done was the more risky (allegedly it can break things!)

Code:

npm audit fix --force

and it looked much better. I ran again, for a test

Code:

npm install

and seems happier now. Yay! Grin

...It also wrote that it would be nice if I update to newer npm, but I've failed badly that part so I'll leave it out Cheesy

Run
If you've made the shell file like here, then:

Code:

cd ~
./run_explorer.sh

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Maintenance: updating Electrs

Now and then it makes sense to update the server, since fixes and improvements are being added to the newer versions.
The details for updating are pretty much described at: https://github.com/romanz/electrs/blob/master/doc/upgrading.md still, I thought it won't hurt to have also a newbie friendly one here, focused on what we've installed.

Version
If you start your local electrs it will show its version. Mine is now 0.9.3 (yeah, I've done at some point in the past another/newer install).
In any git page of the project (like https://github.com/romanz/electrs ) there's a combobox telling "master". If you click it, and click tags, you'll see all the versions; more important, you'll see which is the latest one. In my case it's 0.9.6, so I'll update to that.

Update OS
Well, this should be run more often than updaing electrs, however, here we are:

Code:

sudo apt update
sudo apt upgrade

Optional prerequisites
Although it's not a required step to verify the signature, I will do that.
However, for that to work, we have to make sure our pgp "knows" the signature of the developer.

Code:

curl https://romanzey.de/pgp.txt
curl -o romanz.pgp https://romanzey.de/pgp.txt
gpg --import romanz.pgp

It should tell: "imported: 1".

Update Electrs
Since we have manual install, that path is what I'll follow.

Keep in mind that this code is for version 0.9.6; if you'll find newer versions on git, please adapt to that one.

Code:

cd ~
cd electrs
git checkout master
git pull

Now there's the optional step of verifying what we get. If you didn't import the pgp key, you will probably also skip this.

Code:

git verify-tag v0.9.6

It should tell things like "good signature" and "Primary key fingerprint: 15C8 C357 4AE4 F1E2 5F3F 35C5 87CA E5FA 4691 7CBB"
It may also give a warning that it's not the most trusted signature, but it's fine.

Let's proceed:

Code:

git checkout v0.9.6
ROCKSDB_INCLUDE_DIR=/usr/include ROCKSDB_LIB_DIR=/usr/lib cargo build --locked --release

If, back at install time, your install of librocksdb-dev has failed and have used a workaround, you'll have to look in git and adapt this last command (probably go for static linked path).

And we're done! If you also have the sh file I've created here, then:

Code:

cd ~
./run_electrs.sh

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: HCP on March 30, 2022, 07:05:40 PM

Code:

Error: electrs failed

Caused by:
    0: bitcoind RPC polling failed
    1: daemon not available
    2: JSON-RPC error: transport error: Couldn't connect to host: Connection refused (os error 111)
hcp@HCP-PC:~/electrs$

Really not sure what is causing the issue... any one else come across this? Huh

I can easily reproduce this when bitcoin core is running, but it's not synced.
So I'd start with getting full sync.

If that's not the cause, maybe take a look at rpcbind or rpcallowip in bitcoin.conf...

HCP

legendary

Activity: 2086

Merit: 4361

Because I'm an idiot with bad time management... I decided that I could spare some time getting WSL and electrs up and running again... but I seem to be stuck getting electrs to start up Sad

I don't remember having to do anything too special to make it work... but when I attempt to start electrs I get:

Code:

hcp@HCP-PC:~/electrs$ ./target/release/electrs
Starting electrs 0.9.6 on x86_64 linux with Config { network: Bitcoin, db_path: "/home/hcp/electrs/bitcoin", daemon_dir: "/mnt/e/Bitcoin", daemon_auth: CookieFile("/mnt/e/Bitcoin/.cookie"), daemon_rpc_addr: 127.0.0.1:8332, daemon_p2p_addr: 127.0.0.1:8333, electrum_rpc_addr: 127.0.0.1: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, disable_electrum_rpc: false, server_banner: "Welcome to electrs 0.9.6 (Electrum Rust Server)!", args: [] }
[2022-03-30T23:47:35.040Z INFO  electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
[2022-03-30T23:47:35.040Z INFO  electrs::server] serving Electrum RPC on 127.0.0.1:50001
[2022-03-30T23:47:35.053Z INFO  electrs::db] "/home/hcp/electrs/bitcoin": 9 SST files, 0.000007245 GB, 0.000000009 Grows
[2022-03-30T23:47:35.056Z INFO  electrs::db] closing DB at /home/hcp/electrs/bitcoin
Error: electrs failed

Caused by:
    0: bitcoind RPC polling failed
    1: daemon not available
    2: JSON-RPC error: transport error: Couldn't connect to host: Connection refused (os error 111)
hcp@HCP-PC:~/electrs$

Really not sure what is causing the issue... any one else come across this? Huh

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: NeuroticFish on February 18, 2022, 04:37:02 AM

Quote from: ?? on ??

Glad it works. But what kind of warnings you received? Reduced performance? Might broken when windows release update for WSL/WSL2?

Code:

[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\full" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\null" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\ptmx" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\random" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\tty" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\urandom" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\zero" of type 0020000.

These are my warnings. I've ~~hide~~ replaced 2 parts, for privacy/security.

* Yesterday after the move I've checked that Debian, the Electrum server and the block explorer, all were working fine.
* I've had yesterday evening a Windows update and worked (I don't know what it contained though).

IIRC files in /dev represent your device and generated/removed during boot. Looks like my worry was for nothing.

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: ?? on ??

Glad it works. But what kind of warnings you received? Reduced performance? Might broken when windows release update for WSL/WSL2?

Code:

[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\full" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\null" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\ptmx" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\random" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\tty" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\urandom" of type 0020000.
[WARNING] Ignoring an unsupported file "\\?\C:\Users\\AppData\Local\Packages\TheDebianProject.DebianGNULinux_\LocalState\rootfs\dev\zero" of type 0020000.

These are my warnings. I've ~~hide~~ replaced 2 parts, for privacy/security.

* Yesterday after the move I've checked that Debian, the Electrum server and the block explorer, all were working fine.
* I've had yesterday evening a Windows update and worked (I don't know what it contained though).

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

I was told how to handle the 4.5GB Debian takes on windows drive, I will add also here the relevant information in order to Move after Install that Debian anywhere else you want.

Quote from: ABCbits on February 17, 2022, 07:29:27 AM

Check this answer https://stackoverflow.com/a/64219885. But 4.5GB is rather small compared with Windows itself and some popular application on Windows (such as Ms Office), so i wouldn't bother move it.

Quote from: NeuroticFish on February 17, 2022, 09:35:03 AM

I've installed that app with chocolatey, ran the command line, got some warnings, but went through. Now that Debian is successfully moved to HDD, I don't even mind if it's slower.

More detailed:

1. Installed Chocolatey to my Windows

1.1. Ran PowerShell as administrator and pasted there

1.2 Ran this command in that PowerShell (source: https://chocolatey.org/install ; make sure you use the latest instructions/command line from there)

Code:

Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

2. Installed LxRunOffline with chocolatey

In PowerShell started as administrator ran the command:

Code:

choco install lxrunoffline

3. Opened a completely new command prompt (cmd) as admin and there:

Code:

lxrunoffline move -n Debian -d x:\the\new\folder\

And waited for some time. Got some warnings, but went through. (Thanks again ETFbitcoin)

MixMAx123

full member

Activity: 161

Merit: 168

Thanks @NeuroticFish
I have done it now and it runs.
As announced I created a guide for Ubuntu:
https://bitcointalksearch.org/topic/instructions-installation-btc-rpc-block-explorer-under-ubuntu-5368219

NeuroticFish

legendary

Activity: 3668

Merit: 6382

Looking for campaign manager? Contact icopress!

Quote from: MixMAx123 on October 27, 2021, 06:38:24 PM

Can you help me again how I can install the version "librocksdb-dev=6.11.4-3"?

I also couldn't install that library on Ubuntu in my tests. You can see me complaining here, it was the "smaller" problem I had.
The good news is that you can go without that lib, just then instead of dynamic linking (see the lines in my initial post)

Code:

$ ROCKSDB_INCLUDE_DIR=/usr/include ROCKSDB_LIB_DIR=/usr/lib cargo build --locked --release

you have to go with static linking

Code:

cargo build --locked --release

and you get error here too, you may have to set

Code:

$ RUSTFLAGS="-C link-args=-latomic" cargo build --locked --release

and retry with

Code:

cargo build --locked --release

Source/details: https://github.com/romanz/electrs/blob/master/doc/install.md#static-linking

MixMAx123

full member

Activity: 161

Merit: 168

So I came far now, but at this point I get a mistake:

Code:

sudo apt install librocksdb-dev=6.11.4-3

I did it that way:

Code:

sudo apt install librocksdb-dev

This has been installed version (5.8.8-1).
I tried "sudo apt update" but it did not work.
I can not update this version.
I tried to continue with this version.
But fatal mistakes are the result, it can not be right.
Can you help me again how I can install the version "librocksdb-dev=6.11.4-3"?
Thanks very much! :-)

MixMAx123

full member

Activity: 161

Merit: 168

Quote from: NeuroticFish on October 26, 2021, 02:52:47 AM

Also, I'm a bit surprised. If you are not great at Linux, why didn't you try with Debian as I did?

Well, it's easy, I decided on Ubuntu at that time because people said it was the best for me.
Now I have used it for a few years and you need good arguments or a weapon to bring me to learn again a new system.
I have now found and resolve many mistakes. You are right, it lay on the outdated packet. Two days I only searched for this error.
NodeJS and BTC Explorer work now.
I'll continue and now try to install electrumX or an elevated tool that creates a database for the bitcoin-addresses.
I believe I have to install Python3. At this point I had the last time my ubuntu destroyed. So now I'm here where I was the last time. :-(
When I'm done and everything works well, I will post a detailed description here as it is to set up on Ubuntu.

Topic: Bitcoin + Electrum server + Block explorer under Windows (with WSL and Debian) (Read 936 times)