Bitcoin Forum

Bitcoin => Mining support => Topic started by: SJSMiner on January 22, 2019, 07:07:28 PM



Title: Pools - Dead / Alive
Post by: SJSMiner on January 22, 2019, 07:07:28 PM
All three pools DEAD due to VPN.  changed servers ckpool.org came back but slushpool and kano.is did not.  any ideas?

i know if i reboot i could fix it but plan to wait to see if they eventually come back.

sjs


Title: Re: Pools - Dead / Alive
Post by: kano on January 22, 2019, 07:17:48 PM
Mining through a VPN increases the chance of the pool losing a block.
Don't do that.
You want the path from your miner to the pool to be as short and fast as possible.


Title: Re: Pools - Dead / Alive
Post by: mikeywith on January 22, 2019, 07:39:16 PM
why would they eventually come back? it's unlikely, unless there is a problem with both of them and then it get's fixed which is very unlikely.
the above comment makes sense, but it's also not as bad as it may sound, the problem could be this

- your VPN server itself is blocking slush and kano pool servers for some reason.

you got two things to try to for now:

1- change the VPN server location , until you get those pools back, try to chose a country that is crypto friendly.
2- change the DNS on your router / miner, use a public dns like google's 8.8.8.8

* step 2 is not recommended if you are using online wallets

also you probably have to reboot the miner for a dead pool to become alive again, there is no guarantee that cgminer is going to ping the pool aside from the start-up period.

but you don't have to do this at every change you make, you can simply try pining those pools from a pc that runs on the same network and using the same vpn by:

1- open CMD

2-type

Code:
ping kano.is

if you get something like this

https://i.postimg.cc/63hgn0BT/ping-kano.jpg (https://i.postimg.cc/63hgn0BT/ping-kano.jpg)

then your miner will find the pool "alive"

however if you get something like this

https://i.postimg.cc/cJ3WG8wT/can-t-ping.jpg (https://i.postimg.cc/cJ3WG8wT/can-t-ping.jpg)

then your miner will show pool "dead".

post back your findings, there are a few more things to try out. but these are the most 2 common solutions i can think of now.


Title: Re: Pools - Dead / Alive
Post by: SJSMiner on January 23, 2019, 02:21:28 PM
they eventually came back with slushpool taking the longest time.


Title: Re: Pools - Dead / Alive
Post by: Artemis3 on January 24, 2019, 05:59:51 AM
they eventually came back with slushpool taking the longest time.

Pools have multiple servers, ping them all and choose the fastest 3.

For example:

Code:
fping -c 1 stratum.kano.is or.kano.is nya.kano.is uk.kano.is de.kano.is jp.kano.is sg.kano.is stratum.kano.space or.kano.space nya.kano.space uk.kano.space de.kano.space jp.kano.space sg.kano.space
nya.kano.is        : [0], 84 bytes, 159 ms (159 avg, 0% loss)
stratum.kano.is    : [0], 84 bytes, 183 ms (183 avg, 0% loss)
nya.kano.space     : [0], 84 bytes, 147 ms (147 avg, 0% loss)
uk.kano.is         : [0], 84 bytes, 214 ms (214 avg, 0% loss)
stratum.kano.space : [0], 84 bytes, 188 ms (188 avg, 0% loss)
uk.kano.space      : [0], 84 bytes, 204 ms (204 avg, 0% loss)
jp.kano.is         : [0], 84 bytes, 289 ms (289 avg, 0% loss)
jp.kano.space      : [0], 84 bytes, 270 ms (270 avg, 0% loss)

Here i would pick: nya.kano.space, nya.kano.is and stratum.kano.is