Mining Errors:
-
same thing i am getting... right now its only on this one pool
unplug your HDD's and see what it does? mine gets to "paths' error
go to a different pool and all works fine so DO NOT format your HDD's yet
-
@falconCoin Can't unplug it. It's a partition on the only drive I have. Do you mean remove it from the plots? Please advise. Thanks.
-
try another pool and see what it does, sorry mine is on externals
-
@falconCoin Miner try to resolve address of pool, but pool is down/unavailable - miner stuck.
You may change a pool.*also update your miner - https://github.com/Blagodarenko/miner-burst/releases/tag/v1.170603
changes:
added avx2 support (more 30% faster than avx)
added reconfirmation unconfirmed deadlines
Wake Up! changed to 3 mins
some code refactoring
little bugs fixed
fixed miner crash if you mining at Ninja-like pool v3 (bug with the v3 code)miner-v1.170601.exe - for all CPU (x64)
miner-v1.170601_AVX.exe - for all CPU with support AVX
miner-v1.170601_AVX2.exe - for all CPU with support AVX2
-
thanks will download now
think @haitch and i figured out my issue...
@GhostEmployee give that a whirl what Blago just told us, we are using his awesome miner! thanks again Blago
-
Cool. Now working and I'm earning (some) burst... Thanks for the help.
-
"Your Burst account's reward recipient (XXXX-XXXX-XXXX-XXXXX) does not match pool's account (YYYY-YYYY-YYYY-YYYYY)": As it says, your reward recipient doesn't match the pool. This is either because a) You've done a Reward Assignment but 4 blocks haven't passed yet or b) you're mining on the wrong pool.
i have this problem And I can not fix this problem help me.
-
@vor121 You're the second person I've seen with this error today, and I don't know why. You've got the correct pool address and port, but you're hitting the wrong pool instance- in your case the .biz pool instead of the burst-team pool. Try updating to the latest version of the Blagos miner, if that don'tt rk, look at switching to BIZ or some other pool..
-
504 Gateway Time-out
Online wallet why don't working?
-
@vor121 It's being DoS'd - more transaction requests than it can keep up with. New firewall hopefully going in next week to deal with it.
