Topic: Official FutureBit Apollo BTC Software/Image and Support thread - page 4. (Read 50685 times)

Thanks for your input guys. It looks like I was worried about nothing. I searched why I had made that note and found it was a very old issue with a much earlier version but was fixed in 2021. I found the below note in updated post #3 on page one of this thread.

Release 7/31/21
-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

Nice to see a more recent video from someone using the Apollo node.

Cheers!

https://www.youtube.com/watch?v=uoDD1LEI4DY

Hi BrokenTractor,

When the MicroSD is flashed it is flashed in the correct OS language (Linux) along with the new default Apollo v2.0.6 OS and will overwrite anything currently on the MicroSD your aiming at (so make sure the target MicroSD has nothing on it you want to keep). The process doesn't format the NVME node drive or do anything else except you will lose any "special" data you might have added in the "Bitcoin node configuration" under the "Settings" menu - things such as "listenonion=0" or "addnode=xxx.xx.xxx.xx", etc. At least that was my experience.

After you flash the new card just replace the old card with the newly flashed card and insert it into the appropriate slot and boot up. At this point you will need to re-enter your information such as wallet address, user info, etc. - the same info you were previously using is what I would suggest unless you want to change it now. After that, everything will start up and your node will pick up where it left off (or catch up first). That's it!

Cheers!

Hey PennyBit,     
I had made an old note that loading a newly flashed micro SD card would format the SSD card when it loaded for the first time. Has this behavior changed with v2.0.6? Does it now check first if you already have data on the SSD before trying to format it?
When you started v2.0.6 with the newly flashed micro SD card did it format your SSD card as well or do you still have all your Bitcoin Data intact?
I want to do it the way you did, since I have a new Micro SD card I want to use, as long as it doesn’t wipe all my node data. And if I take out the nvme SSD card before first startup will it try to create a data directory on the system disk instead?

the ports allow incoming connections from other nodes.  the bitcoind attempts to open those ports.  It pushes out to other nodes to connect using a master list in a node database.  Once established the bitcoind creates P2P node connections. At this time it opens the incoming ports.  If successful you will see your node count increase.  If your providers is blocking incoming connections it may be futile and at the mercy of your provider.  Some routers close the ports for firewall purposes which is why you log into the router to open the ports.

The most important thing for all apollo users to do is look at their log.  media/nvme/Bitcoin/debug.log.   It gives loads of information on the performance of your node and status.  You can see the connections made to other full nodes or block only relays.  You can see startup and shutdown sequences.  When the bitcoind node program starts up you will see the sequence of events including the attempt to connect to the outside world.  If it fails you should see the errors there.  Your node is constantly connecting to new nodes around the world on the P2P network(decentralized).  Adding and dropping connections.  In the node tab in the GUI you can see the different nodes and addresses your apollo is connecting to and these change over time.  What is fun is to see when you connect to another apollo node.

This log also addresses the question in a previous post about the node software using the system drive for bitcoin data storage instead of the nvme drive.  during startup it defaults to the system drive for bitcoin data storage files and then reverts to the nvme drive for bitcoin data when it is found.  Described in the logs.

Hi
So unfortunately due to my internet provider and 4g/5g wireless restrictions in the UK I cannot open ports on my Wireless router 
I was wondering what opening the port actually does ??
also would it work if I got a copy of the connections from a miner that had 64 connections and copy/paste them into my miner manually, would that work?

otherwise super impressed with this unit and I am more than happy to let it run with the restrictions that I have at the moment 

Thanks in advance people

SD

My choice was to download the update directly at https://github.com/jstefanop/apolloapi-v2/releases and then simply re-flash my 3 node machines back-to-back on new MicroSD's. It's pretty much risk free and it only took about 45 seconds on each machine to reconfigure with the minimal settings. The upside to this is that I can also keep the large update file on-hand for any future needs if necessary. If this version doesn't work out I still have the old v2.0.5 MicroSD's as well as the backups for each machine. So far so good on v2.0.6.

Cheers!

That is my thoughts as well. I am mining with 2 other miners using the node as well, all 3 using diff wallets and no problems. So no reason to chance updating it.

I just rebooted the node and everything is up and running on v2.0.5.  I'll stay here since my node has been running well and I don't want to fix whats not yet broken on the node until these update bugs are fixed.  I don't want to have to go through reflashing a good memory card.

Same thing happened to Red Panda Mining.  He just posted a video on it, go check it out if you want.  He wound up just flashing the memory card and that worked.

Ok,  

I saw the indicator telling me I can update to the new version.  My Miner and node were all stopped.  I clicked on update and the download began.  However, at 30% My node started up and my update is stuck at 30%  Now its been a few hours, not 30 minutes.  What is stuck and why?  How do I fix this?  It says don't shutdown or restart until update complete.

I upgraded my gen 1 node - I just use http://futurebit-apollo-btc/miner to access it - maybe that will work for you

I just ran my gen 2 node and that update went perfect. I rebooted the old node but still no local access. The node and additional miner are running though as I can see them in the solo mining dashboard. I just can't access the dashboard for the old node remote or direct.

Can you reboot it remotely? Wouldn't suggest doing an update unless you can physically access it in case the update fails and you need to reflash the SD card.

I updated my original BTC node with latest update. I now cannot access localhost:3000 or monitor the node remotely. Any tips?

Just updated my three node units (all solo mining to one node) with no issues. Well done and thank you for this wonderful product!

Thanks!  Your team replied to me today. I'm going to replace the switch myself.

If you dont use solo mining with multiple devices/addresses or have seen any of the graphQL 32 bit errors then you are probably good, updates always include latest security and package patches for the UI though.

For us having no issues running v2.0.05 is there any reason to update to v2.0.6 and just wait for v2.1 ?