Official FutureBit Apollo II/BTC Software/Image and Support thread

[BlazeB]

Hi everyone, I ordered my Apollo II – Next Generation Desktop Full Node System and Home Miner back on July 12/25 — and believe it or not, I still haven’t been able to get it up and running.
Since the new OS was released, I decided to start completely from scratch and try again, but unfortunately I’m still getting the same issues.

Here’s what I’ve done so far:

Flashed the SD card with the new OS using BalenaEtcher
Formatted the HDD and started from zero
The miner is currently turned off — I’m only trying to run the full node
And this is what I’m seeing under System Logs):

date=2013-08-20T12:17:49Z  progress=0.016601  cache=53.69MiB(415338txo)

2025-12-27T21:09:37Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fdd7f04bd31a73c660b97e4 height=253190 version=0x00000002 log2_work=71.326724 tx=22411943
2025-12-27T21:09:41Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/000172.ldb
2025-12-27T21:09:41Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/000172.ldb
2025-12-27T21:09:41Z You can use -debug=leveldb to get more complete diagnostic messages
2025-12-27T21:09:41Z [error] Error reading from database, shutting down.
2025-12-27T21:09:41Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/000172.ldb


Toward the end of the logs, I keep getting database / LevelDB corruption errors and “block checksum mismatch”.

At this point I’m not sure what else to try.
Any guidance or suggestions would be greatly appreciated.

Thanks in advance!

UPDATE

The node keeps going offline, then tries to start again on its own. Sometimes it does manage to come back online, but it only stays up for a few minutes before crashing again. The behavior keeps repeating in a loop.

Since it's dying so early in the sync process, I would try formatting the SSD. Settings -> Extra -> Format Node SSD. If that doesn't fix it, it could be a hardware issue; you will want to get in contact with Futurebit.   

[SwankyMongoose]

Hey all,

Longtime lurker on the forum to keep an eye on things, first time poster for an issue that crept up over the holidays.

Running the most recent update 2.1.0 and thought things went without a hitch, however now I seem to have my node stuck in an infinite loop of attempting to start up.

Far from an expert on these things so I was hoping to get some insight before I fiddle with things and never determine the issue at hand.

Code:

