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

[jimjam123]

Hello guys, some help would be appreciated with the Apollo 1.
I have the older mcu1 edition.
I wanted to use to the new Os as i want to solo mine.
When I wrote to a new micro as, the unit does not read it.
Tried several cards and still nothing.
Now when I put the OG micro sd, it doesn’t mine.
HDMI doesn’t work either, always used the ip to get in.
Ip method no longer works too.

Thanks in advance

[ethex]

Hello guys, some help would be appreciated with the Apollo 1.
I have the older mcu1 edition.
I wanted to use to the new Os as i want to solo mine.
When I wrote to a new micro as, the unit does not read it.
Tried several cards and still nothing.
Now when I put the OG micro sd, it doesn’t mine.
HDMI doesn’t work either, always used the ip to get in.
Ip method no longer works too.

Thanks in advance

why do you use older mcu1 edition?

[GPK260]

Hello guys, some help would be appreciated with the Apollo 1.
I have the older mcu1 edition.
I wanted to use to the new Os as i want to solo mine.
When I wrote to a new micro as, the unit does not read it.
Tried several cards and still nothing.
Now when I put the OG micro sd, it doesn’t mine.
HDMI doesn’t work either, always used the ip to get in.
Ip method no longer works too.

Thanks in advance

Any lights on the front of the unit? does the fan run at full speed by any chance?

[jimjam123]

Original micro sd works. Upgraded OS doesn’t work.
Sucks but trying to figure it out

[bubbAJoe]

If a miner connected to the Apollo II node hits a block, does the blockchain automatically send the coins to the wallet address in the worker name? Or are there steps that we'd need to take to receive the BTC in our wallet?

[Sledge0001]

If a miner connected to the Apollo II node hits a block, does the blockchain automatically send the coins to the wallet address in the worker name? Or are there steps that we'd need to take to receive the BTC in our wallet?

If you are using the built in solo mining option (which uses built in ckpool) on an Apollo Full Node and happen to find a block then the BTC address of the miner that found the block will directly receive the rewards assuming it is a valid block.

[bubbAJoe]

If a miner connected to the Apollo II node hits a block, does the blockchain automatically send the coins to the wallet address in the worker name? Or are there steps that we'd need to take to receive the BTC in our wallet?

If you are using the built in solo mining option (which uses built in ckpool) on an Apollo Full Node and happen to find a block then the BTC address of the miner that found the block will directly receive the rewards assuming it is a valid block.

Yes, sorry, I meant assuming using the built in solo mining option.  Thanks!

[SysIO]

Hi, what about this problem? I formatted the ssd three times on my new Apollo 2 to restart the process. There is a repair/recovery procedure to avoid wasting time? 
This is a part of debug.log:

2025-04-29T10:02:02Z Synchronizing blockheaders, height: 894449 (~100.00%)
2025-04-29T10:02:03Z New outbound peer connected: version: 70016, blocks=894449, peer=1 (outbound-full-relay)
2025-04-29T10:02:03Z No valid UPnP IGDs found
2025-04-29T10:02:04Z UpdateTip: new best=000000000000000000161b3eb86d10c4ca7501c597f01007530c318549e1dde5 height=505892 version=0x20000000 log2_work=87.952195 tx=295081822 date='2018-01-24T14:42:57Z' progress=0.278244 cache=1.2MiB(9206txo)
2025-04-29T10:02:06Z UpdateTip: new best=00000000000000000038dd541c3c5ae0df94f6b606b4caf89f3085aec7417ae3 height=505893 version=0x20000000 log2_work=87.952241 tx=295083361 date='2018-01-24T14:49:42Z' progress=0.278246 cache=2.1MiB(16043txo)
2025-04-29T10:02:07Z UpdateTip: new best=00000000000000000079010c5b9058205c8c646e67765de3c1260be2bf06cea3 height=505894 version=0x20000000 log2_work=87.952287 tx=295085778 date='2018-01-24T15:15:59Z' progress=0.278248 cache=3.5MiB(26303txo)
2025-04-29T10:02:08Z UpdateTip: new best=00000000000000000067ed29ff5a5b8ce33c697a72b2a9db31af3e34afa77a66 height=505895 version=0x20000000 log2_work=87.952334 tx=295087877 date='2018-01-24T15:16:20Z' progress=0.278250 cache=4.6MiB(34864txo)
2025-04-29T10:02:10Z UpdateTip: new best=0000000000000000004464b8ddeda229a7d97f6cc5c7b35612c9cb153c18a270 height=505896 version=0x20000000 log2_work=87.952380 tx=295089051 date='2018-01-24T15:18:16Z' progress=0.278251 cache=5.8MiB(42202txo)
2025-04-29T10:02:11Z UpdateTip: new best=0000000000000000001a3a514a5be70a838d2feffa35338ff22e2c85254ec4fb height=505897 version=0x20000000 log2_work=87.952426 tx=295089825 date='2018-01-24T15:20:04Z' progress=0.278252 cache=6.6MiB(48369txo)
2025-04-29T10:02:11Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb
2025-04-29T10:02:11Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb
2025-04-29T10:02:11Z You can use -debug=leveldb to get more complete diagnostic messages
2025-04-29T10:02:11Z Error: Error reading from database, shutting down.
2025-04-29T10:02:11Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb

