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

[n0nce]

Hello everyone,
is the port the same everywhere in the world?
I tried to give the device permission to find the port itself.
I got a port 6100? Which port is the right one in Europe?

Have read that the port 8333 should be correct.

It's always port 8333. Bitcoin doesn't care about your location.

I also only have a maximum of 10/32 connections.
What are more connections good for?

More connections means you're seeding the blockchain to more users / nodes, so it's always good to have many connections. I have typically over 100 on my node (not an Apollo though).

The miner can only mine 3Th. It doesn't matter, doesn't it?

Mining has nothing to do with the node software running on the device. It's just 2 programs in one box in the Apollo. You run a full node and a miner. Many full nodes don't mine, so the hashrate has no impact on the number of connections, no.

Connections are important but whether there are 10 or 30 connections should not burden such a "small" miner?! Small and  sweet...
What is the reason?

No, that's not a large amount of connections, I don't think the software will allow to have more connections than what it can handle.

[gt_addict]

Just noticed this on my Apollo.

The "DISK /MEDIA/NVME USAGE" says "391.61 GB/915.89 GB" but the node dashboard says its using 415.65 GB.

Are the two meant to be the same or am I missing something. How can the blockchain be using more than the OS says it is??

[mario312]

I just recd mine and plugged it in.  It worked fine for a few minutes.  When I changed the setting to allow me to edit the performance mode, I was prompted to Save & Restart.  The machine won't restart even with a hard boot.  Suggestions?

How do you do a hard reboot?

[mario312]

Solid RED led after startup and one flashing green led on the board, on the last unit that will not run, seems to be bricked.

Did you figure out what caused the solid red, I think I'm having the same problem, initial rapid red then stays solid red, green led on board. Tried flashing the card, tried a brand new card in case it was the card, no changes.

[Gags]

How do you do a hard reboot?
[/quote]

There's a button on the bottom, I think that's the reboot Button.
But I'm not Sure....😁

[mario312]

Update:  I just went and checked out the hashboard #1 unit and there are none of the yellow lights that are normally flashing on the bottom of the hashboard.   The LED is solid red and the unit is cool to the touch.     I will be away for an hour or so, and I will it sit as is incase any logs need to be pulled.

Did you figure out what was causing this?

[Gags]

Hey..
Now the same funny Thing happend to me...
The Start screen password change 'over night' ...
Is this a Firmware problem or could this be a attack from the internet.

I got 2 full node miners an it happend to both of them.

Update
Problem solved...
Now I tred it from another Device and there is no Login Problem.
Maybe ist the Problem (Login) with the Cookies and/or the Browser.
 


And  i Got another Question to jstefanop
What's about Stratum V2?
Is it possible on a apollo or is it a project for the future?
I tried but the miner dont connect with V2 Adress to the Slushpool...

Thanks....

[Tempestblack]

OMG...OMG...OMG...@jstefanop ...I just got her up and running and she is like is Gorgeous...Gorgeous...Gorgeous... Thank you bro for sharing this astounding and wonderful invention and creation with us all... in my book you be a Crypto God... period!!!! I have not touched a Linux-based desktop or operating-related system in years so I am like wandering in a dark forest...lol...hoping not to blow myself up...lol...  ok so I have a question... I know there be a warning and advisement about how to update the system correctly so that one does not wind up bricking the system...I need advice and direction as to how to proceed to update the system without stepping on a land mine and bricking her... look forward to your response or someone from your team...

For everyone else...this man and his team are gods...this baby...this device is sheer sweetness and perfection as is...Nuff said!!!...

[macpilot]

- Regarding the bitnodes data:

I use bitnodes to validate that my node is reachable and I get the following response (all good)"

X.X.36:8333 /Satoshi:0.21.1(FutureBit-Apollo-Node)/

The response shows that everything is  good. However is there a way to change the FutureBit-Apollo-Node string? I don't think I want to advertise what software the node is running as to reduce the attack vector.

