Official FutureBit Apollo BTC Software/Image and Support thread - page 77.

wozzwinkl

newbie

Activity: 4

Merit: 0

Quote from: SpeedForceGN on February 24, 2022, 03:22:54 PM

Quote from: wozzwinkl on February 24, 2022, 02:26:26 PM

Quote from: Biffa on February 24, 2022, 06:28:17 AM

Quote from: wozzwinkl on February 23, 2022, 02:53:19 PM

My Apollo BTC is up and has been mining, node is fully synced and running. However, I am getting the message "Only inbound connections detected, please enable port 8333 on your router port forwarding rules for your Apollo IP address" and it shows 10/32 connections.

I have set up forwards for port 8333 on both my security gateway and FiOS router. I had to set up a similar port forward for my Helium miner, so I know that the settings should work, but it does not appear to be working for the node.

Is there something easy I could be missing here?

You can only have one port forward for 8333, if you have set that port up to forward to this helium thing whatever it is then you can't have one setup for the same port going to the Apollo.

I have a FiOS router first in line, and the port forward is set up in there to forward to my Ubiquiti USG Security Gateway. In the USG setup, I have the node set with a static IP and a port forward set up for that IP address.

My Helium miner settings are similar, but pointing to a different IP address and port.

I can use an external port checking tool such as portchecker.io and my Helium miner responds on the appropriate port, but the node does not.

Just not sure why this setup should need to be different in the case of the node vs. the Helium miner.

Try a different pool. Mine has been up and running for 2 weeks now, no issues.

Wait, what?

My miner is working fine. My issue is with the node.

jfaller30

newbie

Activity: 2

Merit: 0

Quote from: jfaller30 on February 24, 2022, 12:41:42 PM

My apollo 3 keeps restarting/shutting down randomly. Not sure what to do. I'm using f2pool. When I changed the pool URL for BCH to BTC, it started doing this. Not sure if this is the cause. It restarts and when firefox opens, sometimes it reboots or shuts down.

Any help is appreciated, thanks.

Update: I reimaged the SD card but it is still rebooting randomly

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

Quote from: OgNasty on February 24, 2022, 06:37:24 PM

