I have Bitcoin Knots plus BIP-110 running as a fully synced archival node (full IBD complete, ~1072 GB used). Electrs is installed as a dependency. This hasn’t been an issue until the last two weeks. It was working fine for well over a month until now. Subsequently, this affects my mempool service as well, which has the EXACT same issue. Even if mempool didn’t have the same issue, it still relies on electrs as a dependency so I imagine it would still not run properly.
The dashboard shows a Required task: Auto-Configure on Bitcoin Knots, with reason “Electrs requires an archival bitcoin node.” When I open the dialog, it shows a Pruning field pre-filled with 550 MiB and an error: “Number must be greater than or equal to 550” — even though the field already shows 550.
I checked the actual bitcoin.conf at /media/startos/data/package-data/volumes/bitcoind/data/main/bitcoin.conf and there is no prune= line anywhere in it, confirming the node is correctly running in archival mode. The config also has txindex=1 set.
So the node is already in the correct state for Electrs, but the auto-configure task is stuck and won’t clear. It appears the auto-configure logic doesn’t handle the “no prune line present” case correctly and gets caught in a validation loop.
Steps to reproduce:
Run Bitcoin Knots BIP-110 as a full archival node (no prune= in config)
Install Electrs as a dependency
Auto-Configure task fires as Required — opening it shows the pruning validation error despite the field value already meeting the stated minimum
Expected behavior: Auto-configure should detect that pruning is already disabled (archival mode) and either clear the task or complete without error.
Actual behavior: Stuck in a validation loop. Task cannot be completed or dismissed.
What versions of these services are you running? I ask because there’s no service listed on the marketplace called Bitcoin Knots plus BIP-110, though there used to be.
If you want to run BIP-110, you should switch to Bitcoin Knots. If not, you should switch to Bitcoin Knots (pre-RTDS) or Bitcoin Core.
Interesting. I see that now. What is the reason for the removal? It sounds like that instance of Knots being removed from the marketplace is directly correlated with my Electrs not working anymore.
Before I switch packages — if I uninstall Bitcoin Knots plus BIP-110 and install the new Bitcoin Knots, will my existing blockchain data (~1072 GB at /media/startos/data/package-data/volumes/bitcoind/) be preserved and reused, or will I need to do a full IBD again? Is there a safe migration path?
Your chain data is safe and you won’t need to re-IBD — as long as you switch flavors in place rather than uninstalling first.
All the Bitcoin variants (Core, Knots, Knots pre-RDTS,) are flavors of one package, bitcoind, and they all share the same volume — the exact path you posted `(/media/startos/data/package-data/volumes/bitcoind/)`. The chain lives in that shared volume, not in the flavor package, so the new Bitcoin Knots picks it up and your Electrs/mempool dependents reconnect.
The catch: uninstalling a service deletes its data volume, which would force a full IBD. So don’t uninstall — install over the top.
Steps:
Stop your current Bitcoin service.
From the marketplace, switch to the new Bitcoin Knots — it installs over the existing bitcoind package
Let it start. It reads the same data/main/, so your txindex=1 archival config and chainstate carry over.
Electrs/mempool should reattach.
Heads up: the new Knots is the RDTS/BIP-110 line, so you’ll get an “Activate RDTS” task on install — that’s expected and matches the consensus behavior you’re already on with #knotsrdts:29.3.1:10. This switch is also the actual fix for the stuck auto-configure loop, since the old Bitcoin Knots plus BIP-110 package was pulled from the marketplace.
