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

[spiderbud]

I get a status code 400 when trying to login.  I set my password and tried to login and have not been able to login to my device.
Full node connected by ethernet. I've sent tickets in but no response. I can't find anything online to help

[fxxd]

Hi, I am a newbie, so I'm sorry if I missed something trivial

I just updated my futurebit apollo 2 full node to v2.0.7, and for some reason now my node is stuck (it has a green checkmark, but stopped at block 812244). I tried restarting, shut down, reindex, but did not work

I would really appreciate it if anyone has ever had this issue solved before

Thanks!

[ImJGalt2]

Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.

I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.

It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised.  I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc.  I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."

I've scoured most of the 140+ pages in this forum.  Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.

All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this.  I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.

I've read that their return/exchange policy states only 14 days.  So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.

Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II.  (Obviously)

The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?

Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.

Just know I had good intentions when I parted with my $1k for the last 2 months...

Do they not test this shit prior to sending it out?  They had 2 months! 

[ImJGalt2]

Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.

I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.

It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised.  I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc.  I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."

I've scoured most of the 140+ pages in this forum.  Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.

All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this.  I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.

I've read that their return/exchange policy states only 14 days.  So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.

Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II.  (Obviously)

The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?

Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.

Just know I had good intentions when I parted with my $1k for the last 2 months...

Do they not test this shit prior to sending it out?  They had 2 months! 

Flashed it back to v2.0.6

Still no luck with the Node connection.

Then tried upgrading it back to v2.0.7 using the UI upgrade feature.  Non-responsive.

No flashed it back to v2.0.6

Not sure what to do from here.  Thoughts please?

[bluudz]

are there any release notes as to what has been updated? 2.06 is stable for me I dont want to jump up just yet if the updates arent critical.


thanks

It's a support update for the new hashboards shipping now. Will have the images posted on GitHub later.

Is there any details regarding this new hashboards? Are these more efficient? Any chance to be able to upgrade hashboards of older machines?

[bubbAJoe]

Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.

I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.

It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised.  I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc.  I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."

I've scoured most of the 140+ pages in this forum.  Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.

All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this.  I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.

I've read that their return/exchange policy states only 14 days.  So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.

Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II.  (Obviously)

The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?

Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.

Just know I had good intentions when I parted with my $1k for the last 2 months...

Do they not test this shit prior to sending it out?  They had 2 months! 

Flashed it back to v2.0.6

Still no luck with the Node connection.

Then tried upgrading it back to v2.0.7 using the UI upgrade feature.  Non-responsive.

No flashed it back to v2.0.6

Not sure what to do from here.  Thoughts please?

Reformat the SSD:  Settings/Extras.

This was suggested to me by FB support (after waiting a week for a response, of course) and it worked for me.  Had the same issue: "Connection refused"

[thagrmango]

Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.

I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.

It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised.  I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc.  I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."

I've scoured most of the 140+ pages in this forum.  Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.

All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this.  I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.

I've read that their return/exchange policy states only 14 days.  So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.

Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II.  (Obviously)

The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?

Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.

Just know I had good intentions when I parted with my $1k for the last 2 months...

Do they not test this shit prior to sending it out?  They had 2 months! 

I believe it has to do with your SSD. It happen very similar to me many time with node sync. Once i switched over to 2TB Samsung EVO Pro Nvme. I haven't had a reset it ever since. Give that a try and see if it works out for you.

[jstefanop]

Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.

I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.

It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised.  I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc.  I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."

I've scoured most of the 140+ pages in this forum.  Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.

All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this.  I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.

I've read that their return/exchange policy states only 14 days.  So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.

Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II.  (Obviously)

The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?

Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.

Just know I had good intentions when I parted with my $1k for the last 2 months...

Do they not test this shit prior to sending it out?  They had 2 months! 

Just reply to your order email for support. Not sure where you get the impression we dont take care of our customers. We are shipping out a high number of units currently so we might not catch  1/100 faulty units out the door.

I dont see any backlog in our support tickets beyond a few hours today.

Anything that does not work within a year is fixed or swapped out, and happy to refund if the issue was within the 14 days of you getting it.

[ImJGalt2]

Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.

I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.

It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised.  I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc.  I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."

I've scoured most of the 140+ pages in this forum.  Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.