I'm not experiencing any issues with usernames being changed. I've also never seen the dashboard (don't even know how to access it to be honest).

Wait, then how did you set your mining pool information?
And how did you choose between 'eco', 'balanced' or 'turbo'?

OgNasty

donator

Activity: 4760

Merit: 4323

Leading Crypto Sports Betting & Casino Platform

I'm not experiencing any issues with usernames being changed. I've also never seen the dashboard (don't even know how to access it to be honest). It seems like the issue could very well be with someone getting on your networks and not a backdoor, but what do I know...

I did discover a couple lines of code will keep them running in the case of a crash of the software and that has kept mine functioning without any need for manual intervention. I pasted the code below if anyone cares. It's nothing groundbreaking you couldn't find in 2 seconds with a Google search, but does the job for my .bat files.

Code:

@echo off
:Start:
pushd "%~dp0"
.\apollo-miner.exe -host YOURPOOLHERE -port YOURPORTHERE -user USERNAMEHERE -pswd ANYTHING -comport YOURCOMHERE -brd_ocp YOURSETTINGHERE -osc YOURSETTINGHERE -ao_mode 1
:: Wait 10 seconds before restarting.
TIMEOUT /T 10
GOTO:Start

ROcrypto

copper member

Activity: 29

Merit: 0

Quote from: cd1177 on February 24, 2022, 05:19:13 PM

Quote from: ROcrypto on February 24, 2022, 03:03:55 PM

Quote from: ?? on ??

Quote from: ROcrypto on February 24, 2022, 12:53:05 PM

The temperatures are low because the Apollo sits on 2 big fans, the reason for that is overheating, especially in turbo mode. So low temps are because of that not because of the board. The issue is that somehow the miner resets to the slushpool with usename Topminer1 which is not even the default one with username Futurebit so something is fishy, it is interesting we are not getting a reply from the manufacturer....someone left a backdoor and is playing with us newbies ... Sad

(

I feel the same way, I've reflashed, made sure the SSD is seated well, used a USB cable to see if the hashboard was bad absolutely nothing wrong with it, temps are in a great range - I even went as far as putting it in ECO mode... after about an hour I get the notification that my miner was disconnected, log back into the dashboard to see the pool settings are once again changed..

What's odd, is it's completely random times when this happens, the first 7 days were flawless mining and then randomly on the 8th day it started changing the pool settings - again sometimes it'll be hours, then sometimes I have to sit there and change the pool settings 5 times within an hour - reboot - let the node start - start miner (sometimes have to click start 5-10 times before it'll become active to where the dashboard pops up) start hashing and then be fine and connected to my pool for 10+ hours..

Makes absolutely no sense other than a back door or something.

I have the same behavior but mine never worked for more than a day....I have locked the pool config file to see what happens....I'll get back

let me know if this is working for you and if so give a description of how you went about it please. thanks!

Will do.

cd1177

newbie

Activity: 15

Merit: 0

Quote from: ROcrypto on February 24, 2022, 03:03:55 PM

Quote from: ?? on ??

Quote from: ROcrypto on February 24, 2022, 12:53:05 PM

The temperatures are low because the Apollo sits on 2 big fans, the reason for that is overheating, especially in turbo mode. So low temps are because of that not because of the board. The issue is that somehow the miner resets to the slushpool with usename Topminer1 which is not even the default one with username Futurebit so something is fishy, it is interesting we are not getting a reply from the manufacturer....someone left a backdoor and is playing with us newbies ... Sad

(

I feel the same way, I've reflashed, made sure the SSD is seated well, used a USB cable to see if the hashboard was bad absolutely nothing wrong with it, temps are in a great range - I even went as far as putting it in ECO mode... after about an hour I get the notification that my miner was disconnected, log back into the dashboard to see the pool settings are once again changed..

What's odd, is it's completely random times when this happens, the first 7 days were flawless mining and then randomly on the 8th day it started changing the pool settings - again sometimes it'll be hours, then sometimes I have to sit there and change the pool settings 5 times within an hour - reboot - let the node start - start miner (sometimes have to click start 5-10 times before it'll become active to where the dashboard pops up) start hashing and then be fine and connected to my pool for 10+ hours..

Makes absolutely no sense other than a back door or something.

I have the same behavior but mine never worked for more than a day....I have locked the pool config file to see what happens....I'll get back

let me know if this is working for you and if so give a description of how you went about it please. thanks!

SpeedForceGN

newbie

Activity: 59

Merit: 0

Quote from: wozzwinkl on February 24, 2022, 02:26:26 PM

Quote from: Biffa on February 24, 2022, 06:28:17 AM

Quote from: wozzwinkl on February 23, 2022, 02:53:19 PM

My Apollo BTC is up and has been mining, node is fully synced and running. However, I am getting the message "Only inbound connections detected, please enable port 8333 on your router port forwarding rules for your Apollo IP address" and it shows 10/32 connections.

I have set up forwards for port 8333 on both my security gateway and FiOS router. I had to set up a similar port forward for my Helium miner, so I know that the settings should work, but it does not appear to be working for the node.

Is there something easy I could be missing here?

You can only have one port forward for 8333, if you have set that port up to forward to this helium thing whatever it is then you can't have one setup for the same port going to the Apollo.

I have a FiOS router first in line, and the port forward is set up in there to forward to my Ubiquiti USG Security Gateway. In the USG setup, I have the node set with a static IP and a port forward set up for that IP address.

My Helium miner settings are similar, but pointing to a different IP address and port.

I can use an external port checking tool such as portchecker.io and my Helium miner responds on the appropriate port, but the node does not.

Just not sure why this setup should need to be different in the case of the node vs. the Helium miner.

Try a different pool. Mine has been up and running for 2 weeks now, no issues.

ROcrypto

copper member

Activity: 29

Merit: 0

Quote from: ?? on ??

Quote from: ROcrypto on February 24, 2022, 12:53:05 PM

The temperatures are low because the Apollo sits on 2 big fans, the reason for that is overheating, especially in turbo mode. So low temps are because of that not because of the board. The issue is that somehow the miner resets to the slushpool with usename Topminer1 which is not even the default one with username Futurebit so something is fishy, it is interesting we are not getting a reply from the manufacturer....someone left a backdoor and is playing with us newbies ... Sad

(

I feel the same way, I've reflashed, made sure the SSD is seated well, used a USB cable to see if the hashboard was bad absolutely nothing wrong with it, temps are in a great range - I even went as far as putting it in ECO mode... after about an hour I get the notification that my miner was disconnected, log back into the dashboard to see the pool settings are once again changed..

What's odd, is it's completely random times when this happens, the first 7 days were flawless mining and then randomly on the 8th day it started changing the pool settings - again sometimes it'll be hours, then sometimes I have to sit there and change the pool settings 5 times within an hour - reboot - let the node start - start miner (sometimes have to click start 5-10 times before it'll become active to where the dashboard pops up) start hashing and then be fine and connected to my pool for 10+ hours..

Makes absolutely no sense other than a back door or something.

I have the same behavior but mine never worked for more than a day....I have locked the pool config file to see what happens....I'll get back

wozzwinkl

newbie

Activity: 4

Merit: 0

Quote from: Biffa on February 24, 2022, 06:28:17 AM

Quote from: wozzwinkl on February 23, 2022, 02:53:19 PM

My Apollo BTC is up and has been mining, node is fully synced and running. However, I am getting the message "Only inbound connections detected, please enable port 8333 on your router port forwarding rules for your Apollo IP address" and it shows 10/32 connections.

I have set up forwards for port 8333 on both my security gateway and FiOS router. I had to set up a similar port forward for my Helium miner, so I know that the settings should work, but it does not appear to be working for the node.

Is there something easy I could be missing here?

You can only have one port forward for 8333, if you have set that port up to forward to this helium thing whatever it is then you can't have one setup for the same port going to the Apollo.

I have a FiOS router first in line, and the port forward is set up in there to forward to my Ubiquiti USG Security Gateway. In the USG setup, I have the node set with a static IP and a port forward set up for that IP address.

My Helium miner settings are similar, but pointing to a different IP address and port.

I can use an external port checking tool such as portchecker.io and my Helium miner responds on the appropriate port, but the node does not.

Just not sure why this setup should need to be different in the case of the node vs. the Helium miner.

ROcrypto

copper member

Activity: 29

Merit: 0

The temperatures are low because the Apollo sits on 2 big fans, the reason for that is overheating, especially in turbo mode. So low temps are because of that not because of the board. The issue is that somehow the miner resets to the slushpool with usename Topminer1 which is not even the default one with username Futurebit so something is fishy, it is interesting we are not getting a reply from the manufacturer....someone left a backdoor and is playing with us newbies ... Sad

(

n0nce

hero member

Activity: 882

Merit: 5834

not your keys, not your coins!

If you guys don't notice weird network activity and it's not getting as warm as it 'should', then it seems the miner just has a problem.
If reflashing doesn't help, it must be a hardware problem.

In this situation, I'd try using it as hashboard-only (controlling it from a laptop / PC via USB cable), just to make sure the hashboard is fine. I would bet it is though, since I don't get how a malfunctioning hashboard would reset pool settings on the Orange Pi.

I would check temps of that Pi, and also check for disk issues (not sure if it writes pool settings to SD or NVMe). In case e.g. it writes the pool settings to the NVMe, but the drive is loose or something like that, I guess it could revert to some default setting for example.

Just a few ideas..

ROcrypto

copper member

Activity: 29

Merit: 0

Quote from: ?? on ??

Quote from: ROcrypto on February 24, 2022, 11:55:51 AM

I am in the same situation, how to edit the default pool config file to eliminate the factory settings??

It seems like someone figured out a way to exploit the FutureBit, there's nothing I can pinpoint in any of the files available on the FutureBit that were edited for the miner to keep switching to some person's miner.

I locked the pool config file, let's see if it happens again ...

jfaller30

newbie

Activity: 2

Merit: 0

My apollo 3 keeps restarting/shutting down randomly. Not sure what to do. I'm using f2pool. When I changed the pool URL for BCH to BTC, it started doing this. Not sure if this is the cause. It restarts and when firefox opens, sometimes it reboots or shuts down.

Any help is appreciated, thanks.

ROcrypto

copper member

Activity: 29

Merit: 0

I am in the same situation, how to edit the default pool config file to eliminate the factory settings??

cd1177

newbie

Activity: 15

Merit: 0

Quote from: n0nce on February 24, 2022, 10:25:00 AM

Quote from: cd1177 on February 24, 2022, 10:15:43 AM

i just shut mine down until there is a resolutions. i'm not letting my unit run while someone else is getting the perks from it.....

Someone getting a few cents a day would be the least of my concerns if I had attackers in my local home network...

Lol! true and i agree with your statement. however i have 25 other different brand miners running, a storage server and things of that nature and i have no issues or attacks on anything else other than the future bit. I'm not saying it's an attack on it but i really don't know why it keeps doing this.

ROcrypto

copper member

Activity: 29

Merit: 0

Quote from: cd1177 on February 24, 2022, 10:15:43 AM

Quote from: ?? on ??

Quote from: SpeedForceGN on February 23, 2022, 09:05:14 PM

Quote from: ROcrypto on February 23, 2022, 09:02:42 PM

Quote from: SpeedForceGN on February 23, 2022, 09:00:57 PM

Quote from: ROcrypto on February 23, 2022, 08:46:33 PM

Quote from: cd1177 on February 23, 2022, 02:04:51 PM

Quote from: jstefanop on February 23, 2022, 01:48:45 PM

Quote from: ?? on ??

I'm absolutely clueless on why my miner will mine flawlessly for days, then I'll have days where it disconnects 100+ times, what's going on?

Also, every single time it disconnects it changes my pool to - stratum+tcp://stratum+tcp://us-east.stratum.slushpool.com:3333 and the username to Topminer.01 with a password of X

It almost seems like my miner is compromised because it makes no sense on why it reverts to some random slushpool account, I've tried to mine on over 10 different pools and it'll mine great for 1-3 days then I'll experience the same exact thing where it just stops mining, changes the pool back to slushpool and restarts itself.. It DOES connect to this slushpool and it hashes.. but I can't login to the slushpool website and find that Topminer.01 at all, it seems like someone is stealing my hashes.

Sounds like your network or another device on your network is compromised. I would try reflashing your SD card to stock, if you still see it happening then someone is gaining access to your Apollo through another device on your network.

You can also change the default account/ssh password on your Apollo as well using the UI settings (we will have the dashboard password apply as the system password automaticly for additional security in the next update).

I have been having the same issue. I'm going to try and reflash. and see what happens.

Also had the same issue. I have just placed the Apollo over 2 big fans and the temp in turbo is around 40-42C and the board stays at 62-63C, big difference from before. Tha hash rate is also aroun 3.07Gb. It seems to be stable for now so I think the temperature is the issue.

External USB fans under the Apollo is the way to go! My temps arethe same range as yours in turbo mode.

Correct. I suspected the temp as the issue but I wasn't 100%, I will see in a couple of days I guess....

Mine has been running with the fan under it for two weeks, Apollo on Turbo no stop.

I'm almost certain that's exactly what the issue is, when it reaches critical temps it must have some sort of built in fail safe that reverts a portion of your settings, I'm assuming.

Or, my network could be compromised, there have been a few people in this thread that have asked if anyone has had issues with DPN (The Deeper Network) I'm hoping someone hasn't figured out a way to use the tunneling services DPN offers, but the log they provide is pretty detailed as far as traffic and nothing seems out of the ordinary, I'm really hoping it's just a heating issue.

Edit: I forgot to ask, I switched from WiFi to ethernet and now I'm getting a "There is a problem fetching system stats (Internal error)" to where I can't see my temps ETC - up at the top on the dashboard.. any suggestions? please don't say reflash again, LoL!

I have had external fans on my setup for months, temps have been in the 40's. this issue with the pool automatically changing just started within the last week. I have relflashed and changed passwords. it ran for a few hours and then automatically changed to that same slushpool address and topminer01. I don't think this is a temp issue........ not really sure what is going on. i just shut mine down until there is a resolutions. i'm not letting my unit run while someone else is getting the perks from it.....

I am experiencing the same thing, this is a week old Apollo and it keeps reverting to the slush pool with user Topminer.1. This is not a coincidence. The temperatures are low so something else is happening .....please help us fix this !!!!