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

[heslo]

I'll try this soon and report back! Thanks!

Just a heads up, might want to edit your post.... cd /opt/apolloapi/backed should be cd /opt/apolloapi/backend..... you missed the "n"

[heslo]

Annnnd we are up and running! Update went well, took what I'd say is 20 to 30 minutes all up, just let it run in the background while I watched a YouTube video. Still haven't explored everything but the changes on the UI look great, the block history especially! Any issues and I'll be sure to send them your way.

EDIT: It's also nice the solo pool page stays showing stats even when not mining now!

Awesome update guys, great work!

[Block888737]

No issues with the update on my Apollo BTC. The CPU fan quit about 6 months ago, and the power connectors are slightly burned, but she keeps on trucking. Once my solo node arrives, she'll finally be allowed to rest.

[SysIO]

Updated in about 25 minutes via Ethernet.
Works well now, nice UI! 

[heslo]

Just looking deeper into the new software now and have seen there's a setting for different node software; very cool! Not that I have any intention in running Knots but the fact there's a choice is very nice

[jstefanop]

Annnnd we are up and running! Update went well, took what I'd say is 20 to 30 minutes all up, just let it run in the background while I watched a YouTube video. Still haven't explored everything but the changes on the UI look great, the block history especially! Any issues and I'll be sure to send them your way.

EDIT: It's also nice the solo pool page stays showing stats even when not mining now!

Awesome update guys, great work!

Yea we did major refactoring on the backend, the whole status system as well as logging and services have all been separated in the front end, so you can now start/stop all three major services (miner, node, and solo pool) independently

[heslo]

Annnnd we are up and running! Update went well, took what I'd say is 20 to 30 minutes all up, just let it run in the background while I watched a YouTube video. Still haven't explored everything but the changes on the UI look great, the block history especially! Any issues and I'll be sure to send them your way.

EDIT: It's also nice the solo pool page stays showing stats even when not mining now!

Awesome update guys, great work!

Yea we did major refactoring on the backend, the whole status system as well as logging and services have all been separated in the front end, so you can now start/stop all three major services (miner, node, and solo pool) independently

Absolutely awesome, brilliant work guys!

[jstefanop]

v2.1 has been pushed to all devices, still marking this as beta since its a massive update and there will probably be a few minor bugs but its currently stable across all our devices and beta group.

