I noticed a pop up saying that the BTC solo pool address changed to solo.nexuspool.io. After changing the pool address on one of my Bitaxe 601 Gamma’s and rebooting it, it still acts as though it’s working through the bitaxe web interface, but the pool isn’t picking it up after that. Switching back to nexuspool.io picks it back up.
Thanks for the report. Your Gamma was mining while it sat on the solo address. We point solo.nexuspool.io at four servers, and your rig landed on the Chicago one, the nearest to you. Our dashboard reads from LA, so the Gamma dropped off your stats while it hashed in Chicago. Moving it back to nexuspool.io put it on LA, where the dashboard can see it.
That gap is ours to fix. We’re wiring Chicago and the other servers into the dashboard, and I’ll ping you here when it’s done. Until then, keep the Gamma on nexuspool.io if you want to watch it from the dashboard, since your odds are the same on both addresses.
Hey, following up on this one. When your gamma05 Bitaxe reconnected after the reboot, it landed on our Chicago server for a bit instead of LA. That’s normal load balancing, nothing broke on your end. The problem was our dashboard only checked LA, so it looked dead even though it was hashing fine. We saw it pull 1.5 to 2.2 TH/s during that window.
Fixed it today so the dashboard checks every server. Should be good to leave it on solo.nexuspool.io now. If it bounces to another region again, it’ll still show up.
Sounds good. Switch back over to that. Thanks for checking into it.