Thanks

[buyDFL]

I received my Apollo II about 4-5 days ago & have been having syncing issues since day 1. I had to make the IP static because one of the issues I'm having, is that it keeps disconnecting from the interface. The node struggled to even start the syncing process, but once it did, it's been 4 long days of making a little progress and then constantly erroring out (not syncing, timed-out, error getting stats for node: failed to fetch & connection refused errors to be specific). I've had to reboot the system, reformat the SSD & do clean power cycles so many times! I finally thought I was making some real consistent progress once it finally got over block 440K, but my current issue has been that it keeps getting up to blocks just over 586K, errors out and then picks back up at just after block 584K. It's been almost 24hrs with this current cycle and ChatGPT helped a lot with each issue I have, but it can only help so much.  

Is anyone else having this particular issue or knows what's happening with my node? As per ChatGPT:

"The real issue sounds like:

Either a bad peer connection

Corrupted block files

Or a configuration or storage hiccup

If your node keeps bouncing back from 586xxx to 584xxx and repeating, it might be:

Reorg attempts (unlikely at that height and date)

Or more likely: invalid data detection triggering rollbacks."


HELP!

[eagleye]

Hi, what about this problem? I formatted the ssd three times on my new Apollo 2 to restart the process. There is a repair/recovery procedure to avoid wasting time?  
This is a part of debug.log:

2025-04-29T10:02:02Z Synchronizing blockheaders, height: 894449 (~100.00%)
2025-04-29T10:02:03Z New outbound peer connected: version: 70016, blocks=894449, peer=1 (outbound-full-relay)
2025-04-29T10:02:03Z No valid UPnP IGDs found
2025-04-29T10:02:04Z UpdateTip: new best=000000000000000000161b3eb86d10c4ca7501c597f01007530c318549e1dde5 height=505892 version=0x20000000 log2_work=87.952195 tx=295081822 date='2018-01-24T14:42:57Z' progress=0.278244 cache=1.2MiB(9206txo)
2025-04-29T10:02:06Z UpdateTip: new best=00000000000000000038dd541c3c5ae0df94f6b606b4caf89f3085aec7417ae3 height=505893 version=0x20000000 log2_work=87.952241 tx=295083361 date='2018-01-24T14:49:42Z' progress=0.278246 cache=2.1MiB(16043txo)
2025-04-29T10:02:07Z UpdateTip: new best=00000000000000000079010c5b9058205c8c646e67765de3c1260be2bf06cea3 height=505894 version=0x20000000 log2_work=87.952287 tx=295085778 date='2018-01-24T15:15:59Z' progress=0.278248 cache=3.5MiB(26303txo)
2025-04-29T10:02:08Z UpdateTip: new best=00000000000000000067ed29ff5a5b8ce33c697a72b2a9db31af3e34afa77a66 height=505895 version=0x20000000 log2_work=87.952334 tx=295087877 date='2018-01-24T15:16:20Z' progress=0.278250 cache=4.6MiB(34864txo)
2025-04-29T10:02:10Z UpdateTip: new best=0000000000000000004464b8ddeda229a7d97f6cc5c7b35612c9cb153c18a270 height=505896 version=0x20000000 log2_work=87.952380 tx=295089051 date='2018-01-24T15:18:16Z' progress=0.278251 cache=5.8MiB(42202txo)
2025-04-29T10:02:11Z UpdateTip: new best=0000000000000000001a3a514a5be70a838d2feffa35338ff22e2c85254ec4fb height=505897 version=0x20000000 log2_work=87.952426 tx=295089825 date='2018-01-24T15:20:04Z' progress=0.278252 cache=6.6MiB(48369txo)
2025-04-29T10:02:11Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb
2025-04-29T10:02:11Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb
2025-04-29T10:02:11Z You can use -debug=leveldb to get more complete diagnostic messages
2025-04-29T10:02:11Z Error: Error reading from database, shutting down.
2025-04-29T10:02:11Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb

