Search content
Sort by
Showing 10 of 10 results by LordKroc
Re: Official FutureBit Apollo BTC Software/Image and Support thread
I had issues with the pool switching and I have replaced the root and dashboard password, I ONLY have port 83333 forwarded but after I made the miner_config file READ ONLY I have no more issues, still I think the issue is not outside the network but inside the futurebit os or Ubuntu. I will be happy to send you logs to see if you can find anything suspicious but I will need instructions on how to do it. So to be clear, I REPEAT, the only forwarded port is 83333 and I have replaced the root password after I have noticed the issues with the pool which started after i turned the miner on after it fully synced the bitcoin node. The password change did not stop the pool switching, the only thing it stopped it was making that config file read only so there is something in the software that tries to change the pool. Now the fact that it happened on 2 Apollo units, mine is a week old, i think it cannot be a coincidence....I would like the manufacturer to look more into this please....
To pinpoint the problem, do the following:
- make sure no other network component is compromised (if in doubt, turn off all other equipment)
- reflash the Apollo OS with a brand new SD card (don't use the current one)
- remove the SSD (which holds the blockchain) from the machine (to make sure no bogus app has been installed on the NVME drive)
- disable port forwarding 8333 on your router (and any other forward if such one exist)
1) Turn on the Apollo and make sure the mining process is disabled - enter your pool credentials.
2) Next, connect to the Apollo via SSH (from a trusted source), or if you have a monitor/keyboard attached, open a terminal session.
3) To see if something is happening to the miner config file, enter the following command:
Code:
watch cat /opt/apolloapi/backend/apollo-miner/miner_config
(you should see your correct pool URL with your credentials)The 'watch' command updates the file contents every 2 seconds. If the config file is altered, you'll see it.
4) Now turn on the miner process from within the dashboard. (Have a look at the 'watch' output - is there a credential change?)
If NO, let the machine run for a few hours to make sure the miner behaves as normal.
Next, turn off the miner process and the Apollo and reinstall the NVME disk. Repeat step 1) and following.
If there is no change in the miner_config, that's good.
Now enable port forwarding 8333 to your Apollo. Repeat step 1 ...
If, at some point, your credentials are being changed, report back when this was gonna happen.
Good luck.
Alright, after doing the step by step trouble shooting you suggested I never seen a change happen on the terminal, hashed great for 14 hours after doing all that, I came home from work and once again, Pool settings changed.
I'm seriously at a loss and have no idea what else to try.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
If anyone is interested in buying a full node+psu at an extremely discounted price, message me.
I have absolutely no desire to be apart of FutureBit with the obvious coding flaws that's allowed some sort of exploit through that's caused a great deal of us to all experience the same exact thing.
I'm currently mining 7 different coins with a dozen or so different miner manufacturers, Helium, a couple weather stations, GEOD navigators, etc... this is the only product I own I truly feel has a potential to completely compromise my entire network by the obvious back doors on these units.
First 400 takes it, it's less than 2 weeks old, I'll even throw in free expedited shipping.
I have absolutely no desire to be apart of FutureBit with the obvious coding flaws that's allowed some sort of exploit through that's caused a great deal of us to all experience the same exact thing.
I'm currently mining 7 different coins with a dozen or so different miner manufacturers, Helium, a couple weather stations, GEOD navigators, etc... this is the only product I own I truly feel has a potential to completely compromise my entire network by the obvious back doors on these units.
First 400 takes it, it's less than 2 weeks old, I'll even throw in free expedited shipping.
Let's stop with the fear mongering please. Only you and one other person has reported this, and support has been in touch with one of you. Its been determined the issue is because you guys chose to expose your Apollo to the whole internet for anyone to attack. This akin to leaving your Bitcoin wallet on a table outside, publicly yelling out your address and telling everyone come and take it.
The issue is with forwarding our webUI to the open internet. The webui is not a server grade hardened frontend, its designed for easy access and control of your Apollo from your LAN. While you can forward your WAN port 80 so you can bring your UI up from any and device/place what you are doing is essentially hosting it as a public web page that anyone can try to attack, and this is precisely what happened.
Simply remove those port forwards and you will be fine(or go through the process of turning your Apollo into a hardened server grade web server). If you really want to be able to access your Apollo from outside your LAN in an easy and more secure way, then setup a remote access app directly in the desktop environment.
uPnP is disabled, and the only port open is for my Helium miner, so once again I'm at a loss here on why it keeps reverting.
Also, just in the past 3 days there's actually been 5 of us that have raised concern to the same exact issue.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
If anyone is interested in buying a full node+psu at an extremely discounted price, message me.
I have absolutely no desire to be apart of FutureBit with the obvious coding flaws that's allowed some sort of exploit through that's caused a great deal of us to all experience the same exact thing.
I'm currently mining 7 different coins with a dozen or so different manufacturers, Helium, a couple weather stations, GEOD navigators, etc... this is the only product I own I truly feel has a potential to completely compromise my entire network by the obvious back doors on these units.
First 400 takes it, it's less than 2 weeks old.
I have absolutely no desire to be apart of FutureBit with the obvious coding flaws that's allowed some sort of exploit through that's caused a great deal of us to all experience the same exact thing.
I'm currently mining 7 different coins with a dozen or so different manufacturers, Helium, a couple weather stations, GEOD navigators, etc... this is the only product I own I truly feel has a potential to completely compromise my entire network by the obvious back doors on these units.
First 400 takes it, it's less than 2 weeks old.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
update on my end. i thought i had it figured out. but i woke up this morning and was wrong..... so i reflashed, setup a totally different vlan than it was on, added it on a totally different wifi network instead of the same ether connection it was on before, setup the pool and password on startup, clicked on settings and users and changed the main password to one that is different from default and different than my dashboard login, fired it up, working great, temps around 45 and 62, ran great for 5-8 hours, woke up, changed back to slushpool and topminer01.........(i have tried using multiple pools, keeps reverting back to topminer01 on slushpool) is there something i'm missing? is there a different system password that someone could be accessing to get into it and change everything? i'm at a loss at this point.....
Where did you buy it?
from futurebit. one full node and 3 standard units.
OK just wanted to rule out third party tampering before you got it.
What pool are you using? Have you tried other pools?
yep i've used multiple. i am not currently using slushpool however. its so strange, i go through all these steps. it runs fine on the pool i set, then at random it will go back to this topminero1 workername on slushpool as others have seen. with reflashing and all that and setting the default pool to something totally different, i just can't understand how it keeps changing without some sort of a compromise or something. like i said, after yesterday, it had a new network, new ip, isoloated from anything else in my network, all the passwords on the unit that i know of changed, unless there's more i don't know about or some kind of a virus or bug or something....
OK
The config file that the miner uses to populate the pool login details is called "miner_config" and is located in: /opt/apolloapi/backend/apollo-miner/
If you SSH into the miner you can cd to that directory and view it with "cat miner_config" command
So I would first, SSH in while the miner is set how you like it, then check that file to make sure it has saved the settings.
Then if it switches back to slushpool and the other account, check again and see if the file has changed.
You can also see the log for the miner in that directory called miner.events
First thing you need to change is the default root password. Please remember that the root password is public, so if someone gains access to your network and scans it and finds "futurebit-btc" its pretty easy for them to do a google search and figure out how to log in and take over your unit. This applies to almost any miner / open source firmware or devices on your network.
You can change the default password in the OS settings using a monitor:
Power Button on Upper right hand corner -> Settings -> Users -> Change password
OR
SSH into your device (futurebit/futurebit123) and type password update command
Code:
passwd
Ideally you should do this right after a fresh SD card install before you connect the device to your network with a monitor keyboard and mouse, that way if you have another compromised system on your network it does not have a chance to auto log in and hijack your Apollo.
This is just temporary though and you need to find the root cause of how they are accessing your network in the first place, which is probably another compromised system/device on your network.
Everyone should be doing this regardless, and in a future update we will be implementing more security measures like setting the dashboard password you initially set up to the root password as well.
Did everything above to a T and still it switched me back to the slushpool, Topminer.01 and password X...
This is a SERIOUS issue that needs addressed immediately, my network IS NOT compromised.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
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 ...
( 
( 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.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
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 a some person's miner.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
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...It's definitely not my network being compromised, something is wrong with this miner, it's also not getting above 55°C so it's not the heat causing it to revert back to some random guys mining pool.
I've sat here for the past 4 hours looking through every single packet sent from the Apollo and I don't see anything weird.
So I don't know.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
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.
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.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
It almost seems like my miner is compromised
Then just reflash the microSD card with the iso files on the first page of this thread.Might also just be an instable WiFi connection. Would recommend Ethernet if in any way possible..
I tried the reflashing and I am not on WiFi.. I'm just absolutely confused on why this one always reverts back to default pool settings every time it disconnects.
Re: Official FutureBit Apollo BTC Software/Image and Support thread
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.
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.