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

[eagleye]

i manually set the apollo ii mining power and speed and I"m getting better performance than in eco mode.  The temp is 7 degrees cooler, same power, and .5 TH faster.  I set power 52-55% and frequency 44-46.   fan speed is a little higher.  still close to eco power consumption.  increasing frequency above this and maintaining same power shows no errors, but no increase in speed on my unit. 

[sopsy8t]

i manually set the apollo ii mining power and speed and I"m getting better performance than in eco mode.  The temp is 7 degrees cooler, same power, and .5 TH faster.  I set power 52-55% and frequency 44-46.   fan speed is a little higher.  still close to eco power consumption.  increasing frequency above this and maintaining same power shows no errors, but no increase in speed on my unit. 

Well if your miner is attached to a solo node box, there isn't a 'miner' tab in the GUI to customize the miner settings. But in My Apollo 1 GUI, I have a tab to set everything custom. Why is that?
I think the new firmware runs the miners better now, but still - I'd love to be able to try and optimize them more. If you're getting another .5TH - thats great. Wonder if I could do it via SSH ?

[eagleye]

im running apollo os v2.1.1
goto settings > miner > customize
eco mode turns off
then power and frequency sliders pop up
apollo II
save and restart

[kekeck33]

i manually set the apollo ii mining power and speed and I"m getting better performance than in eco mode.  The temp is 7 degrees cooler, same power, and .5 TH faster.  I set power 52-55% and frequency 44-46.   fan speed is a little higher.  still close to eco power consumption.  increasing frequency above this and maintaining same power shows no errors, but no increase in speed on my unit. 

I have a standard unit, controlled via PC, can you please share the command line?

[MakerAZ]

Updated my Apollo 2 Full Node to 2.1.1 via web inteface.
All seems to be good, but Node is not starting.
Here is the log:

