Running Bitaxe for 2 days and once in 24 hours on the nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze dashboard it shows that it’s offline 🤷‍♂️ It’s already happened twice. But on my end it’s connected and hashing. Any ideas why it’s happening?

Reply to this note

Please Login to reply.

Discussion

I wonder does it have a log?

On my end logs are good and it’s hashing

I have a similar experience woth my 3 miners. I see no issues with miner side logs but at times ocean shows them momentarily at 0. I think its an issue on their end and i have no idea if its just a display issue, or an actual deficiency in their pool receiving shares submitted by miner. Or perhaps their analytics are more accurate than other pools that smooth out their data reported back to you ( if any ) ? 🤷‍♂️ perhaps all miners have moments where they deliver 0 work

Anyways i dont think its a problem with your bitaxe, imo

Probably an issue with low hash rate vs difficulty.

You should be using looks meant for these miners.

Lol pools*

I checked other miners on the dashboard and they don’t have that drops to 0 🤔

run solo brother

I will do solo with Bitaxe but I gotta play around first with pool. Maybe will get more TH/S to plug in 🤔

Pools might have some minimum threshold of shares before they kill a connection… purely to allocate bandwidth/resources on their side. Not sure.

Have you tested a single Bitaxe with any other pool?

Haven’t tested with other pools

Might try it out.

Happened again 🤷‍♂️

Seems like Bitaxe also restarted after 23 hours 🤔 Weird

Happens occasionally. Internet interruption, port switches, machine reboots. Sometimes the hashboards will start doing strange things and the machine will reboot. If the hashboard is not sending high enough hash difficulty the pool will reject the hashes. Could look at accepted and rejected hashes.

Internet is good for the past 24 hours. Thought that these machines are none stop 24/7/365 seems like not 😅