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

Hi, is 2.0.5 out yet? If so, can you please share the DL link? I'm running the Apollo 2 node so would need to reflash to that.

Hello Team, my Apollo 2 node consistently shows 31/32 node connections. Any idea why it cannot fully connect with 32/32?

I have the Apollo II and I upgraded the OS using Apollo BTC MCU2 and the issue was the same even before I upgraded the OS.

Is this on an Apollo BTC or Apollo II? If you upgraded the OS make sure you chose the right MCU image download, otherwise the miner wont get detected and you'll get this issue.

I have my node fully synced and opened port 83333 on my router
and this is the message I see "Waiting for the current miner status to match the desired one (Online)."

http://i.ibb.co/4YFDwdq/miner.png

any ideas on what the problem might be in this situation?

It's something like "Mined by a Solo FutureBit Apollo"...no these are ASICs, algo is hardcoded in the hardware itself there is no way to change the mining algorithm like a GPU.

Ok thanks. What’s the current default coinbase tag if I’m lucky to mine a block? And to confirm, there is no other way to customize the mining algorithm (besides having a unique wallet address)?

You can also read the apollo log file. It is in JSON format.

It would be fine if you add keyboard language selection into initialisation process. Or warn "do not use special characters in password".

Deleting of /opt/apolloapi/futurebit.sqlite restarts the setup again, fine.

Now it works. Thanks!

Awesome good to know!

Power usage is on the top where is says "BOARD SYS INFO" the last value on the line is the power usage (under P, wt)

Thats on our to do list and will add that as an option for a future update (customizing solo coinbase tag).

Hi did you use German characters for the password? Can you DM me an example so we can test if this is causing issues.

The futurebit user password (for OS login screen) is set to the web UI password you set during the web setup.

Usually you need to reflash your SD card if you cant login, but since you seem to know your way around ssh you can just delete the .sqlite database file in /opt/apolloapi and it will force setup again.

Hello,
I´ve start the Apollo II for first time and created the WEB password (with a german keyboard).
Now I can´t login tu the Website of my Apollo II.

ssh as root (futurebit123 worked well), changed password for user futurebit worked also well, but the WEB-password must be independed of system password.

How can I change the Apollo II WEB-password?

I'm sure it's somewhere but can anyone point me in the direction of how my futurebit works? Where are the sats that I earn, etc, etc. Seems to be running well but clearly I haven't figured everything out yet.

Hello Team, for solo mining on the Apollo 2, is it possible to manipulate any mining inputs like inscribing into the coinbase (ex “Chancellor on brink….” or maybe the extraNonce or anything else to customize and further randomize the hashes?

how do we check the power usage of the standard unit if we are running it via a raspberry pi or different computer? not sure how to read the terminal/command line results haha.

i got mine running yesterday, just wanted to confirm i was able to run the binaries for the Apollo II standard unit. i got it working on a $40 thinkpad 11e [it was a chromebook but i installed linux mint on it] so it should work on most setups.

Tor is notorious for sync issues. I would temporarily turn tor off and let the node sync then turn it back on.

Update issues have been resolved, so as long as you dont do a dist upgrade you should be fine with apt update/upgrade going forward (kernel is now frozen).

Hello FutureBit!
I received my apollo-2 full node systems about a month ago,
and it's been quite an educational journey!  I joined the
ocean pool and received my first payout with lightning.

However a few days ago the bitcoin nodes on both my apollo-2
systems (configured as TOR mode) lost connection to other nodes,
so they're stuck syncing blocks (~644000/844366).

Tor logs in /var/log/syslog are filled with messages like this :

May 22 04:49:35 futurebit-apollo-2 Tor[202872]: No circuits are opened. Relaxed timeout for circuit 123467 (a Hidden service client: Fetching HS descriptor 4-hop circuit in state waiting to see how other guards perform with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1348 similar message(s) suppressed in last 3900 seconds]
May 22 09:42:24 futurebit-apollo-2 Tor[202872]: We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [4454 similar message(s) suppressed in last 600 seconds]
May 22 09:47:18 futurebit-apollo-2 Tor[202872]: Failed to find node for hop #1 of our path. Discarding this circuit.

The internet connection is fine, and the miner continues to contribute
to the ocean pool.

I am able to use tor from other computers on my LAN.
Rebooting the apollo-2 does not help.

Tor version 0.4.6.10 is a couple years old.
How are updates managed?

Do you have any hints about this?
Thanks!

Should we immediately see accepted shares if it's working correctly? Still waiting for first share no matter what kind of wallet address is used

It's working now, thanks!