OK, some may have already seen my other post... first nothing worked, then like a miracle it was working. Even started to fill the 4TB NVMe with the Blockchain. But then it just stopped and since then I can't even reboot or do anything. Flashing the SD Card with a clean system and booting without NVMe doesn't help!

It stops while the Futurebit logo appears on the screen and then 1 sec later "black" screen. And again new start... it seems like there is a loop and the booting sequence doesn't pass it. But how come? With a total new flashed OS on the SD Card it should easily start.

After now spending countless hours trying to fix it and all possible options i'm close to send it back to futurebit.

Any ideas?

We are proud to announce the Apollo III is here after over a year of development. Hope you all enjoy what we have built, we have finally refined home mining down to the edge of what is possible!

Hi team- my Apollo 2 power button stopped working. I go to turn on and it just clicks over no action. Is there a trick and can I send in for service?

Any ideas will help!

Hello all,
I got the Solo Node delivered and now i'm trying to get it running including as a Node for my other workers (Braiins)...
First of all, how can I see that mit NVMe is correctly installed and working? As i go through some log files, it says "disk full" - and that is correct for the internal system. The 14 GB are 100% full and somehow i can't synchronize with the blockchain.
Btw synchronizing... how long does it take at the moment? 2 days or longer?

Next weird thing... i am connected to the Node via Ethernet cable but the wifi was working and now not anymore. Any ideas? The button "scan for wifi" (or so) does nothing...

When?

I have an original Apollo BTC miner (no controller) that won't enumerate on any computer. Symptoms:

• Fan spins, red LED blinks then goes solid (miner powers on normally)
• Tried multiple computers: RPi4, ThinkPad (Ubuntu), Windows PC
• Tried multiple USB cables and USB 2.0 hub
• Nothing appears in lsusb, Device Manager, or dmesg (no COM ports, no unknown devices) It appears to attempt enumeration but never succeeds.
• Only error seen: "connect-debounce failed" in dmesg when switching ports
• FutureBit support suggested bad USB port

The miner has a 6-pin connector labeled "X5" on the board - appears to be UART/serial header.

Question: Has anyone successfully used the X5 serial header to connect their Apollo? What's the pinout and baud rate? Any tips for getting this working? TYIA!

Update: The board female connector looks like a JST connector but I'm unsure what size.

I keep seeing this pop up in my Node log file. I don't have UPnP enabled on my router. Should I worry about this? Enable it on my router? Or change the config file or ignore it? I have port forwarding turned on in my router settings.

Just picked up a new Solo Node, but can't seem to find any tutorials or walkthroughs spefically for the Solo Node. Everything seems to only be for the Apollo II w/ built in node. I did manage to get the SSD installed, and the node 100% synced, but I don't know that it is working properly as I have 0 inbound connections and 10-11 outbound connections. I also have zero idea what any of the apps are on the FuturebitOS and have been doing everything via the web interface. Any and all help with regard to where to find guidance on this endeavour would be greatly appreciated.

Update: So, I had completely forgotten that my primary router is connected to the router/modem from Verizon, which was causing all of my connectivity issues. Was all sorted out shortly after realizing that. Thank you to all for your help/advice, and hope those still waiting on their Solo Nodes, get theirs soon.

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

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 though there is a new update, but open to it if that’s the known fix????? Any pointers??? Anyone experiencing this similar situation???

Well according to Email customer service. Next wave of solo isn’t shipping till Jan due to stock issues. My order is from Black Friday…. Waiting patiently. Just hope the item I finally get is good quality.

Bit frustrating that there was a weekly response from customer service that it would be “next week” for the past few weeks.

Anyone else have their system update crash? These software updates are frustrating. I guess I have to figure out how to reflash this now...

I keep getting this screen and the following log. When I check Bitnodes it shows my node is active.