Thanks

shutdown and restart the miner.  Turn off completely then turn on.  you want to reset the system this way.  the chainstate will rebuild itself.  Just restarting the node may not clear the error.  That has been my solution.  These chainstate files are temporary and get rewritten on bitcoind restart and when bitcoind flushes the database memory.  If the error continues after several attempts then you could have a corrupt database on the nvme and you'll need to format the nvme.  It's why I have a backup nvme.  Also, when you restart the apollo bitcoind will take several minutes rewriting the chainstate.  You'll see the cpu usage running 100% or close to it as it rebuilds the chainstate and verifies the database.  If you interrupt this process by stopping the node you interrupt this process and don't fix the problem.  Use the system monitor to look at bitciond running.  You'll see cpu usage and disk read/writes  as long as that's active bitcoind is running properly.

My apollo II has been running well for months and I've not seen that error again.  only during download of IDB.  I think it may be power surges or network interruptions that may have caused the problem.

Regarding power surges, you need a good backup power supply with noise suppression.  The apollo II power supply seems sensitive to power surges.

[bubbAJoe]

Regarding power surges, you need a good backup power supply with noise suppression.  The apollo II power supply seems sensitive to power surges.

What make/model of UPS are you using?

[eagleye]

APC Backups PRO 1500.   Some real cheap backup UPS may flicker on a brownout which will knockout the apollo II

[rwwilson75]

On the futurebit node running solo. At the top of the miner page it says to connect to 192.168.xxxx:3333. On the node page it says local node address 192.168.xxxx:8332 with a connect link to the right of it. Bitcoin core default port is 8333. My local miners connect using port 3333. I have port forwarding for 3333 and port 8333. Do i need to set 8332 as a port forward as well? JUst a little confusing whats the port 8332 for?

[BlazeB]

On the futurebit node running solo. At the top of the miner page it says to connect to 192.168.xxxx:3333. On the node page it says local node address 192.168.xxxx:8332 with a connect link to the right of it. Bitcoin core default port is 8333. My local miners connect using port 3333. I have port forwarding for 3333 and port 8333. Do i need to set 8332 as a port forward as well? JUst a little confusing whats the port 8332 for?

Do not forward port 8332, that is for RCP communications with your Bitcoin node. For example, you could use port 8332 to connect Sparrow Wallet to your node. If you're concerned about privacy, that's a great way to keep all your wallet activities anonymous, but not something you want open to the Internet.

[UncleB]

I’ve tried contacting support 3 times and never got a response so I am trying here.

I have been having issues with one of my standard miners. One of my standard miners keeps going inactive. When I go to check it out, it is cool to touch and the power switch light is off while the switch is in the on position. If I gently touch the switch (still in the on position), it clicks and the light comes back on. However, I do have to turn off my three miners to get it active again. Then it only stays active for a short time. It has gotten to the point that it is now unusable and unplugged.

[rwwilson75]

On the futurebit node running solo. At the top of the miner page it says to connect to 192.168.xxxx:3333. On the node page it says local node address 192.168.xxxx:8332 with a connect link to the right of it. Bitcoin core default port is 8333. My local miners connect using port 3333. I have port forwarding for 3333 and port 8333. Do i need to set 8332 as a port forward as well? JUst a little confusing whats the port 8332 for?

