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

The first thing in the "idea / guess" category would be heat - but since you're in ECO mode I doubt that's an issue unless there's an air flow problem for whatever reason. My second thought is related to a post from jstefanop back on 8/17/24 (Post #2398 & #2399) regarding a bad batch of power switches that are causing some issues on a small number of units. Perhaps that's the culprit? I also remember reading somewhere about loose cords not inserted 100% into the back of the units causing some grief. Outside of that, I'll go out on a crazy limb and say maybe check the seating on your memory cards underneath the full node unit (just a guess). Wish I had more to offer. Cheers!

Hi all - has anyone run into this issue? I've had my Apollo II for about a month.  Working fine for the first few weeks.  Over the last week and a half.  3 times the node and miner both stop.  I monitor it using remote desktop.  Unfortunately since I lose access to it when this happens I cannot reboot it from where I'm at.  When I get home I have to physically turn it off with the power switch and back on again to get it back up and running.  The first time it happened was about a week ago.  Then again yesterday and again today.  When running the miner is set to eco mode.  Any ideas?

Thank you!

When running a single hash board, my particular Apollo 2 runs an "average" of 5.5 on ECO, 7.0 on BAL, and 8.5 on TURBO. Of course, by adding two more Apollo standard units I see an "average" of 16.5 on ECO, 21.0 on BAL, and 25.5 on TURBO. Although my hash rate does vary up and down throughout the day from hour-to-hour and minute to minute, the average stays about what was stated.

Quick question. I just connected my new apollo 2 node and while its syncing I have it mining to my old node but my hashrate is around 5.3-5.5. Is it normal for it to be below 6 TH/S?

Good news! After some work and digging into the problem, I’m excited to share that I’ve developed a Python-based script to control the Apollo II miner. I faced concerns about the miner not stopping even when the mining program was closed, but Futurebit has provided the apollo-helper proprietary binary, which can put the device into a reset state where it stops any work. This way, when the miner is not mining, power usage drops to almost zero, as it should. Currently, this solution only works on Arm64 boards because the apollo-helper binary is only available for that architecture. Windows or Linux AMD64 are not yet supported. Once Futurebit releases their binary for these systems, I will be happy to update my script.

The script I’ve created monitors the temperature using a TEMPer USB thermometer and can automatically start or stop the mining process based on configurable temperature thresholds. It also supports two mining speeds: ECO and BALANCED modes, depending on the external temperature. Additionally, it can send notifications via Telegram when the miner state changes (started, stopped, or miner binary crashes) as well as hourly notifications with stats.

I’ve published the code on my GitLab, and I’m thrilled to share it with the community. I hope this will be helpful. Please check it out! 😊

https://gitlab.com/UyosDP8sQsgO/apollo-ii-temperature-control/

Thank you for your answer.
No, I run the Apollo Server as a pure network server (without keyboard, mouse and monitor).
Regarding “sudo apt update” and “sudo apt upgrade” I don't share your concerns.
As far as I have understood the support, you just should not do a distribution update, but these updates are ok (as they also contain security fixes) and can be done in addition to the Web-IF updates from Appollo.
My Apollo 2.0.5 system runs very stable even after having installed the latest Ubuntu OS updates with above commands using SSH.

To enable other BTC nodes to connect to your BTC node, you must enable port forwarding in your router to the apollo node.

Example:
Inbound rule:
Allow ANY SOURCE IP:Protocol:TCP:ANY SOURCE PORT -> APOLLO INTRANET NODE-IP:Protocol:TCP:PORT:8333

I highly advise to configure suitable internal and external firewall rules, accordingly, and place the Apollo node into a VLAN network which is separate from your normal untagged intranet LAN.

Example:
internal firewall: full isolation of apollo server from intranet network. Except access for specific admin device (allow access to web-if (port 80) and SSH (port 22)).
external firewall: allow access from any external port to apollo server tcp port 8333 only.