Change log and image links below for those that would rather update the image that way or if you have OTA update issues (MCU1 image still in the works and should have download link this weekend/early next week:

Welcome to Apollo OS 2.1

Our largest update to Apollo OS 2 since release! This release features major backend and front end changes, with a much more robust management of Apollo Core services including node functionality, solo pool, and miner services. New features include hashrate graphs to better visualize miner and pool performance, user selection of core clients, easy access to system and services logs, and much more!

v2.1 CHANGELOG

•⁠ ⁠Added new hashrate chart feature
•⁠ ⁠Major refactoring of backend services and API state engine
•⁠ ⁠Added user selectable core clients
•⁠ ⁠Added API/UI logs
•⁠ ⁠(RE)Added temperature settings
•⁠ ⁠Added block found monitor and celebration
•⁠ ⁠Various UI/Data fixes
•⁠ ⁠Better Mining Drawers
•⁠ ⁠Better UI responsiveness
•⁠ ⁠Updated JS packages (GraphQL, Redux, React, NextJS)
•⁠ ⁠Updated base OS packages and security updates

Image Releases:

Click on the image release links in below: (MCU1 Images will be uploaded shortly)

[Apollo II / Apollo BTC MCU 2 Download](https://www.dropbox.com/scl/fi/0kbv2diyaxs0z9skepwme/apollo-2-mcu2_121925.img.xz?rlkey=kedjwsu2gztu5390vbijxhp45&dl=0)

[Solo Node Download](https://www.dropbox.com/scl/fi/9cyrhyu1gzk6s6ob202wm/solo-node_121225.img.xz?rlkey=5awpw8xwr8gc5ef1dpldr7ipt&dl=0)


If you own an older Apollo BTC, please read SD Card flash instructions and identify MCU1/2 Devices with README below (not relevant for Apollo II units, they are all MCU 2 devices):

[README](https://mega.nz/file/dghWnKJC#J2kkpfH5RVKynf0OvuE5mKojXdUqAFCczHMyv6mDrM4)

SHA256 SUMS

**Apollo 2/Apollo BTC MCU2 Devices**

fad611085a2aaa44da65c9634a7688ddb2ed5f3f164f4906fc8ef5225b80352d  apollo-2-mcu2_121925.img.xz

**Solo Node Devices**

755da8ca8dcd0abf7200b41fb0d9ee9089ecd42d158d06e1d2726777c5eac673  solo-node_121225.img.xz

[heslo]

If we already forced the update for testing, is this a different build with any more fixes? I get it will show 2.1.0 in the GUI instead of 2.0.7 but has anything else changed?

[AQUARIUZ88]

hey everyone I'm reaching out for help with a futurebit apollo 2 full node that refuses to start solo mining,even though the node appears fully sycned and everythging is updated.

The node finished syncing to the current btc block height
Inside the miner tab the only active button is Start Miner-Restart and Stop are not available.
Press start miner does nothing no change in status,no hashing.
pool mining is OFF.
Solo mining is ON with a valid btc recieve address
firmware is fully updated

What I've tried

restarted the unit
verified block sync
check wallet address
disabled/enabled LAN access
updating all firmware modules
even considered wiping the device to factory settings.

symptoms
node=ok
miner status=not ok
miner refuses to initialize hasing
start miner button is inactive/ineffective
no error messages shown
current miner status never matches desired miner status

has anyone experienced anything similar SOS anyone

Does the miner work in regular pool mining mode? If not the issue is with the miner itself. Do you see the front light start flashing when you start/restart the miner?

Thank you for the reply.

I tested pool mining as suggested and get the same behavior.
Front LED flashes when starting/restarting the miner, but:

- Miner stays Offline
- Start Miner does nothing
- Pool mining also fails
- Node shows “connection refused”
- Miner cannot reach desired state

I reseated the miner controller and hashboard connections and confirmed the board powers on.

At this point it seems like the miner service / OS layer is corrupted rather than a solo mining config issue. I’m trying to avoid a full reflash, but open to it if that’s the known fix.

The miner light are flashing and when I perform to pool mine I get the same issue the node won’t start connection refused and the miner cannot find desired match.

[Hamster123]

v2.1 has been pushed to all devices, still marking this as beta since its a massive update and there will probably be a few minor bugs but its currently stable across all our devices and beta group.

Change log and image links below for those that would rather update the image that way or if you have OTA update issues (MCU1 image still in the works and should have download link this weekend/early next week:

Welcome to Apollo OS 2.1

Our largest update to Apollo OS 2 since release! This release features major backend and front end changes, with a much more robust management of Apollo Core services including node functionality, solo pool, and miner services. New features include hashrate graphs to better visualize miner and pool performance, user selection of core clients, easy access to system and services logs, and much more!

v2.1 CHANGELOG

•⁠ ⁠Added new hashrate chart feature
•⁠ ⁠Major refactoring of backend services and API state engine
•⁠ ⁠Added user selectable core clients
•⁠ ⁠Added API/UI logs
•⁠ ⁠(RE)Added temperature settings
•⁠ ⁠Added block found monitor and celebration
•⁠ ⁠Various UI/Data fixes
•⁠ ⁠Better Mining Drawers
•⁠ ⁠Better UI responsiveness
•⁠ ⁠Updated JS packages (GraphQL, Redux, React, NextJS)
•⁠ ⁠Updated base OS packages and security updates

Image Releases:

Click on the image release links in below: (MCU1 Images will be uploaded shortly)

[Apollo II / Apollo BTC MCU 2 Download](https://www.dropbox.com/scl/fi/0kbv2diyaxs0z9skepwme/apollo-2-mcu2_121925.img.xz?rlkey=kedjwsu2gztu5390vbijxhp45&dl=0)

[Solo Node Download](https://www.dropbox.com/scl/fi/9cyrhyu1gzk6s6ob202wm/solo-node_121225.img.xz?rlkey=5awpw8xwr8gc5ef1dpldr7ipt&dl=0)


If you own an older Apollo BTC, please read SD Card flash instructions and identify MCU1/2 Devices with README below (not relevant for Apollo II units, they are all MCU 2 devices):

[README](https://mega.nz/file/dghWnKJC#J2kkpfH5RVKynf0OvuE5mKojXdUqAFCczHMyv6mDrM4)

SHA256 SUMS

**Apollo 2/Apollo BTC MCU2 Devices**

fad611085a2aaa44da65c9634a7688ddb2ed5f3f164f4906fc8ef5225b80352d  apollo-2-mcu2_121925.img.xz

**Solo Node Devices**

755da8ca8dcd0abf7200b41fb0d9ee9089ecd42d158d06e1d2726777c5eac673  solo-node_121225.img.xz

Good Morning Everyone!

Wanted to briefly add that I updated both of my Apollo 2 Node/Miner units within the last 12 hours:
*Unit 1 (primary node unit used for my home mining network to solo mine) updated by flashing the SD card a few minutes ago and now running default Core node software with zero issues.
*Unit 2 I updated over WIFI last night (unit wired to WIFI network extender) and now running Knots node software with zero issues. The update process only took about 25 minutes total including reboot and reconnecting to the network on it's own. Seamless.

My primary Apollo 2 node unit is solo mining on my home network with all of my home mining units reconnecting after rebooting them to establish connection (after new software up set-up and running). The blockchain was already up to date so downtime was minimal. Very happy with the update and love the new functionality and interface. I am not very tech literate (no programming skills, etc.) so greatly appreciate the Futurebit set-up guides, this forum for information, and the great hardware.

Thank you!

[shaotai]

v2.1 has been pushed to all devices, still marking this as beta since its a massive update and there will probably be a few minor bugs but its currently stable across all our devices and beta group.

Change log and image links below for those that would rather update the image that way or if you have OTA update issues (MCU1 image still in the works and should have download link this weekend/early next week:

Welcome to Apollo OS 2.1

Our largest update to Apollo OS 2 since release! This release features major backend and front end changes, with a much more robust management of Apollo Core services including node functionality, solo pool, and miner services. New features include hashrate graphs to better visualize miner and pool performance, user selection of core clients, easy access to system and services logs, and much more!

v2.1 CHANGELOG

•⁠ ⁠Added new hashrate chart feature
•⁠ ⁠Major refactoring of backend services and API state engine
•⁠ ⁠Added user selectable core clients
•⁠ ⁠Added API/UI logs
•⁠ ⁠(RE)Added temperature settings
•⁠ ⁠Added block found monitor and celebration
•⁠ ⁠Various UI/Data fixes
•⁠ ⁠Better Mining Drawers
•⁠ ⁠Better UI responsiveness
•⁠ ⁠Updated JS packages (GraphQL, Redux, React, NextJS)
•⁠ ⁠Updated base OS packages and security updates

Image Releases:

Click on the image release links in below: (MCU1 Images will be uploaded shortly)

[Apollo II / Apollo BTC MCU 2 Download](https://www.dropbox.com/scl/fi/0kbv2diyaxs0z9skepwme/apollo-2-mcu2_121925.img.xz?rlkey=kedjwsu2gztu5390vbijxhp45&dl=0)

[Solo Node Download](https://www.dropbox.com/scl/fi/9cyrhyu1gzk6s6ob202wm/solo-node_121225.img.xz?rlkey=5awpw8xwr8gc5ef1dpldr7ipt&dl=0)


If you own an older Apollo BTC, please read SD Card flash instructions and identify MCU1/2 Devices with README below (not relevant for Apollo II units, they are all MCU 2 devices):

[README](https://mega.nz/file/dghWnKJC#J2kkpfH5RVKynf0OvuE5mKojXdUqAFCczHMyv6mDrM4)

SHA256 SUMS

**Apollo 2/Apollo BTC MCU2 Devices**

fad611085a2aaa44da65c9634a7688ddb2ed5f3f164f4906fc8ef5225b80352d  apollo-2-mcu2_121925.img.xz

**Solo Node Devices**

755da8ca8dcd0abf7200b41fb0d9ee9089ecd42d158d06e1d2726777c5eac673  solo-node_121225.img.xz

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!

[oneeighteen]

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!
[/quote]



Mine got stuck at 30% too. I refreshed the webpage and started the update again. It started at 30% and then it didn't take long to finish.
Working ok now!

[shaotai]

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...

[BitcoinSHARK]

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

[shaotai]

@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

I ran it locally and noticed it had some errors getting repos and some locked files. Still was stuck at 2.0.7
Then ran it remotely via ssh and after the reboot, it seems to have finally worked.  Both web GUI are up to date to 2.1.
Thanks for the suggestion!

[jstefanop]

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...

This is a caching issue, you need to close the web page or clear cache if it still shows the old version.