I am using the firewall to prevent all communication from other ports to the miner, but still there's potential risk that someone could try to exploit bitcoind through the open port in an attempt to break out to ubuntu root.

Are my fears unfounded? Thanks

(also on the same line is there a way to update ubuntu to the latest security patches? I don't want to run an update and risk breaking everything. The miner runs like clockwork so the less I have to mess with it the better.

Also, should I holdoff on installing TOR and LND on my own? how far is the next update :-)?

Finally I think I want to replace the 500GB for a TB, any recommendations on which one to get that will provide the performance and years of worry free operation? :-)

Thanks, I really like the miner, it's awesome!

J

[Gags]

@ Tempestblack:

I know there be a warning and advisement about how to update the system correctly so that one does not wind up bricking the system...I need advice and direction as to how to proceed to update the system without stepping on a land mine and bricking her... look forward to your response or someone from your team...

1.Download the image on https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q
2.Shut down your miner
3.Put out the SD Card (on the Bottom)
4.Put the SD Card in your PC-Slot
5.Download a Iso writing Sowtware (like Rufus, etcher or other)
6.Open the software an klick on the Downloaded Image (apollo-btc_310721.img (Step 1))
7.Klick start and wait for a couple Minutes
8.After complete put the SD Card in the Miner slot an start your Mner.
9.Start the browser and put the IP Adresse in...follow the steps and its done.

The same you can read on the first Side of the Post.


____________________________________________

Apollo BTC SD Card Image/OS Download and Install

Folder for all Apollo BTC Image Releases: https://mega.nz/folder/ZlxnwYZb#ZN77cDAcXa6dN_2QKSdT_Q

Release 7/31/21

d6f820869268383883db4741dcfcade8f57ad1a1c20c359fd7a3015c78ffe3dd  apollo-btc_310721.img.xz

-Updated Apollo UI to latest 0.3.1
-Image no longer wipes SSD if it detects it has already been formatted
-Added additional swap memory to prepare for Lightning network/block explorer apps
-System level fixes/tweaks for stability


Initial Release 5/14/21

c5dfeb7812e43df64fac2fd4dbc929ec7c78f6df513bed0d8aba81a6573bec7e  apollo-btc-14-05-21.img.xz



SD Card Flash Instructions:

• Download image linked above, verify SHASUM is correct
• Decompress the image (should have just a .img extension when its done full size ~7GB when decompressed)
• Use an easy cloner tool like etcher (etcher.io) or dd etc if your know what your doing
• Insert SD card in your computer, select the the decompressed apollo.img file, and select the SD card you inserted
• Flash away...this will return your SD card back to stock state

[n0nce]

Is there a way to change the FutureBit-Apollo-Node string? I don't think I want to advertise what software the node is running as to reduce the attack vector.

I am using the firewall to prevent all communication from other ports to the miner, but still there's potential risk that someone could try to exploit bitcoind through the open port in an attempt to break out to ubuntu root.

I someone finds an exploit in Bitcoin Core, it should make no difference if your node is an Apollo node or not; they're not running anything custom or so when it comes to bitcoind; just drivers and stuff for connection to the miner / hashboard are custom. So your attack vector isn't any different if it's an Apollo unit or another machine; everyone would be equally affected by a Core bug. However, for privacy it would be indeed nice to not tell everyone what machine you have; after all, this leaks that you're mining. Mining is banned in some countries for example or requires a permit since it's seen as a business and stuff like this. So I agree it would be good to be able to turn it off.

Finally I think I want to replace the 500GB for a TB, any recommendations on which one to get that will provide the performance and years of worry free operation? :-)

Usually any NVMe SSD with 1TB should work fine. Samsung m.2's are very popular, and just a bit more expensive than the cheap stuff. Or Western Digital.

[Biffa]

- Regarding the bitnodes data:

I use bitnodes to validate that my node is reachable and I get the following response (all good)"

X.X.36:8333 /Satoshi:0.21.1(FutureBit-Apollo-Node)/

