Stuck in a restart loop Bitcoin Knots and Electrs

StartOS Support
1

HI
I’m stuck in a restart loop
I searched online and got this answer:
" Bitcoin Knots and Electrs have mismatched RPC credentials , a known bug in StartOS v0.3.5.1.

  1. Re-save dependent services :
    Go to Electrs → Config → Save (no changes needed). Do the same for RTL or any other service using Bitcoin. This forces them to re-fetch credentials.

  2. If that fails, reindex Bitcoin Knots :
    Go to BTC Knots → Menu → Actions → Re-index Blockchain . This fixes corruption from unexpected shutdowns.
    "

That’s a bummer if I have to reindex bitcoin knots and wait at least a day to access my wallet linked to electrum.
any ideas? thanks

2

Try going to both services, one at a time, opening up the “config” menu and just click on “Save”.

That is the simplest / quickest solution.

But checking the service logs for errors is always the best course of action. If there is indeed signs of corruption, then you might have to try the “Re-index Blockchain” Action.

1 Like
3

Thanks Alvaro will do!

4

so it worked till today after reindexing all the block! 24hrs… and now it’s doing the restart again! can’t access my cold wallet from Tor… I had to disconnect in order to move on! anyone know what’s going on here? thanks

5

Hi rb1111, what do your logs look like when you are in the restart loop? Have there been any unexpected power interruptions to the server?

6

Hi Scott.
it looks like this:
2025-11-22T15:52:33-10:00 2025-11-23T01:52:33Z Saw new header hash=000000000000000000011258307f18fd6ac1ac9733dadc2eba675627c9cb802e height=924784
2025-11-22T15:52:33-10:00 2025-11-23T01:52:33Z Saw new header hash=00000000000000000001a52cda6f5de9b6448ba6eeb4b31b371e499f4c211430 height=924785
2025-11-22T15:52:33-10:00 2025-11-23T01:52:33Z P2P peers available. Skipped DNS seeding.
2025-11-22T15:52:33-10:00 2025-11-23T01:52:33Z dnsseed thread exit
2025-11-22T15:52:50-10:00 2025-11-23T01:52:50Z UpdateTip: new best=00000000000000000001094b69817c400f81eb075d2fe2108ac5117d1c1c9605 height=924776 version=0x20038000 log2_work=95.951077 tx=1274249235 date=‘2025-11-22T23:24:00Z’ progress=0.999953 cache=26.7MiB(194804txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:52:50-10:00 2025-11-23T01:52:50Z UpdateTip: new best=000000000000000000003e1a7f62fbe32c8f022a054c0196ed2b32d64a860e4e height=924777 version=0x2fffe004 log2_work=95.951089 tx=1274251638 date=‘2025-11-22T23:38:12Z’ progress=0.999957 cache=27.4MiB(200940txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:52:50-10:00 2025-11-23T01:52:50Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2025-11-22T15:52:50-10:00 2025-11-23T01:52:50Z New outbound-full-relay v1 peer connected: version: 70016, blocks=924785, peer=4
2025-11-22T15:52:51-10:00 2025-11-23T01:52:51Z UpdateTip: new best=0000000000000000000066d1bafc3c9c66fe581b42128184b0c79c6186a5b6c9 height=924778 version=0x20052000 log2_work=95.951102 tx=1274255706 date=‘2025-11-22T23:53:57Z’ progress=0.999962 cache=28.4MiB(208968txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:52:53-10:00 2025-11-23T01:52:53Z UpdateTip: new best=00000000000000000000dc5071f9151e27f3f5b0bec5fa00fce769ccfc82cea3 height=924779 version=0x30cf4000 log2_work=95.951114 tx=1274258720 date=‘2025-11-23T00:26:01Z’ progress=0.999973 cache=29.7MiB(219554txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:52:53-10:00 2025-11-23T01:52:53Z UpdateTip: new best=000000000000000000015eb4261372b3bce7c68e46aaf509c11cdb51ae568f63 height=924780 version=0x2252e000 log2_work=95.951126 tx=1274261635 date=‘2025-11-23T00:52:52Z’ progress=0.999981 cache=30.7MiB(227109txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:52:53-10:00 2025-11-23T01:52:53Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
2025-11-22T15:52:54-10:00 2025-11-23T01:52:54Z UpdateTip: new best=00000000000000000000aa2272db1bab9a71d25af54c5f83552d08d403afa77d height=924781 version=0x20dc2000 log2_work=95.951139 tx=1274264983 date=‘2025-11-23T01:14:24Z’ progress=0.999988 cache=31.4MiB(234889txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:52:57-10:00 2025-11-23T01:52:57Z UpdateTip: new best=000000000000000000006a0b39e98a61b01ebe4c7dec7b55ca511100b3ad4a2a height=924782 version=0x26000000 log2_work=95.951151 tx=1274267580 date=‘2025-11-23T01:22:28Z’ progress=0.999990 cache=32.2MiB(238855txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:52:57-10:00 2025-11-23T01:52:57Z New outbound-full-relay v1 peer connected: version: 70016, blocks=924785, peer=5
2025-11-22T15:52:58-10:00 2025-11-23T01:52:58Z UpdateTip: new best=000000000000000000003f1378d3fabdea55ddcb89c819c995c770e7815962b9 height=924783 version=0x25522000 log2_work=95.951163 tx=1274269061 date=‘2025-11-23T01:22:49Z’ progress=0.999990 cache=32.4MiB(241855txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:52:58-10:00 2025-11-23T01:52:58Z New outbound-full-relay v2 peer connected: version: 70016, blocks=924785, peer=6
2025-11-22T15:53:01-10:00 2025-11-23T01:53:01Z UpdateTip: new best=000000000000000000011258307f18fd6ac1ac9733dadc2eba675627c9cb802e height=924784 version=0x20124000 log2_work=95.951176 tx=1274272712 date=‘2025-11-23T01:29:15Z’ progress=0.999992 cache=32.9MiB(246658txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:53:02-10:00 2025-11-23T01:53:02Z UpdateTip: new best=00000000000000000001a52cda6f5de9b6448ba6eeb4b31b371e499f4c211430 height=924785 version=0x20846000 log2_work=95.951188 tx=1274275244 date=‘2025-11-23T01:34:46Z’ progress=0.999994 cache=33.2MiB(249314txo) warning=‘Miner violated version bit protocol’
2025-11-22T15:53:09-10:00 2025-11-23T01:53:09Z New outbound-full-relay v2 peer connected: version: 70016, blocks=924785, peer=7
2025-11-22T15:53:18-10:00 2025-11-23T01:53:18Z New outbound-full-relay v2 peer connected: version: 70016, blocks=924785, peer=8

No power interruptions to the server…
Thanks

7

Hey! Have you tried config → save on both services after reindex?

1 Like
8

yes I did many time in vain

9

You can try running a System Rebuild.

A System Rebuild, which won’t delete or change anything. Just rebuilds the containers.

You can find this option under System → Power → System Rebuild

Keep in mind that It may take up to 70 minutes to complete. During this time, you will lose all connectivity to your server, so just be patient and let the process finish and the server will come back online when it finishes.

1 Like
10

Thanks Alvaro,
In the meantime what I did last nite is :

System/Experimental Features/Reset Tor/Wipe State (Before doing this I stopped both the Knots and Electrs

It seems to work since yesterday…
Will definitely try your suggestion if it goes back in a restart loop again!
I still want to find out why its doing this