Quote from: jstefanop on February 26, 2022, 04:11:52 AM

Quote from: LordKroc on February 26, 2022, 03:40:25 AM

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.

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.

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....