[2025-12-29 19:00:55.307] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:00:55.307] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:00:55.307] CRITICAL: No bitcoinds active!
[2025-12-29 19:00:56.747] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:00:56.747] HTTP response to ( "getblock...) 0.264s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:00:56.747] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:01:00.569] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:01:00.570] HTTP response to ( "getblock...) 0.260s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:01:00.570] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:01:00.570] CRITICAL: No bitcoinds active!
[2025-12-29 19:01:01.737] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:01:01.738] HTTP response to ( "getblock...) 0.253s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:01:01.738] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:01:05.824] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:01:05.824] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:01:05.824] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:01:05.824] CRITICAL: No bitcoinds active!
[2025-12-29 19:01:06.738] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:01:06.739] HTTP response to ( "getblock...) 0.253s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:01:06.739] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate

Keeping things shut down for now to minimize wear and tear until I can troubleshoot, any info at this stage is appreciated!

[jstefanop]

Hey all,

Longtime lurker on the forum to keep an eye on things, first time poster for an issue that crept up over the holidays.

Running the most recent update 2.1.0 and thought things went without a hitch, however now I seem to have my node stuck in an infinite loop of attempting to start up.

Far from an expert on these things so I was hoping to get some insight before I fiddle with things and never determine the issue at hand.

Code:

[2025-12-29 19:00:55.307] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:00:55.307] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:00:55.307] CRITICAL: No bitcoinds active!
[2025-12-29 19:00:56.747] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:00:56.747] HTTP response to ( "getblock...) 0.264s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:00:56.747] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:01:00.569] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:01:00.570] HTTP response to ( "getblock...) 0.260s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:01:00.570] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:01:00.570] CRITICAL: No bitcoinds active!
[2025-12-29 19:01:01.737] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:01:01.738] HTTP response to ( "getblock...) 0.253s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:01:01.738] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:01:05.824] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:01:05.824] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:01:05.824] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-29 19:01:05.824] CRITICAL: No bitcoinds active!
[2025-12-29 19:01:06.738] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-29 19:01:06.739] HTTP response to ( "getblock...) 0.253s not ok: HTTP/1.1 401 Unauthorized
[2025-12-29 19:01:06.739] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate

Keeping things shut down for now to minimize wear and tear until I can troubleshoot, any info at this stage is appreciated!

Looks like the solo pool has not received the updated credentials after the update, try rebooting the system. If this still does not work post your node log to make sure that it is synced.

[SwankyMongoose]

Have let it run for a bit this evening.

Here are the recent node specific logs -

Code:

2025-12-30T07:20:22Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39658
2025-12-30T07:20:24Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39616
2025-12-30T07:20:25Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39616
2025-12-30T07:20:26Z ThreadRPCServer incorrect password attempt from 127.0.0.1:53436
2025-12-30T07:20:27Z ThreadRPCServer incorrect password attempt from 127.0.0.1:53458
2025-12-30T07:20:31Z ThreadRPCServer incorrect password attempt from 127.0.0.1:53478

[Wolf_schiesst]

Kicked off the upgrade on the web console last night and it stopped at 30%, and I went to bed.
Checking it this morning, the upgrade didn't complete, so I logged in via KVM and from the web console on the desktop, restarted the upgrade. It just rebooted, so that seems to have done the trick.
Not sure what prevented it from completing but I got it upgraded.
Looking forward to the changes!

@jstefanop - something odd with my upgrade. Remote connection via web browser GUI shows I'm running on 2.1 but when I console (KVM) into the desktop and open the browser locally(port 3000), it still shows 2.07 with the old GUI.
If I click on the 2.07 where the power button is, it asks me if I want to upgrade! I wonder if the upgrade got partially corrupted? It currently mines and is running as a node just fine...

You can do this to become a great update:
ssh yourusername@Apollo_IP enter your password
sudo /opt/apolloapi/backend/update_system

This solved my problem with the recent Beta-Update. Thanks! 
By the way, for PCs I needed to add an internal network firewall rule to allow Miner Traffic (PORTs: ANY TO ANY) to my PC to get the login running (using different VLANs).

[AQUARIUZ88]

Hello FutureBit Support Team,

I’m reaching out for assistance with my Apollo unit, which is currently unable to complete boot and bring the node online. I want to summarize everything clearly to avoid repeating steps.

Issue Summary:
   •   The unit powers on normally.
   •   Internal LEDs show steady green and steady red.
   •   Ethernet link light blinks, fans ramp up and stay high.
   •   The unit either briefly appears in the router device list does not appear at all.
   •   The web UI does not load (browser shows “site can’t be reached” or times out).

Troubleshooting Already Performed:
   1.   Reflashed the microSD card multiple times using Balena Etcher (validation on/off).
   2.   Confirmed Linux partitions on the SD card (Windows prompts to format).
   3.   Tried controlled power cycles and extended boot times (30–45 minutes).
   4.   Attempted forced recovery / reset behavior.
   5.   Determined the issue was not router, firewall, or port forwarding related.
   6.   Replaced the internal NVMe SSD (original SSD suspected failed).
   7.   New SSD powers on with the same behavior: steady green/red LEDs, LAN blinking, fans ramping, but no stable network presence or UI.

Current State:
   •   The board powers on and appears alive.
   •   OS appears to start, but services never complete initialization.
   •   The unit does not reliably detect or initialize the internal SSD.

Request:
Could you please advise on:
   •   Confirmed compatible NVMe SSD models for this Apollo revision.
   •   Any required firmware steps after SSD replacement.
   •   Whether this behavior indicates a known SSD compatibility issue or controller failure.

Lastly I was told it can be a hardware issue ok cool but what part what's the fix ?

[OlympicSSJ]

   •   Confirmed compatible NVMe SSD models for this Apollo revision.

I also want to know if the latest update to the Apollo 2 has increased the list of compatible NVMes?
I remember that Kingston NV2 is supported (the one I use), but are there any other new compatible devices?

[dwood443]

I also tried to do the update and all is working execpt the node won't start with the error warning
Connection refused. Your node is not running
I have rebooted a few times with the same result. and the miner is connected via cat5 direct. also tried to manually start the node

I reflashed the sd card and even tried multiple sd cards
Can anyone help? Not sure how to check the logs as I just connect to the http://futurebit-apollo-2.local/overview interface

update. I wound up reverting back to the 2.0.7 version and all is well now

[bubbAJoe]

Has anyone tried to point NiceHash mining power to their solo node?  

I ran the NH pool tester on my node and it says difficulty too low (42). (Everything else passed). NH requires a minimum difficulty of 500,000.

Is there a way to set a minimum difficulty on the Apollo solo node?

[BlazeB]

Has anyone tried to point NiceHash mining power to their solo node?  

I ran the NH pool tester on my node and it says difficulty too low (42). (Everything else passed). NH requires a minimum difficulty of 500,000.

Is there a way to set a minimum difficulty on the Apollo solo node?

You will need to change the starting difficulty here /opt/apolloapi/backend/ckpool/ckpool.conf and restart the pool.

Add this line to ckpool.conf:

"startdiff" : 500000

[jegalindogt]

Hi everyone, I ordered my Apollo II – Next Generation Desktop Full Node System and Home Miner back on July 12/25 — and believe it or not, I still haven’t been able to get it up and running.
Since the new OS was released, I decided to start completely from scratch and try again, but unfortunately I’m still getting the same issues.

Here’s what I’ve done so far:

Flashed the SD card with the new OS using BalenaEtcher
Formatted the HDD and started from zero
The miner is currently turned off — I’m only trying to run the full node
And this is what I’m seeing under System Logs):

