My miners are being rejected

Encounter a problem related to the pool or have a request for a feature? Post your issue here and we will help you out.
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.

Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.

We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Locked
jaether
Posts: 15
Joined: Fri Oct 13, 2017 8:51 am

My miners are being rejected

Post by jaether » Wed Mar 28, 2018 8:34 am

Hi, is there a problem with solo mining Verge. My miners are being rejected and going to the back-up pool.
Am I the only one with this problem? I prefer mining at PH because of solo mining possibility so I hope I'm not banned.
Also tried another coin than Verge, but still it jumps to the back-up pool. I don't know what's going wrong, can anybody tell me?
jaether
Posts: 15
Joined: Fri Oct 13, 2017 8:51 am

Re: My miners are being rejected

Post by jaether » Wed Mar 28, 2018 8:37 am

As I post this message the miners are going back to PH. Is that coincidence? anyway I am happy. Hope they will stay now!
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: My miners are being rejected

Post by Steve Sokolowski » Wed Mar 28, 2018 8:44 am

jaether wrote:As I post this message the miners are going back to PH. Is that coincidence? anyway I am happy. Hope they will stay now!
There was a bug that occurred with Verge that I wasn't able to determine what happened. I restarted the mining servers that were experiencing that bug and everything returned to normal.

I'll continue investigating this if it occurs again. Sorry about that!
Locked