As Ubuntu is a very safe OS, I have no real doubt to get hacked.
However, you could consider additionally using TOR via flag in settings, to increase security.

You can try out, if your node is accessable using this link to bitnodes.io (or just check, whether your node is connected to > 11 nodes):
https://bitnodes.io/#join-the-network

\Trimmed as this got too damn long!  

I personally wouldn't leave my Apollo UI exposed to the internet. Keep it behind your firewall otherwise you're asking to get hacked.

It is my understanding (correct me if I am wrong) that the Apollo offers a Non-SSL encrypted login page via (Port 80) but I don't believe it offers a secure login connection via SSL (Port 443) through the UI to securely login.

This means if you expose Port 80 of the Apollo UI it will be available to anyone that knows your IP and worse yet when you try to connect remotely you would be sending your password over the internet in clear text. Not good by any means from a security perspective.


You'd be much better off if your router offers VPN functionality / connectivity this way you will be able to access your VPN and then your Apollo (and all other devices on your LAN) in a much more secured manner.

Thanks I just tested and everything is open. Thanks so much for the details. So if I wanted to login to my dashboard from outside of my network, do we know which port needs to be open and how I actually get into it?

I figured out how to remote into my mac last night but I had to download an app. then put the YOURPUBLICIP:5900 - Is there something else I need in order to access dashboard from outside of the network?

Sounds like you don't have the port forwarding set correctly in your router to be honest.

The forwarding of port 3333 will be used for the external stratum connections / mining pool connectivity.

So if you forward port 3333 from your WAN to your Apollo's internal LAN IP then you should be able to connect miners from outside your LAN to stratum+tcp://YOURPUBLICIP:3333 or stratum+tcp://YOURDDNSDOMAINNAME:3333 .

You can test your IP address and confirm if the port is open through your router here just make sure you change the port to 3333 for testing: https://www.yougetsignal.com/tools/open-ports/

8332 is the port you need to open for the node to communicate and connect up to 32 connections. If you don't see more than 28 connections to your node then this is also not configured properly.

Hope this helps.

Thanks again for your help. After I set the ddns and I try to remote in form another device, it doesn’t work when I go to port 3333 and when I got to 8332 which is open as well and that’s where the dashboard says to go to access the node I get this message “ JSONRPC server handles only POST requests”

Any idea what I could be doing incorrectly?

Cheers

Unless you're pretty good at soldering / reflowing I would recommend a local shop. Basically any shop that repairs motherboards / logic boards and the like can do it fairly inexpensively providing the USB is the only issue. I understand there are some mail in services as well but I've never used any myself. I'd try your local shops first.

The usb connector on the back of my old apollo standard unit popped off the board when I was disconnecting to move. Anyone have recommendations to get this fixed? I'm happy to even try to solder it back myself. Total rookie but could be fun.

I 'm trying to connect all of my old units to my new node.

Excellent! Thanks for the info.

Yes I have used 4 port usb 3.0 non powered hubs to add more than 3 standards to the full node. Works great.

Here is the exact hub from Amazon:
https://a.co/d/2gniDhk

As far as I know the fix is in v2.0.6 yet to be released. Cheers!

Quick question to you Apollo II miners out there . . .

Has anyone tried using a USB hub / splitter to expand the ability of the full node unit to except more than two standard hashing units via USB? Thanks.

Perfect!! Thanks so much!!

You must enable port forwarding regardless!

Yes, if ddns is available, then 100% use the domain they provide with :3333 at the end.

Give Compass that ddns info as your stratum, but make sure you include the :3333 at the end of the ddns domain.

anyone know if there is a fix in place for this error yet? 
[GraphQL error]: Message: Int cannot represent non 32-bit signed integer value: 2793209866

I reached out to FutureBit support a month ago and they told me that a fix would go out that week, and then the week after that.  Still nothing.  They said I could just restart the miner, but I'd prefer not rebooting the miner every other day.