date=2013-08-20T12:17:49Z  progress=0.016601  cache=53.69MiB(415338txo)
2025-12-27T21:09:17Z UpdateTip: new best=0000000000000000000153b8f5c230c054f3818566f78f1548e5e4216288108 height=253182 version=0x00000002 log2_work=71.326224 tx=22480406
2025-12-27T21:09:17Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fad5bd39379a0dfde height=253183 version=0x00000002 log2_work=71.326238 tx=22480748
2025-12-27T21:09:36Z UpdateTip: new best=00000000000000000153b93132d2caf5cbc981b89c8c9ebd30607d7f5447 height=253184 version=0x00000002 log2_work=71.326437 tx=22480956
2025-12-27T21:09:32Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fda2cfb1d1730b396 height=253185 version=0x00000002 log2_work=71.326453 tx=22480981
2025-12-27T21:09:37Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fdd7f04bd31a73c660b97e4 height=253186 version=0x00000002 log2_work=71.326453 tx=22480991
2025-12-27T21:09:17Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fdd7f04bd31a73c660b97e4 height=253186 version=0x00000002 log2_work=71.326493 tx=22409391
2025-12-27T21:09:37Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fdd7f04bd31a73c660b97e4 height=253187 version=0x00000002 log2_work=71.326606 tx=22409393
2025-12-27T21:09:37Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fdd7f04bd31a73c660b97e4 height=253188 version=0x00000002 log2_work=71.326642 tx=22411066
2025-12-27T21:09:37Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fdd7f04bd31a73c660b97e4 height=253189 version=0x00000002 log2_work=71.326662 tx=22411088
2025-12-27T21:09:37Z UpdateTip: new best=00000000000000000153b93132d2caf5cb5f5fdd7f04bd31a73c660b97e4 height=253190 version=0x00000002 log2_work=71.326724 tx=22411943
2025-12-27T21:09:41Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/000172.ldb
2025-12-27T21:09:41Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/000172.ldb
2025-12-27T21:09:41Z You can use -debug=leveldb to get more complete diagnostic messages
2025-12-27T21:09:41Z [error] Error reading from database, shutting down.
2025-12-27T21:09:41Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/000172.ldb


Toward the end of the logs, I keep getting database / LevelDB corruption errors and “block checksum mismatch”.

At this point I’m not sure what else to try.
Any guidance or suggestions would be greatly appreciated.

Thanks in advance!

UPDATE

The node keeps going offline, then tries to start again on its own. Sometimes it does manage to come back online, but it only stays up for a few minutes before crashing again. The behavior keeps repeating in a loop.

Sharing this in case it helps others troubleshoot similar issues.

Symptoms

Bitcoin Core sync starts normally (pruned node).
Sync progresses to ~30–40%, then suddenly:
Web UI becomes clickable but blank.
SSH becomes unresponsive.
CPU and disk activity drop.
Device stays powered on (LEDs/fan still on).

Resolution

Futurebit offered:
Replacement controller board (easy swap, no soldering), or
Full RMA (2–3 weeks)
I chose the controller replacement for fastest turnaround.

Takeaway

If your Apollo keeps corrupting chainstate after clean re-syncs:
Don’t assume it’s software or SSD.
Run memtester more than once.
Repeated LevelDB corruption during IBD is very likely hardware-related.

Hope this saves someone else a lot of time.