All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this.  I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.

I've read that their return/exchange policy states only 14 days.  So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.

Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II.  (Obviously)

The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?

Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.

Just know I had good intentions when I parted with my $1k for the last 2 months...

Do they not test this shit prior to sending it out?  They had 2 months! 

Flashed it back to v2.0.6

Still no luck with the Node connection.

Then tried upgrading it back to v2.0.7 using the UI upgrade feature.  Non-responsive.

No flashed it back to v2.0.6

Not sure what to do from here.  Thoughts please?

Reformat the SSD:  Settings/Extras.

This was suggested to me by FB support (after waiting a week for a response, of course) and it worked for me.  Had the same issue: "Connection refused"

Thanks I just reformatted and it worked.  It is now redownloading.  Appreciate your help!

[ImJGalt2]

Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.

I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.

It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised.  I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc.  I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."

I've scoured most of the 140+ pages in this forum.  Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.

All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this.  I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.

I've read that their return/exchange policy states only 14 days.  So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.

Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II.  (Obviously)

The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?

Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.

Just know I had good intentions when I parted with my $1k for the last 2 months...

Do they not test this shit prior to sending it out?  They had 2 months! 

Flashed it back to v2.0.6

Still no luck with the Node connection.

Then tried upgrading it back to v2.0.7 using the UI upgrade feature.  Non-responsive.

No flashed it back to v2.0.6

Not sure what to do from here.  Thoughts please?

Reformat the SSD:  Settings/Extras.

This was suggested to me by FB support (after waiting a week for a response, of course) and it worked for me.  Had the same issue: "Connection refused"

Thanks I just reformatted and it worked.  It is now redownloading.  Appreciate your help!

Unfortunately overnight the Apollo II unit gave me the connection refused error again. Requested an RMA. 
Hope you all have better luck.

[Jdztvr]

Just received my Apollo II from Futurebit after waiting two months. $999 plus shipping.

I wanted to run my own node to support the botcoin network/community as well as have some privacy with my transactions, all the while having a lottery ticket to win 3.125 bitcoin every 10 minutes or so.

It was a noble idea, but this thing they sent me is VERY buggy and not working as advertised.  I've been trying to download the completed blockchain to the node for a few days, but it crashes, etc.  I got really far yesterday about 72% complete, but today now the unit is refusing connection: "warning Connection refused. Your node is not running."

I've scoured most of the 140+ pages in this forum.  Reached out to futurebit (not holding my breath on that)... and now kindly asking if any of you got this same error and resolved it successfully.

All this to say, I'm kinda disappointed I'm going to have to put a lot of work in to resolving this.  I overpaid to have it be easy... as time is money and I'm willing to part with my money to save time.

I've read that their return/exchange policy states only 14 days.  So I'll give it a couple more days to resolve, else, I'm returning it and dusting off my old Etherium miner (please note, I got paid in Bitcoin BTC so I'm not a shitcoiner) to run as my node.

Running the latest v2.0.7
Have At&t fiber 1GB up and down.
Hardwired directly in to switch that is connected to EERO 6.
Saved a port with the Ip address, added the 8333 and have disabled it after reading that it conflicted with operation while downloading the block chain.
Have tried rebooting router, switch, and Apollo II.  (Obviously)

The Apollo II can mine, but what's the point if I'm trying to solo mine to my own non-functioning node?

Any advice is appreciated, otherwise this baby is going back so they can make it someone else's problem.

Just know I had good intentions when I parted with my $1k for the last 2 months...

Do they not test this shit prior to sending it out?  They had 2 months!  

Flashed it back to v2.0.6

Still no luck with the Node connection.

Then tried upgrading it back to v2.0.7 using the UI upgrade feature.  Non-responsive.

No flashed it back to v2.0.6

Not sure what to do from here.  Thoughts please?

Reformat the SSD:  Settings/Extras.

This was suggested to me by FB support (after waiting a week for a response, of course) and it worked for me.  Had the same issue: "Connection refused"

Thanks I just reformatted and it worked.  It is now redownloading.  Appreciate your help!

Unfortunately overnight the Apollo II unit gave me the connection refused error again. Requested an RMA.  
Hope you all have better luck.

