Dead Pool - Nicehash -> PH

Hi guys!

I'm getting "dead" every time my X11 NiceHash send some love to PH. The worker looks connected at PH... however, NiceHash register more than 75% rejected shares and goes dead.
I'm using this same password for about 2 months and it was working well:
Password: a=x11 g=off h=1000 d=2

Clues how to solve this?

Thank you so much for the help.

Post edited to add screen:
https://ibb.co/dEcUyw

ive accidentally switched pool to PH, it was showing live when i called switch, but when i switchd it came up with "DEAD" satatus,. than i got distracted walked away and some 8 hours later i noticed it was actually chugging away at PH, and has been ever since than .. 3 and a bit days.

Not sure why you have g=off

and d=2? lol?

And then h=1000?

Take all of that off (except g=off if you are cloud mining? otherwise you're just lowering your profit if that's not the case) and see if your issues persist.

When in doubt, if you have stuff in your password arguments, take them away and see if you continue to have an issue.

Aura89 wrote:Not sure why you have g=off

and d=2? lol?

And then h=1000?

Take all of that off (except g=off if you are cloud mining? otherwise you're just lowering your profit if that's not the case) and see if your issues persist.

When in doubt, if you have stuff in your password arguments, take them away and see if you continue to have an issue.

Hi Aura89,

I'm using Nicehash and using that same password for about 2 months... now suddenly is not working for the last 2 days... strange

Ok... now NH tells me:

"Disconnected. Pool difficulty too low for high speed." and Current Diff is 2.

What diff should I try?

I don't even understand what current difficulty being 2 would mean, is that even a valid difficulty?

As i said, take off all of the stuff other then g=off (i assume that is needed for nicehash? If someone wants to state if that is so, that'd be good.) and a=x11

As i see it, you have your difficulty set to 2, which i'm 99.99% certain is not a valid difficulty, and even if it were it'd be so small it'd be useless, and then you have your minimum set to 1000, how is something supposed to work with a difficulty of 2 and minimum 1000?

Just use Password: a=x11 g=off, that's it, nothing more.

Don't set a difficulty, as the system will assign you one based off your hashrate. Setting a difficulty, unless you know what you're doing and have done multiple tests for you, specifically, will only lower profits

Setting a minimum difficulty, again will only lower profits

It states this in the help page.

https://prohashing.com/help.html

Fine Aura89, I'm going to test that way.
However, I've been mining very fine with this settings so... I don't understand why it should stop working now.

Bitatlas wrote:Fine Aura89, I'm going to test that way.
However, I've been mining very fine with this settings so... I don't understand why it should stop working now.

It doesn't really matter that it's been "fine" before. There have been some updated (though this was more then two days ago) settings within the pool that makes too low of a difficulty not work, but again, a difficulty of 2 i don't think would work anywhere........

Point being, what i said in my original post:

When in doubt, if you have stuff in your password arguments, take them away and see if you continue to have an issue.

If you don't do that first thing, to see if the password arguments are what are causing you the issue, then no one can help you.

And yes i see you said you're going to try it, which is great, but that should always be the first thing you do. If you tinker with your engine in your car and it happens to have issues later on, you'd do the same thing, reset whatever you tinkered with back to normal and see if you have having an issue.

If it happens that the password arguments are not the issue, then you need to submit a support ticket and give them all the information about your setup that you can.

I would like to put out there though, you sure it's been working for x11 on nicehash?

Per one of the creators of this pool;

Steve Sokolowski wrote:

Checker1 wrote:I think it is not possible to get nicehash x11 properly work in prohashing.com. I just tested huge amount of different settings/passwortarguments, but finally result is with every setup the same: pool shows permanently dead or pool starts to show dead in the moment when hashing starts.

Scrypt miningpower from nicehash works good.

If somebody would have some atlernative setup which works, it would be very helpful.

Thx!

This is correct. NiceHash rejects scrypt difficulties as being too high and doesn't wait the fraction of a second necessary for the x11 difficulty to be parsed from the password.

The only workaround for this issue is to have a second server that defaults to a=x11. Parallelism is one of the things we plan to do in the future to increase capacity, so this would go along with it, but I can't guarantee when that will be available.

According to him, it shouldn't be possible, not yet anyways, and if you had it working before you got lucky, because the post i just put in here is from september 25th, which is not that long ago.

Aura89 wrote:I would like to put out there though, you sure it's been working for x11 on nicehash?

Per one of the creators of this pool;

Steve Sokolowski wrote:

Checker1 wrote:I think it is not possible to get nicehash x11 properly work in prohashing.com. I just tested huge amount of different settings/passwortarguments, but finally result is with every setup the same: pool shows permanently dead or pool starts to show dead in the moment when hashing starts.

Scrypt miningpower from nicehash works good.

If somebody would have some atlernative setup which works, it would be very helpful.

Thx!

This is correct. NiceHash rejects scrypt difficulties as being too high and doesn't wait the fraction of a second necessary for the x11 difficulty to be parsed from the password.

The only workaround for this issue is to have a second server that defaults to a=x11. Parallelism is one of the things we plan to do in the future to increase capacity, so this would go along with it, but I can't guarantee when that will be available.

According to him, it shouldn't be possible, not yet anyways, and if you had it working before you got lucky, because the post i just put in here is from september 25th, which is not that long ago.

Guys, tried only for password a=x11 g=off and I'm dead... I assure you I've been mining with the same password for 2 months and it was working pretty well... Suggestions?