Do not forward port 8332, that is for RCP communications with your Bitcoin node. For example, you could use port 8332 to connect Sparrow Wallet to your node. If you're concerned about privacy, that's a great way to keep all your wallet activities anonymous, but not something you want open to the Internet.

Thank you for the info much appreciated!

[eagleye]

I’ve tried contacting support 3 times and never got a response so I am trying here.

I have been having issues with one of my standard miners. One of my standard miners keeps going inactive. When I go to check it out, it is cool to touch and the power switch light is off while the switch is in the on position. If I gently touch the switch (still in the on position), it clicks and the light comes back on. However, I do have to turn off my three miners to get it active again. Then it only stays active for a short time. It has gotten to the point that it is now unusable and unplugged.

Sounds like a bad power switch which is a known problem  Keep trying support for a replacement switch.

[SysIO]

Hi, what about this problem? I formatted the ssd three times on my new Apollo 2 to restart the process. There is a repair/recovery procedure to avoid wasting time?  
This is a part of debug.log:

2025-04-29T10:02:02Z Synchronizing blockheaders, height: 894449 (~100.00%)
2025-04-29T10:02:03Z New outbound peer connected: version: 70016, blocks=894449, peer=1 (outbound-full-relay)
2025-04-29T10:02:03Z No valid UPnP IGDs found
2025-04-29T10:02:04Z UpdateTip: new best=000000000000000000161b3eb86d10c4ca7501c597f01007530c318549e1dde5 height=505892 version=0x20000000 log2_work=87.952195 tx=295081822 date='2018-01-24T14:42:57Z' progress=0.278244 cache=1.2MiB(9206txo)
2025-04-29T10:02:06Z UpdateTip: new best=00000000000000000038dd541c3c5ae0df94f6b606b4caf89f3085aec7417ae3 height=505893 version=0x20000000 log2_work=87.952241 tx=295083361 date='2018-01-24T14:49:42Z' progress=0.278246 cache=2.1MiB(16043txo)
2025-04-29T10:02:07Z UpdateTip: new best=00000000000000000079010c5b9058205c8c646e67765de3c1260be2bf06cea3 height=505894 version=0x20000000 log2_work=87.952287 tx=295085778 date='2018-01-24T15:15:59Z' progress=0.278248 cache=3.5MiB(26303txo)
2025-04-29T10:02:08Z UpdateTip: new best=00000000000000000067ed29ff5a5b8ce33c697a72b2a9db31af3e34afa77a66 height=505895 version=0x20000000 log2_work=87.952334 tx=295087877 date='2018-01-24T15:16:20Z' progress=0.278250 cache=4.6MiB(34864txo)
2025-04-29T10:02:10Z UpdateTip: new best=0000000000000000004464b8ddeda229a7d97f6cc5c7b35612c9cb153c18a270 height=505896 version=0x20000000 log2_work=87.952380 tx=295089051 date='2018-01-24T15:18:16Z' progress=0.278251 cache=5.8MiB(42202txo)
2025-04-29T10:02:11Z UpdateTip: new best=0000000000000000001a3a514a5be70a838d2feffa35338ff22e2c85254ec4fb height=505897 version=0x20000000 log2_work=87.952426 tx=295089825 date='2018-01-24T15:20:04Z' progress=0.278252 cache=6.6MiB(48369txo)
2025-04-29T10:02:11Z LevelDB read failure: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb
2025-04-29T10:02:11Z Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb
2025-04-29T10:02:11Z You can use -debug=leveldb to get more complete diagnostic messages
2025-04-29T10:02:11Z Error: Error reading from database, shutting down.
2025-04-29T10:02:11Z Error reading from database: Fatal LevelDB error: Corruption: block checksum mismatch: /media/nvme/Bitcoin/chainstate/128041.ldb

Thanks

shutdown and restart the miner.  Turn off completely then turn on.  you want to reset the system this way.  the chainstate will rebuild itself.  Just restarting the node may not clear the error.  That has been my solution.  These chainstate files are temporary and get rewritten on bitcoind restart and when bitcoind flushes the database memory.  If the error continues after several attempts then you could have a corrupt database on the nvme and you'll need to format the nvme.  It's why I have a backup nvme.  Also, when you restart the apollo bitcoind will take several minutes rewriting the chainstate.  You'll see the cpu usage running 100% or close to it as it rebuilds the chainstate and verifies the database.  If you interrupt this process by stopping the node you interrupt this process and don't fix the problem.  Use the system monitor to look at bitciond running.  You'll see cpu usage and disk read/writes  as long as that's active bitcoind is running properly.