The response shows that everything is  good. However is there a way to change the FutureBit-Apollo-Node string? I don't think I want to advertise what software the node is running as to reduce the attack vector.

You can change the string that says "FutureBit-Apollo-Node" in your conf file

Its called the Custom Agent name.

This is from my .bitcoin/bitcoin.conf file

Code:

#Custom Agent Name goes here
uacomment=To-The-Moon

So mine looks like this:
/Satoshi:22.0.0(To-the-moon)/

BTW this isn't my Apollo, this is my Linux node that I've run for years. My apollo nodes is turned off (I've already got a node so don't need another at my house)

[philipma1957]

- Regarding the bitnodes data:

I use bitnodes to validate that my node is reachable and I get the following response (all good)"

X.X.36:8333 /Satoshi:0.21.1(FutureBit-Apollo-Node)/

The response shows that everything is  good. However is there a way to change the FutureBit-Apollo-Node string? I don't think I want to advertise what software the node is running as to reduce the attack vector.

I am using the firewall to prevent all communication from other ports to the miner, but still there's potential risk that someone could try to exploit bitcoind through the open port in an attempt to break out to ubuntu root.

Are my fears unfounded? Thanks

(also on the same line is there a way to update ubuntu to the latest security patches? I don't want to run an update and risk breaking everything. The miner runs like clockwork so the less I have to mess with it the better.

Also, should I holdoff on installing TOR and LND on my own? how far is the next update :-)?

Finally I think I want to replace the 500GB for a TB, any recommendations on which one to get that will provide the performance and years of worry free operation? :-)

Thanks, I really like the miner, it's awesome!

J

. get a crucial i swapped to one it is good.


https://www.amazon.com/dp/B089DNM8LR?

94 bucks and you are done for years to come.

[crypto_curious]

- Regarding the bitnodes data:

I use bitnodes to validate that my node is reachable and I get the following response (all good)"

X.X.36:8333 /Satoshi:0.21.1(FutureBit-Apollo-Node)/

The response shows that everything is  good. However is there a way to change the FutureBit-Apollo-Node string? I don't think I want to advertise what software the node is running as to reduce the attack vector.

Advertising bitcoind version (0.21.1 in your case) is harmless. Every bitcoin node out there advertises its version so it can efficiently communicate with other compatible nodes. However, when you reinstall system, "FutureBit-Apollo-Node" string will disappear and your node will become generic bitcoind. This setting is configurable somewhere in bitcoin.conf, read the docs for bitcoind if you want to change it or keep it after reinstall.

I am using the firewall to prevent all communication from other ports to the miner, but still there's potential risk that someone could try to exploit bitcoind through the open port in an attempt to break out to ubuntu root.

You assumed bitcoind is running in Apollo as root? I don't think that's the case. You can verify this in ssh session, just run htop.

Are my fears unfounded? Thanks

I suggest reinstalling OS on Apollo, see below. You can run bitcoind as a separate user (to decrease escape risk) with generic version string, that's what I do.

(also on the same line is there a way to update ubuntu to the latest security patches? I don't want to run an update and risk breaking everything. The miner runs like clockwork so the less I have to mess with it the better.

That was my very concern when I first put my hands on this machine. I have reinstalled Armbian Ubuntu (default system in Apollo) to Armbian Debian, headless, ssh access only. See my post with details:
https://bitcointalk.org/index.php?topic=5340015.msg57531106#msg57531106

You can do something like that. For me, not applying security updates on Internet-exposed machine is a big no-no. That's why I reinstalled. Since this post, I upgraded system to latest Armbian-Debian 11, did even more Telegram stats, it's been running great. Also I moved it to another country, so I am bitcoin node operator in two countries now

Also, should I holdoff on installing TOR and LND on my own? how far is the next update :-)?

Finally I think I want to replace the 500GB for a TB, any recommendations on which one to get that will provide the performance and years of worry free operation? :-)