[2026-04-23 15:36:46.022] HTTP response to ( "getblock...) 0.251s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:46.022] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:46.022] CRITICAL: No bitcoinds active!
[2026-04-23 15:36:46.459] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:46.459] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:46.459] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:51.276] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:51.276] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:51.276] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:51.276] CRITICAL: No bitcoinds active!
[2026-04-23 15:36:51.528] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:51.528] HTTP response to ( "getblock...) 0.251s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:51.529] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:56.460] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:56.460] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:56.461] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:56.713] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:56.714] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:56.714] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:56.714] CRITICAL: No bitcoinds active!

[MakerAZ]

Updated my Apollo 2 Full Node to 2.1.1 via web inteface.
All seems to be good, but Node is not starting.
Here is the log:

[2026-04-23 15:36:46.022] HTTP response to ( "getblock...) 0.251s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:46.022] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:46.022] CRITICAL: No bitcoinds active!
[2026-04-23 15:36:46.459] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:46.459] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:46.459] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:51.276] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:51.276] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:51.276] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:51.276] CRITICAL: No bitcoinds active!
[2026-04-23 15:36:51.528] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:51.528] HTTP response to ( "getblock...) 0.251s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:51.529] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:56.460] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:56.460] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:56.461] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:56.713] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2026-04-23 15:36:56.714] HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2026-04-23 15:36:56.714] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2026-04-23 15:36:56.714] CRITICAL: No bitcoinds active!

Fixed, thanks to Gemini

[MakerAZ]

That worked. Cheers bud



This feels good, some great hardware you made @jstefanop, props to you and the team. The fact I can rent hardware from across the world and hash to my own node is something pretty special. Yeah I know latency and odds of hitting a block are non existent but for $50 it was a fun little exercise

May I know how did you configured separate difficulty levels for your local 5TH/s Apollo Miner and the rented 1PH/s mining hardware? If I keep 1024, the default starting difficulty level, 1PH/s will flood my Node with shares.

[heslo]

I just upped the starting difficulty (can't actually remember what I set it to; but Braiins did warn me it was set too low and then the number I adjusted it to was fine)

[MakerAZ]

I just upped the starting difficulty (can't actually remember what I set it to; but Braiins did warn me it was set too low and then the number I adjusted it to was fine)

Did you change the Start Difficulty number in the Apollo's Settings? It is currently at 1024, which is optimal for 5TH/s Miner.

[bubbAJoe]

I just upped the starting difficulty (can't actually remember what I set it to; but Braiins did warn me it was set too low and then the number I adjusted it to was fine)

Did you change the Start Difficulty number in the Apollo's Settings? It is currently at 1024, which is optimal for 5TH/s Miner.

I set mine to 500,000 and 10 PH/s ran fine.

[MakerAZ]

I just upped the starting difficulty (can't actually remember what I set it to; but Braiins did warn me it was set too low and then the number I adjusted it to was fine)

Did you change the Start Difficulty number in the Apollo's Settings? It is currently at 1024, which is optimal for 5TH/s Miner.

I set mine to 500,000 and 10 PH/s ran fine.

With 500K for 10PH/s or 1PH/s?
What about your built-in 5TH/s Miner? How often did your pool received shares from it? It may be so long that the pool may close connection.

[MakerAZ]

Is it at all possible to set various difficulty levels for different miners via Apollo's web interface?

[BlazeB]

Is it at all possible to set various difficulty levels for different miners via Apollo's web interface?

No, you can only set the pool-wide starting difficulty. It's fine to start your 5TH miner at a much greater difficulty. Ckpool will automatically adjust the difficulty down to a more appropriate level. In the end, only shares higher than the network difficulty count.

[heslo]

I just upped the starting difficulty (can't actually remember what I set it to; but Braiins did warn me it was set too low and then the number I adjusted it to was fine)

Did you change the Start Difficulty number in the Apollo's Settings? It is currently at 1024, which is optimal for 5TH/s Miner.

Correct, in the Start Difficulty field

[MakerAZ]

I'm in the game!

[bubbAJoe]

I just upped the starting difficulty (can't actually remember what I set it to; but Braiins did warn me it was set too low and then the number I adjusted it to was fine)

Did you change the Start Difficulty number in the Apollo's Settings? It is currently at 1024, which is optimal for 5TH/s Miner.

I set mine to 500,000 and 10 PH/s ran fine.

With 500K for 10PH/s or 1PH/s?
What about your built-in 5TH/s Miner? How often did your pool received shares from it? It may be so long that the pool may close connection.

10 PH/s for 24-hours.  Post 3216.

[super0]

HELP!

Recently upgraded to v2.1, the Miner was running perfectly on Balanced mode, I give it a try to switch to Turbo mode and now the whole machine is constantly in a reboot loop.

From a HDMI-connected screen I can see the LinuxOS reach the FutureBit Login screen asking for password, then suddenly reboot. Not sure what's going on.

Does anyone know if is possible to manually change the miner settings to Balanced somehow from the microSD card files?

EDIT: Fixed and wrote about it here https://bitcointalk.org/index.php?topic=5581895

[btcdfghj]

Hi guys,

I've got a question regarding FutureBit Solo Node Solo Mode Configuration setup.

The official Solo Node Guide (which is included in the Solo Node files) says (in the "Solo Mode Configuration"):

"Please note only legacy or legacy segwit addresses are supported for solo mining currently. DO NOT USE EXCHANGE ADDRESSES FOR SOLO MINING".

I get the part about the exchange addresses but what is a "legacy segwit address" ?

Do "bc1q........" type addresses qualify for solo mining on FutureBit Solo Node?

-------------------------------------------------------------------------------------------------------------------------

EDIT: So I've tried to insert a really long random address into the field and got a warning while typing the 62nd character:

"Warning: P2WSH and P2TR Bitcoin address are not valid for SOLO mining. Please add a different Bitcoin address"

P2WSH is a specific address type which starts with "bc1q...." but is 62 characters long (as opposed to Native Segwit "bc1q...." type address which is 42 characters long).

P2TR is a Taproot address which is 62 characters long as well.

So it looks like Native Segwit addresses ("bc1q...." which are 42 (not 62!) character long) are good for Solo mining on FutureBit Solo Node currently, and the guide contains outdated information.

Reference chart of Bitcoin address types:

https://www.unchained.com/blog/bitcoin-address-types-compared#reference-chart

[Block888737]

Hi guys,

I've got a question regarding FutureBit Solo Node Solo Mode Configuration setup.

The official Solo Node Guide (which is included in the Solo Node files) says (in the "Solo Mode Configuration"):

"Please note only legacy or legacy segwit addresses are supported for solo mining currently. DO NOT USE EXCHANGE ADDRESSES FOR SOLO MINING".

I get the part about the exchange addresses but what is a "legacy segwit address" ?

Do "bc1q........" type addresses qualify for solo mining on FutureBit Solo Node?

As someone who has won a block using a “bc1q….”  address, I can vouch that Native SegWit address are good. If you use an invalid address I’m pretty sure ckpool will reject the connection.

Legacy address = starts with 1 (e.g., 1A1zP1...) — Pay-to-Public-Key-Hash (P2PKH), the original Bitcoin address format.

Legacy SegWit address = starts with 3 (e.g., 3FZbgi...) — Pay-to-Script-Hash (P2SH)

Native SegWit = starts with bc1q — These are Bech32 addresses (P2WPKH).

[philipma1957]

Hi guys,

I've got a question regarding FutureBit Solo Node Solo Mode Configuration setup.

The official Solo Node Guide (which is included in the Solo Node files) says (in the "Solo Mode Configuration"):

"Please note only legacy or legacy segwit addresses are supported for solo mining currently. DO NOT USE EXCHANGE ADDRESSES FOR SOLO MINING".

I get the part about the exchange addresses but what is a "legacy segwit address" ?

Do "bc1q........" type addresses qualify for solo mining on FutureBit Solo Node?

my guess is that needs to be upgraded to include bc1q***   addresses

ie :

legacy. begin with 1
legacy segwit begin with 3
native seqwit begin with bc1q

no exchange addresses

only 90 to 95% sure I am correct