Hello, I’m having this exact same issue and I’m using a cat6 Ethernet cable

warning Connection refused. Your node is not running

I was able to get node to start syncing without showing the connection refused that it displays by formatting ssd. I’m now waiting on results. It’s currently at 46%…..edit- fast forward 6 hrs, and the issue occurred again with the hiccup at 50.84%.
I suspect a fault with the ssd. As thagrmango stated, I might purchase a better ssd.

[eagleye]

A few things to try.

When it says "connection refused" it means the bitcoind program stopped running.  Back a few messages, I recommend a way to monitor your node in real time with live scrolling of the debug.log.  It's very important to monitor that log as it tells you how the download is going with the database.
Sometimes you can just restart the node and it will pick up where it left off.  If you click on the button multiple times trying to force restart it can crash bitcoind.   Sometimes just restarting the system can fix the issue and restart the bitcoind.  I've had it where the bitcoind crashes, won't restart with the node start button, but shutting down the system and restarting fixes it and the bitcoind restarts normally.  Especially after a chainstate database crash.

having a running log window open allows you to see the progress and see how it stopped.  Did it just crash or did it exit or close.  you can see that in the logs.

Having the miner running may stress the power supply and for some reason the cpu is sensitive to power spikes.   that can cause a crash.  open the system monitor so you can see how busy the cpu is when downloading the blocks.  It's not a simple download, it decrypts it which takes cpu power and sets up the database.   In system monitor you can also see if bitcoind is running or not and how much resources it is taking up.

I have my unit on backup power with line conditioners.  Also only running the IBD"Initial Blockchain Download" is best.  don't have multiple browsers open and really, don't mine until it's complete.  bitcoind will use a lot of memory when downloading.  

Once the download is complete I can tell you that the system runs pretty well.  In eco, normal, or turbo, depending on your temp and noise preference.

I had problems with my microsd card that i changed out and i got two of those and also 2 pcie cards.  Once the IBD is complete I made a backup of the blockchain on the second pcie in case i had problems in the future.  Saves downloading the whole blockchain and if something goes wrong I have a quick backup.

If you have a new apollo II then is seems you must run the 2.0.7 because its designed to work with the new systems they produced.  My understanding is you can't go backwards to an older version with the new system.

[fxxd]

Hi guys, so I have reformatted my node SSD and for some reason my node gets stuck at block 841,322. I have tried this twice and got the same results. Does anyone have and ideas what might went wrong?

Thanks so much!

[proxy3]

Hi, I just received my Apollo 2 last week and have been trying to do IBD, but continually hitting the following error. Tried reformatting the ssd (tried a different SSD as well), flashed v2.0.6 (using a different SD card) and tried reindexing but nothing has worked -

2025-04-21T00:58:55Z ERROR: ConnectBlock: Consensus::CheckTxInputs: 6fb015b067fe6a09ce5b3c08309c6192385688b00e75eb9febb97c83fb2f9f7e, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-04-21T00:58:55Z InvalidChainFound: invalid block=0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea  height=341480  log2_work=82.138294  date=2015-02-01T12:08:43Z
2025-04-21T00:58:55Z InvalidChainFound:  current best=000000000000000008d4484f45d53c08c69c0db7aa7e4688b7ee90b1a5c47772  height=341479  log2_work=82.138246  date=2015-02-01T12:14:37Z
2025-04-21T00:58:55Z ERROR: ConnectTip: ConnectBlock 0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea failed, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-04-21T00:58:55Z InvalidChainFound: invalid block=0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea  height=341480  log2_work=82.138294  date=2015-02-01T12:08:43Z
2025-04-21T00:58:55Z InvalidChainFound:  current best=000000000000000008d4484f45d53c08c69c0db7aa7e4688b7ee90b1a5c47772  height=341479  log2_work=82.138246  date=2015-02-01T12:14:37Z

I'm wondering if this is a hardware issue or if there's anything else to try here.

Thanks!

[jstefanop]

Hi, I just received my Apollo 2 last week and have been trying to do IBD, but continually hitting the following error. Tried reformatting the ssd (tried a different SSD as well), flashed v2.0.6 (using a different SD card) and tried reindexing but nothing has worked -