If you decide to go reinstall route, you have endless possibilities. I have 1TB USB spinning HDD connected as a node drive, formatted to Btrfs, so I have checksum warnings, had this drive already so cost was free. If you need to have it nice and tidy without extra equipment next to it, as it was, just buy any 1TB SSD, if will be all right. Bitcoind is barely using SSD bandwidth and speed anyway. Have fun

[n0nce]

~ snip ~

Interesting, you're the first one I come across that reinstalled the OS from scratch on an Apollo. I'm wondering then, how you got the miner working? I understood that we're not supposed to do anything with the system, not even package upgrades, since it could break something in the driver for the hashboard or something like that.

[Tempestblack]

This is for @Gags... Thank you for your post it is awesome to see other members chime in and be helpful to us noobs... lol... To @philipma to you bro I dig your videos and follow your hardware reviews and recommendations and yes I agree let's all go buy I TB crucial NVME cards and replace them in these beautiful Futurebit miner/nodes cause yea I can see the current 500GB drives not sufficing...this is in no way taking away from the beautiful creation by @jstefanop and his team... ideally he will in future releases install the larger 1 TB size NVME cards for due to Bitcoin size the 500 GB will not suffice within 2 years time... by the way philipma a question I pose to you is whether to clone our node drive we have installed currently or to start a fresh node install on what would be the new 1TB drive...and finally @crypto_curious thank you as well for your post every bit of input from the membership is appreciated

To the man who is at the heart of this all...JSTEFANOP...I cannot stop praising you and your team's creation...it is just gorgeous and the Node and Miner Dashboard are just awesome to view and to take in the information displayed on them...please keep up the outstanding work...you have gained a lifelong devotee and client...I so look forward to the second miner that I just ordered and hopefully expect delivery by year's end...and of course, look forward to seeing what new and amazing devices you and your crew design in the near future...

[dwood443]

rebooted my two miners today and both not showing stats and says inactive in web GUI?. Strange as these have been running just fine for the last couple months. But solo.ckpool shows they are actively mining. Both on 0.3.1 firmware. The node status still shows up too

Just an FYI if John still working on a fix

EDIT, I did a miner restart in the Web GUI and stats showing again. When I first rebooted I powered off at the unit because I could not access via IP (router upgrade)

[kyle15]

Any news on updated miner binary?

[jstefanop]

This is for @Gags... Thank you for your post it is awesome to see other members chime in and be helpful to us noobs... lol... To @philipma to you bro I dig your videos and follow your hardware reviews and recommendations and yes I agree let's all go buy I TB crucial NVME cards and replace them in these beautiful Futurebit miner/nodes cause yea I can see the current 500GB drives not sufficing...this is in no way taking away from the beautiful creation by @jstefanop and his team... ideally he will in future releases install the larger 1 TB size NVME cards for due to Bitcoin size the 500 GB will not suffice within 2 years time... by the way philipma a question I pose to you is whether to clone our node drive we have installed currently or to start a fresh node install on what would be the new 1TB drive...and finally @crypto_curious thank you as well for your post every bit of input from the membership is appreciated

To the man who is at the heart of this all...JSTEFANOP...I cannot stop praising you and your team's creation...it is just gorgeous and the Node and Miner Dashboard are just awesome to view and to take in the information displayed on them...please keep up the outstanding work...you have gained a lifelong devotee and client...I so look forward to the second miner that I just ordered and hopefully expect delivery by year's end...and of course, look forward to seeing what new and amazing devices you and your crew design in the near future...

Thanks that means a lot! Of course I have this whole community to thank just as much, none of all this grass roots non-VC funded work would be possible without all of you. Now the next step is to get the Apollo and devices like it to millions of BTC users, we need projects like this to scale if we want to take Bitcoin back from the institutional grip thats starting to take hold.

Tweet at all the influencers, drop emails to crypto news sites etc...no one has really covered us yet and we dont have a budget to spend 10s of thousands on PR.

[jstefanop]

Any news on updated miner binary?

Should have something by end of the week.