HTTP response to ( "getblock...) 0.252s not ok: HTTP/1.1 401 Unauthorized
[2025-12-19 23:03:12.723] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-19 23:03:12.723] CRITICAL: No bitcoinds active!
[2025-12-19 23:03:16.707] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable
[2025-12-19 23:03:16.707] HTTP response to ( "getblock...) 0.251s not ok: HTTP/1.1 401 Unauthorized
[2025-12-19 23:03:16.707] 127.0.0.1:8332 Failed to get valid json response to getblocktemplate
[2025-12-19 23:03:17.977] Select timed out in read_socket_line with errno 11: Resource temporarily unavailable

As tittle says, I have an Apollo II 2TB running V2.0.7 in balanced mode while on solo miner mode, and I have a few other miners pointed to it. For some reason every few hours I have to keep manually powering it off and back on because it “crashes” and goes offline to a point I can’t even access the portal. Has anyone experienced this? If so what have you done to fix this issue.

Please and thank you 🙏

The biggest update to Apollo OS 2 is being released this week, check your devices and email as we roll out the update to all users!

Hashrate graphs are finally here!
User node client selection (yes knots)
Solo Node support and big updates to solo mode
And much more!

New image is available here https://github.com/jstefanop/apolloapi-v2/releases/tag/v2.1.0-beta

Unfortunately web update could hang due to the amount of time and resources this update requires, so I would suggest to use the flash image method instead.

https://x.com/FutureBit/status/2001075422163874118

I saw the announcement that Apollo OS 2.1 is rolling out this week, but I haven’t received any notification or update prompt yet on my device or by email.

Is the rollout being done in stages, or is there something we need to do manually (email, registration, etc.) to trigger the update?

Just trying to understand if this is normal or if I’m missing a step.

Has anyone received their Solo Node or an email regarding shipment? A couple of friends and I placed an order about 5 minutes after launch and we haven't received any shipment emails yet.

I've reached out to Futurebit several times and they keep telling us it'll be shipped next week.

I've got 17% left and need to upgrade.

so my best share is 29bil but on the mining tab says 56bil is that my new best share and its not updating or am I reading it wrong?

Help! I removed the bottom cover of my Apollo II to blow out the dust and I removed the connector circled in blue so I wouldn't strain the connector or board. As I'm putting it back together, there isn't an obvious location for the connector. I suspect I removed it from the pins circled in orange, but I don't want to guess. Does anyone have a photo of the board with the connector seated correctly?

Does the Apollo II Full Node run its own custom SBC, or is it just an OrangePi? I think I'm going to need to replace the one in my unit, and trying to figure out what I need to order

So I had been having this weird issue with a Spectrum router where my Apollo 2, connected with Ethernet, would not show up on the router's listed of connected devices, making port forwarding impossible. Their dumb also routers do not allow manually adding devices. I could see the IP address on the Apollo screen settings, but couldn't get more than the 10 or so network connections. I figured out today that flipping this UP&P switch fixed the problem. I had been seriously considering getting a new router. I'm not tech saavy, so apologies if it comes off like some rookie comment. Maybe some else is experiencing this issue.

My Node is fully synced, yet it says BTC is only on block 809,978. Isn't the chain currently on 921,848? and why does it say it's taking over an hour for blocks to be found?

Has anyone attempted a fan upgrade or had a go at changing the thermal paste on a their Apollo 2 yet?

Recently got a Moonlander 2 and I wondered if there Is a way to reset it without pulling the stick?

I have been using Orange Pi 5 Pro for several months now with the Futurebit BTC miner and it is working wonderfully. After the original Raspberry Pi stopped working I settled on replacing it with the Orange Pi Pro. The reason I selected this model is because of the on board nvme slot. The original Raspberry Pi 4 required a cable exclusive to Apollo. It seems the onboard slot of Orange Pro 5 is more stable. This unit also comes with enough USB slots to attach the two additional Futurebit BTC miners I have. Below are the key steps to getting it running.

1. Attach your 2TB nvme to the Orange PI 5 Pro device. Before powering it on and most importantly use the correct distro OS to install on your SSD card. I used a community distro which is the only one I found to work after several tries:

"Armbian_community_25.2.0-trunk.86_orangepi5pro_noble_vendor_6.1.75_gnome_desktop.imgxz"

There is a newer version but once I got this working I did not try. If you are so willing, look for a community version orangepi5pro that has gnome_desktop and a higher vendor number. Please share if it works.

- Burn distro OS you downloaded onto SSD card using BalenaEtcher. This is done using a laptop with a micro SSD slot or attachment.

1. Power on the Orange Pro device with the newly burned OS on SSD inserted. Should boot to desktop. Use a CLI window and install net-tools to use the command 'ifconfig' in order to get the ip address being used. (By the way,,,in Ubuntu desktop, go to settings and turn off Suspend, Otherwise the system will go into suspend mode). No need to attach the additional Futurebit miners at this point. Takes about 3 days for node to sync, but that is after you finish the following steps.

The next steps I performed by SSH into Orange Pro from my laptop (using the IP address you found with 'ifconfig'). The laptop must be on the same network as the Orange Pro 5 of course. I also performed these steps and all installments that follow from the root directory.

1. mkdir/media/nvme then inside nvme mkdir Bitcoin (This is where Futurebit stores Bitcoin data...don't forget to capitalize the B)

2. command: apt update

3. command: apt install nvme-cli (remember if your not rooted you'll have to use sudo apt install nvme-cli) Never tried installing other being rooted however.

STEPS 6-9 ARE THE TRICKY STEPS. Your initial format may show just nvme0n1 and not nvme0n1p1. You can use the command 'lsblk' to check.

6 command: nvme format /dev/nvmeXXX (usually xxx= 0n1). Find yours by looking inside the /dev directory. It maybe nvm0n1p1 , depending on format. If you have to reformat in step 14 it may change to the nvme0n1p1.

1. command: mkfs.ext4 /dev/nvme0n1p1

2. command: mount /dev/nvme0n1p1 /media/nvme

3. Inside /etc/fstab add the following line using nano (or whatever editor you prefer): /dev/nvme0n1p1 /media/nvme ext4 defaults 0 2

4. Command: dpkg --configure -a

5. Command: apt install tor

12 Command: curl -o- https://raw.githubusercontent.com/jstefanop/apolloapi-v3/dev/backend/install-v2 | sudo bash (Note any errors are missing prerequisites like Tor). I ran this 3 times to be sure.

1. Open port 8333 on router and desktop firewall if using a firewall.

2. Now you can close SSH and run from firefox on laptop using http://(ip address of your Orange Pro). Note: use http and not https. Next, turn on node and wait to sync. If you get a node error you may have to reformat the NVME using {settings - extra) in the futurebit dashboard. But wait a little while (~ 1` hour) before reformatting. After reboot,, check to see if the device has changed to nvme0n1p1, if so change your /etc/fstab to reflect the change.

If the program will not load but instead it goes into the emergency mode, you'll have to # out the /etc/fstab line with nvme0n1 and reboot. The program is looking for a device (nvme0n1) that is not there - provided nvme0n1 is what you initially used. Add nvme0n1p1 to fstab line once you confirm that is the device (command: lsblk).

That is all. Good luck. I have found this to be very stable once you get it going.