2025-04-21T00:58:55Z ERROR: ConnectBlock: Consensus::CheckTxInputs: 6fb015b067fe6a09ce5b3c08309c6192385688b00e75eb9febb97c83fb2f9f7e, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-04-21T00:58:55Z InvalidChainFound: invalid block=0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea  height=341480  log2_work=82.138294  date=2015-02-01T12:08:43Z
2025-04-21T00:58:55Z InvalidChainFound:  current best=000000000000000008d4484f45d53c08c69c0db7aa7e4688b7ee90b1a5c47772  height=341479  log2_work=82.138246  date=2015-02-01T12:14:37Z
2025-04-21T00:58:55Z ERROR: ConnectTip: ConnectBlock 0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea failed, bad-txns-inputs-missingorspent, CheckTxInputs: inputs missing/spent
2025-04-21T00:58:55Z InvalidChainFound: invalid block=0000000000000000042aa6f0e5a237b36c0a776d2f5e2136a74444ab465373ea  height=341480  log2_work=82.138294  date=2015-02-01T12:08:43Z
2025-04-21T00:58:55Z InvalidChainFound:  current best=000000000000000008d4484f45d53c08c69c0db7aa7e4688b7ee90b1a5c47772  height=341479  log2_work=82.138246  date=2015-02-01T12:14:37Z

I'm wondering if this is a hardware issue or if there's anything else to try here.

Thanks!

If you keep getting these corruption errors after whipping the drive at least 2 times reach out to support, small number of recent batch of controllers had issues with bad memory chips.

[dimascgm]

Hey everyone,
I’m a total newbie here, so please bear with me—and I’d truly appreciate any help you can throw my way.

I received my Apollo II a couple of weeks ago. Everything was working great until there was a power outage. Since then, whenever I turn it on, my unit’s fan is running at full speed, I can't access the dashboard, and the front LED stays off.

I tried flashing versions v2.0.6 and v2.0.5, but neither worked. Maybe it’s because I have the limited hash version of the Apollo 2, and it only works with v2.0.7? Anything else I could try?

Does anyone know where I can download that version?

Thanks!

[jmpcrypto]

hello, I just received my apollo II and had it syncing with no problem for two days. I was able to access the dashboard as well with no problem. Then I saw that there was an update available so I updated, and ever since then I have not been able to access the dashboard through the web. I log into my router and its connected. I reflashed the SD card and I was able to get to dashboard for a short period until I noticed the dashboard freeze and then lost access. I have not tried plugging a monitor in directly into apollo yet cause I read that it'll only recognize the monitor at startup. I don't want to turn it off again if it is still syncing. Looking for some assistance thanks!

[bubbAJoe]

Hey everyone,
I’m a total newbie here, so please bear with me—and I’d truly appreciate any help you can throw my way.

I received my Apollo II a couple of weeks ago. Everything was working great until there was a power outage. Since then, whenever I turn it on, my unit’s fan is running at full speed, I can't access the dashboard, and the front LED stays off.

I tried flashing versions v2.0.6 and v2.0.5, but neither worked. Maybe it’s because I have the limited hash version of the Apollo 2, and it only works with v2.0.7? Anything else I could try?

Does anyone know where I can download that version?

Thanks!

AFAIK, 2.0.7 is not yet available in the public domain, only via OTA. Email support, they can probably supply it to you.

[dimascgm]

Hey everyone,
I’m a total newbie here, so please bear with me—and I’d truly appreciate any help you can throw my way.

I received my Apollo II a couple of weeks ago. Everything was working great until there was a power outage. Since then, whenever I turn it on, my unit’s fan is running at full speed, I can't access the dashboard, and the front LED stays off.

I tried flashing versions v2.0.6 and v2.0.5, but neither worked. Maybe it’s because I have the limited hash version of the Apollo 2, and it only works with v2.0.7? Anything else I could try?

Does anyone know where I can download that version?

Thanks!

AFAIK, 2.0.7 is not yet available in the public domain, only via OTA. Email support, they can probably supply it to you.

Thanks! But do you think that the issue is indeed the version? Or could it be something else?

[blackakashi]

Hi,

It might be interesting to ssh to the Apollo and look at the logs to see if any issue arise.