My apollo II has been running well for months and I've not seen that error again.  only during download of IDB.  I think it may be power surges or network interruptions that may have caused the problem.

Regarding power surges, you need a good backup power supply with noise suppression.  The apollo II power supply seems sensitive to power surges.

It worked again thanks to your reply, many thanks, but now the block counter stop to 785095 for more time and this is the log:

2025-05-01T18:10:51Z UpdateTip: new best=0000000000000000000595c4447aeca726f55be44eee7853e08220533e521d40 height=785094 version=0x200ee000 log2_work=94.116211 tx=823352602 date='2023-04-12T15:33:37Z' progress=0.775759 cache=318.1MiB(2164404txo)
2025-05-01T18:10:52Z UpdateTip: new best=0000000000000000000049af2d495822edb701291ad2264dc8f3921bea2227d3 height=785095 version=0x20400000 log2_work=94.116225 tx=823355666 date='2023-04-12T15:38:24Z' progress=0.775760 cache=318.4MiB(2166945txo)
2025-05-01T18:10:53Z ERROR: ConnectBlock: Consensus::CheckTxInputs: 0f65054cb7fc6f36310edd1805bda844d4c21905a7048996f0df437671966538, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-05-01T18:10:53Z InvalidChainFound: invalid block=000000000000000000035e95d598779668af4fcc8b7d00812d97596c4c30dab2  height=785096  log2_work=94.116238  date=2023-04-12T15:42:49Z
2025-05-01T18:10:53Z InvalidChainFound:  current best=0000000000000000000049af2d495822edb701291ad2264dc8f3921bea2227d3  height=785095  log2_work=94.116225  date=2023-04-12T15:38:24Z
2025-05-01T18:10:53Z ERROR: ConnectTip: ConnectBlock 000000000000000000035e95d598779668af4fcc8b7d00812d97596c4c30dab2 failed, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-05-01T18:10:53Z InvalidChainFound: invalid block=00000000000000000003d52ddd60a5c14a419cae4d7f17a955944dba62a90a40  height=785098  log2_work=94.116266  date=2023-04-12T15:51:36Z
2025-05-01T18:10:53Z InvalidChainFound:  current best=0000000000000000000049af2d495822edb701291ad2264dc8f3921bea2227d3  height=785095  log2_work=94.116225  date=2023-04-12T15:38:24Z
2025-05-01T18:10:59Z New outbound peer connected: version: 70016, blocks=894767, peer=42 (outbound-full-relay)
2025-05-01T18:12:21Z No valid UPnP IGDs found
2025-05-01T18:15:42Z Flushed fee estimates to fee_estimates.dat.

Power Off and On don't work now 

[buyDFL]

I'm staring to believe I have a defective full node. How can I get in touch with someone @ FutureBit for actual support & help?

I received my Apollo II about 4-5 days ago & have been having syncing issues since day 1. I had to make the IP static because one of the issues I'm having, is that it keeps disconnecting from the interface. The node struggled to even start the syncing process, but once it did, it's been 4 long days of making a little progress and then constantly erroring out (not syncing, timed-out, error getting stats for node: failed to fetch & connection refused errors to be specific). I've had to reboot the system, reformat the SSD & do clean power cycles so many times! I finally thought I was making some real consistent progress once it finally got over block 440K, but my current issue has been that it keeps getting up to blocks just over 586K, errors out and then picks back up at just after block 584K. It's been almost 24hrs with this current cycle and ChatGPT helped a lot with each issue I have, but it can only help so much.  

Is anyone else having this particular issue or knows what's happening with my node? As per ChatGPT:

"The real issue sounds like:

Either a bad peer connection

Corrupted block files

Or a configuration or storage hiccup

If your node keeps bouncing back from 586xxx to 584xxx and repeating, it might be:

Reorg attempts (unlikely at that height and date)

Or more likely: invalid data detection triggering rollbacks."


HELP!

[MakerAZ]

1 undefined?