"no valid shares" on most of my L3+

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.
JAsolutions
Posts: 5
Joined: Mon Sep 11, 2017 6:26 am

"no valid shares" on most of my L3+

Post by JAsolutions » Mon Sep 11, 2017 6:32 am

I'm getting "no valid shares" on 30-80% of my L3+.

What is causing this problem and what can I/we do to fix it?
kenny018
Posts: 2
Joined: Mon Sep 11, 2017 6:36 am

Re: "no valid shares" on most of my L3+

Post by kenny018 » Mon Sep 11, 2017 6:38 am

Same problem here. Keeps disconnecting after minutes. All miners
kenny018
Posts: 2
Joined: Mon Sep 11, 2017 6:36 am

Re: "no valid shares" on most of my L3+

Post by kenny018 » Mon Sep 11, 2017 6:39 am

Image

After the server upgrade i have major problems.
JAsolutions
Posts: 5
Joined: Mon Sep 11, 2017 6:26 am

Re: "no valid shares" on most of my L3+

Post by JAsolutions » Thu Sep 14, 2017 12:14 am

Yes... would be nice to have our issue address by support staff or another knowledgeable reader :)
hashingpro
Posts: 207
Joined: Fri Aug 18, 2017 1:14 am

Re: "no valid shares" on most of my L3+

Post by hashingpro » Thu Sep 14, 2017 2:45 am

what is the password line you are using?

On the pool status does it show ALIVE or DEAD of prohashing site?

What URL are you using for the site?

Did you spell your miner name case-sensitive to when you made the account?
BOBBIE =/= Bobbie or bobbie
JAsolutions
Posts: 5
Joined: Mon Sep 11, 2017 6:26 am

Re: "no valid shares" on most of my L3+

Post by JAsolutions » Thu Sep 14, 2017 12:08 pm

hashingpro wrote:what is the password line you are using?

On the pool status does it show ALIVE or DEAD of prohashing site?

What URL are you using for the site?

Did you spell your miner name case-sensitive to when you made the account?
BOBBIE =/= Bobbie or bobbie
Password line is n=NameXX

I got the URL right - when it says "no valid shares", Miner Status shows Alive and appears to be hashing. It's just the status shown on prohashing dashboard that says "no valid shares". When miner status shows Dead, it's not even shown on prohashing dashboard (mining on backup site).

Miners apparently go on and off from prohashing.com. Frequently. And the problem is worse on some days than others (pretty bad today).

Really seems like a server problem.. if this continues, many people will not want to mine here! Are you upgrading server or sth?

https://i.imgur.com/N4WLair.png
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: "no valid shares" on most of my L3+

Post by Steve Sokolowski » Thu Sep 14, 2017 12:54 pm

JAsolutions wrote:
hashingpro wrote:what is the password line you are using?

On the pool status does it show ALIVE or DEAD of prohashing site?

What URL are you using for the site?

Did you spell your miner name case-sensitive to when you made the account?
BOBBIE =/= Bobbie or bobbie
Password line is n=NameXX

I got the URL right - when it says "no valid shares", Miner Status shows Alive and appears to be hashing. It's just the status shown on prohashing dashboard that says "no valid shares". When miner status shows Dead, it's not even shown on prohashing dashboard (mining on backup site).

Miners apparently go on and off from prohashing.com. Frequently. And the problem is worse on some days than others (pretty bad today).

Really seems like a server problem.. if this continues, many people will not want to mine here! Are you upgrading server or sth?

https://i.imgur.com/N4WLair.png
Unfortunately, we've been working on this issue for a month and still don't have any leads. Chris is going to try increasing the rejected share ban threshold today on the theory that because L3s have so much hashrate, they are more likely to submit rejected shares and exceed the ban threshold.

Hopefully, that will make a difference.
User avatar
alvarezgen
Posts: 7
Joined: Sun Sep 10, 2017 1:08 pm
Location: Planet Earth

Re: "no valid shares" on most of my L3+

Post by alvarezgen » Thu Sep 14, 2017 5:14 pm

Steve Sokolowski wrote:
JAsolutions wrote:
hashingpro wrote:what is the password line you are using?

On the pool status does it show ALIVE or DEAD of prohashing site?

What URL are you using for the site?

Did you spell your miner name case-sensitive to when you made the account?
BOBBIE =/= Bobbie or bobbie
Password line is n=NameXX

I got the URL right - when it says "no valid shares", Miner Status shows Alive and appears to be hashing. It's just the status shown on prohashing dashboard that says "no valid shares". When miner status shows Dead, it's not even shown on prohashing dashboard (mining on backup site).

Miners apparently go on and off from prohashing.com. Frequently. And the problem is worse on some days than others (pretty bad today).

Really seems like a server problem.. if this continues, many people will not want to mine here! Are you upgrading server or sth?

https://i.imgur.com/N4WLair.png
Unfortunately, we've been working on this issue for a month and still don't have any leads. Chris is going to try increasing the rejected share ban threshold today on the theory that because L3s have so much hashrate, they are more likely to submit rejected shares and exceed the ban threshold.

Hopefully, that will make a difference.
Same problem here on all my L3+. I have been mining with no problem for the past 2 - 3 days, but since yesterday I'm getting "no valid shares".

I hope increasing the rejected share ban threshold can fix this.
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: "no valid shares" on most of my L3+

Post by Steve Sokolowski » Thu Sep 14, 2017 5:32 pm

alvarezgen wrote:
Steve Sokolowski wrote:
JAsolutions wrote:
Password line is n=NameXX

I got the URL right - when it says "no valid shares", Miner Status shows Alive and appears to be hashing. It's just the status shown on prohashing dashboard that says "no valid shares". When miner status shows Dead, it's not even shown on prohashing dashboard (mining on backup site).

Miners apparently go on and off from prohashing.com. Frequently. And the problem is worse on some days than others (pretty bad today).

Really seems like a server problem.. if this continues, many people will not want to mine here! Are you upgrading server or sth?

https://i.imgur.com/N4WLair.png
Unfortunately, we've been working on this issue for a month and still don't have any leads. Chris is going to try increasing the rejected share ban threshold today on the theory that because L3s have so much hashrate, they are more likely to submit rejected shares and exceed the ban threshold.

Hopefully, that will make a difference.
Same problem here on all my L3+. I have been mining with no problem for the past 2 - 3 days, but since yesterday I'm getting "no valid shares".

I hope increasing the rejected share ban threshold can fix this.
We just increased the threshold. Have you had more success now?
ishkatar
Posts: 3
Joined: Thu Sep 14, 2017 5:26 pm

Re: "no valid shares" on most of my L3+

Post by ishkatar » Thu Sep 14, 2017 5:43 pm

Hi Steve,
The same is happening with my 2 L3+ miners... they were working fine last week and since yesterday the pool status changes from dead/alive every couple of seconds... while the proxy.prohashing.com:443 has stayed dead...
If there is anything I can do to help let me know...
(I did not see any change in the last couple of minutes, so any change you made did not solve the issue, at least for me)
Thanks,
Ishkatar
Post Reply