 Show Posts
|
|
Pages: [1]
|
|
any updates on solo mining to our own nodes? or any working workarounds ? is it worth it or better to just use ckpool solo?
|
|
|
|
Ive have 3 standards and a full node. they have all ran fine for quite awhile. the full node and 1 standard are first batches and i have since upgraded the ssd. like i said they have all ran fine for months. one of the standards stopped and won't ever start back up. i power it down and restart and it will go through the process but eventually it will just completely stop and stay that way. tried restarting the whole thing numerous times as a reboot usually seems to fix any issues. but not with this one standard unit. any ideas? thanks
Are you connecting all the standards to the Full package Apollo via USB? I find that the USB connection on my Full packages is very sketchy. You could try to connect just the faulty Standard unit, or swap the order in which connect them to USB, maybe another one starts to malfunction then. When I suspect USB issues, I disconnect the USB hub before rebooting the Full package unit, then reconnect the USB hub and standard unit after it has booted up. Changing the USB port also helps sometimes, there seems to be no rhyme nor rhythm to it, just that once one of the USB ports is having a dummy spit, it causes weird issues until it is allowed to power up without a load on it. worked! thank you |
|
|
|
|
Ive have 3 standards and a full node. they have all ran fine for quite awhile. the full node and 1 standard are first batches and i have since upgraded the ssd. like i said they have all ran fine for months. one of the standards stopped and won't ever start back up. i power it down and restart and it will go through the process but eventually it will just completely stop and stay that way. tried restarting the whole thing numerous times as a reboot usually seems to fix any issues. but not with this one standard unit. any ideas? thanks
|
|
|
|
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.... |
|
|
|
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. |
|
|
|
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. 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. 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..... |
|
|
|
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. 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! |
|
|
|
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. |
|
|
|
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..... |
|
|
|
So good news is that I was able to get my BITCOIN NODE connected to my Ledger Live account. It was a little tedious, but I got it figured out. Wish me luck that it stays connected and up and running.
Next task is that I need to set up my LIGHTNING NETWORK. I think that I am going to try C-Lightning. From what I have found, this seem to be the best choice. (Any help on this would be greatly appreciated).
what's the benefit of connecting your node to your ledger? just curious. |
|
|
|
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. |
|
|
|
I seen a standard unit on eBay with a broken usb c port what would it take to get that repaired?
any answer to this? i have one with the same issue. emailed futurebit about it but haven't heard anything yet. i know they are busy getting batch 3 orders out. |
|
|
|
|
if i have 4 units, will a 1800w bitmain apw7 power supply be okay to use? I have a couple extra and want to eliminate the individual 200w supplies. just want to make sure nothing gets fried and it's compatible. thanks!
|
|
|
|
|
My full unit and 2 standards have ran great for a couple months. couple restarts here and there. today they quit hashing and it won't let me log into the dashboard. i powered them down and back on, still nothing and it's not hashing. the red lights are all blinking like normal though? ideas?
|
|
|
|
|
I've read some posts on here about the port forwarding and helping with connections on the node. I currently have 10/32 connections. I tried forwarding the ports but it didn't change. not sure if i did every right or not? anyone have any suggestions or a good guide for this? also looking to try and forward ports to be able to access remote. I tried that but i can't access remote still so obviously i'm not doing something right.......
|
|
|
|
|
