Author

Topic: [ANN] NiceHash.com - sell & buy hash rate cloud mining service / multipool - page 166. (Read 794394 times)

legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
nicehashsupport ...

just wondering whether you have sifted through the multitude of emails you guys usually get and seen the latest one ( which i sent to info@ and support@ ) regarding the whitelist of ips ...

i dont want to activate them until you whitelist - as they too will be blocked ...

it hasnt been long ... im just impatient Smiley ...

#crysx

hero member
Activity: 588
Merit: 501
I am trying to connect GPU farm to Nicehash, but there are problems with frequent forced disconnects every few minutes. All machines are connected through stratum proxy (Stratehm). There are extranonce subscriptions enabled both in proxy and miners and notification is working properly.

Similar problems appear when machines are directly connected without proxy - connections are dropped in several minutes - again extranonce subscription is checked on Nicehash site.

It seems like there is something closing the stratum connections even if extranonce subscription is active and working correctly. I saw this in a post above:

>>>Unfortunatelly, we are under constant attack by botnet miners, therefore we have filters in place that ban IPs that only idle. If you have large hashing power and static IPs, contact us for a whitelist.

Is there someone else with many machines experiencing the same problems?


Contact us [email protected] and provide details (IP, algo, num. miners, type) and we will take a look into it.

I have sent 2 emails yesterday describing the problem before posting here. Will write again in few minutes.

I believe you got the answer now.
copper member
Activity: 61
Merit: 0
I am trying to connect GPU farm to Nicehash, but there are problems with frequent forced disconnects every few minutes. All machines are connected through stratum proxy (Stratehm). There are extranonce subscriptions enabled both in proxy and miners and notification is working properly.

Similar problems appear when machines are directly connected without proxy - connections are dropped in several minutes - again extranonce subscription is checked on Nicehash site.

It seems like there is something closing the stratum connections even if extranonce subscription is active and working correctly. I saw this in a post above:

>>>Unfortunatelly, we are under constant attack by botnet miners, therefore we have filters in place that ban IPs that only idle. If you have large hashing power and static IPs, contact us for a whitelist.

Is there someone else with many machines experiencing the same problems?


Contact us [email protected] and provide details (IP, algo, num. miners, type) and we will take a look into it.

I have sent 2 emails yesterday describing the problem before posting here. Will write again in few minutes.
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
I am trying to connect GPU farm to Nicehash, but there are problems with frequent forced disconnects every few minutes. All machines are connected through stratum proxy (Stratehm). There are extranonce subscriptions enabled both in proxy and miners and notification is working properly.

Similar problems appear when machines are directly connected without proxy - connections are dropped in several minutes - again extranonce subscription is checked on Nicehash site.

It seems like there is something closing the stratum connections even if extranonce subscription is active and working correctly. I saw this in a post above:

>>>Unfortunatelly, we are under constant attack by botnet miners, therefore we have filters in place that ban IPs that only idle. If you have large hashing power and static IPs, contact us for a whitelist.

Is there someone else with many machines experiencing the same problems?


we had the same issues ... with a very similar setup ...

we use stratehm 1.5 ( not the latest version ) and our farm worked perfectly until we were booted for idle ...

nicehash were very supportive of this and have suggested a solution ... we still get kicked on occasion - but that is normal and it reconnects pretty much right away ...

the reason is that their stratum DOES ban the ip that you are connecting the stratehm proxy from ...

the only way is to send support a message and get that ip you are running from whitelisted ...

nicehash have been very helpful in this area - and really have had no issues since the whitelist ...

we have requested the dev donation server ips ( https://bitcointalksearch.org/topic/a-chainworks-industries-cwi-project-donate-by-mining-dbm-1089744 ) to be whitelisted also - and nicehash have also taken those into the whitelist within 24hours of request ... these servers will be active and fumctional by the end of the week when the ips of the new servers get whitelisted also ...

have had nothing but excellent help and service from nicehash support ... quite refreshing compared to other pools / hash brokers that we were looking at as the main sites to allocate all the hash to ...

cant ask much more than that ...

#crysx
hero member
Activity: 588
Merit: 501
I am trying to connect GPU farm to Nicehash, but there are problems with frequent forced disconnects every few minutes. All machines are connected through stratum proxy (Stratehm). There are extranonce subscriptions enabled both in proxy and miners and notification is working properly.

Similar problems appear when machines are directly connected without proxy - connections are dropped in several minutes - again extranonce subscription is checked on Nicehash site.

It seems like there is something closing the stratum connections even if extranonce subscription is active and working correctly. I saw this in a post above:

>>>Unfortunatelly, we are under constant attack by botnet miners, therefore we have filters in place that ban IPs that only idle. If you have large hashing power and static IPs, contact us for a whitelist.

Is there someone else with many machines experiencing the same problems?


Contact us [email protected] and provide details (IP, algo, num. miners, type) and we will take a look into it.
copper member
Activity: 61
Merit: 0
I am trying to connect GPU farm to Nicehash, but there are problems with frequent forced disconnects every few minutes. All machines are connected through stratum proxy (Stratehm). There are extranonce subscriptions enabled both in proxy and miners and notification is working properly.

Similar problems appear when machines are directly connected without proxy - connections are dropped in several minutes - again extranonce subscription is checked on Nicehash site.

It seems like there is something closing the stratum connections even if extranonce subscription is active and working correctly. I saw this in a post above:

>>>Unfortunatelly, we are under constant attack by botnet miners, therefore we have filters in place that ban IPs that only idle. If you have large hashing power and static IPs, contact us for a whitelist.

Is there someone else with many machines experiencing the same problems?
hero member
Activity: 588
Merit: 501

When you closely monitor order before it goes into dead, you can see bridge status. What kind of status is reported once order gets dead?

sorry, i've got 3 sessions of attempts, and this was the final,
i won't try again to monitor anything, no time for that


Since you exactly knew what kind of diff it was, then you could exactly know what kind of status it reported. Both of these values are reported in same line.

Also, which port was high diff? 6070?

yes i could but i didn't, the diff i saw was in cryptopia worker stats not nicehash.
port 6070 is high-diff, 5070 low-diff

Well, the pool verificator reports that initial diff of that high diff port is only 4096 and not 90k as you claim.

read carefully, "soon after the start", not initial.
and to hell that cryptopia, i couldn't get anything working more than half an hour, on any pool.
so if someone has the same shit - you'r welcome to have a problem, if no one - my mistake,
but i'm done with nicehash.

We checked your select pool manually by placing order with your details - sorry, we mined some coins for you Wink

Pool at start did increase diff, but after 3 minutes of working it decreased diff (for unknown reasons):

Code:
104.219.250.54:6070 Disconnected. Pool difficulty too low for high speed. 0 0.0619 6907.5586

It decreased diff below 8192 threshold (to only 6907.5586). Why this happened, only the pool can explain.
hero member
Activity: 588
Merit: 501

When you closely monitor order before it goes into dead, you can see bridge status. What kind of status is reported once order gets dead?

sorry, i've got 3 sessions of attempts, and this was the final,
i won't try again to monitor anything, no time for that


Since you exactly knew what kind of diff it was, then you could exactly know what kind of status it reported. Both of these values are reported in same line.

Also, which port was high diff? 6070?

yes i could but i didn't, the diff i saw was in cryptopia worker stats not nicehash.
port 6070 is high-diff, 5070 low-diff

Well, the pool verificator reports that initial diff of that high diff port is only 4096 and not 90k as you claim.
hero member
Activity: 588
Merit: 501

When you closely monitor order before it goes into dead, you can see bridge status. What kind of status is reported once order gets dead?

sorry, i've got 3 sessions of attempts, and this was the final,
i won't try again to monitor anything, no time for that


Since you exactly knew what kind of diff it was, then you could exactly know what kind of status it reported. Both of these values are reported in same line.

Also, which port was high diff? 6070?
hero member
Activity: 588
Merit: 501

Your pool isn't using high enough difficulty.


this only means nicehash is incompatible with its vardiff behaviour these days,
becoz when i started, the diff was insane 90k not 4k.
coinmine.pw, coinotron, ipominer, and even 3-4 pools on suprnova, the same shit.
all of them were ok a month ago, that's why i asked what changed ...
i just noticed the fixed rent gets killed every time when price jumps

Most of pools offer you ability to choose difficulty (via password for example) or they have high diff ports. Most of Scrypt pools are still stuck with old diff configs, when Scrypt was mined with GPUs. Diffs below 1024 were normal that time, but todays ASICs are 100-500x times faster thus they need 100-500x higher diff.

As explained already 2 pages back to another person who had the same problem, fixed orders have very small tolerance for dead time They get cancelled if being dead for more than 10% of the time.

well, that's it, 10%, and seems i've no use of fixed orders then.
as per theory, 6**** ports of cryptopia are just those high diff ones,
but that doesn't help, and suprnova "nicehash" ports don't help either,
those 10% deadtime happen to occur no matter,
or at least nicehash engine counts like that.
thanks anyway.....

Contact the pool you mine at and ask them for a diff raise. Using a diff 16384 is nothing unusual today and this is still very low diff for fast modern ASICs. It is just a matter of setting value in pool's config.

i used high diff ports wherever possible, or manually set as on ipominer for example.
but that doesn't help, fixed jobs die in 30 min maximum

What was the diff on these ports? If it was 4096 like in that order # you provided - that is not high diff port, that is low diff port. It would have been high diff port 1 year ago, but not today with 400MHs titans running around.

the diff on cryptopia was 90k soon afetr the start, that diff is NOT appropriate for 80MH/s,
after it reached that value pool dropped, so your engine started counting deadtime,
then it revives again from 1024-2048 and goes higher until next drop,
that's how it works, and not only for cryptopia,
probably that's why those 10% are being accumulated very soon and order gets killed.

When you closely monitor order before it goes into dead, you can see bridge status. What kind of status is reported once order gets dead?
hero member
Activity: 588
Merit: 501

Your pool isn't using high enough difficulty.


this only means nicehash is incompatible with its vardiff behaviour these days,
becoz when i started, the diff was insane 90k not 4k.
coinmine.pw, coinotron, ipominer, and even 3-4 pools on suprnova, the same shit.
all of them were ok a month ago, that's why i asked what changed ...
i just noticed the fixed rent gets killed every time when price jumps

Most of pools offer you ability to choose difficulty (via password for example) or they have high diff ports. Most of Scrypt pools are still stuck with old diff configs, when Scrypt was mined with GPUs. Diffs below 1024 were normal that time, but todays ASICs are 100-500x times faster thus they need 100-500x higher diff.

As explained already 2 pages back to another person who had the same problem, fixed orders have very small tolerance for dead time They get cancelled if being dead for more than 10% of the time.

well, that's it, 10%, and seems i've no use of fixed orders then.
as per theory, 6**** ports of cryptopia are just those high diff ones,
but that doesn't help, and suprnova "nicehash" ports don't help either,
those 10% deadtime happen to occur no matter,
or at least nicehash engine counts like that.
thanks anyway.....

Contact the pool you mine at and ask them for a diff raise. Using a diff 16384 is nothing unusual today and this is still very low diff for fast modern ASICs. It is just a matter of setting value in pool's config.

i used high diff ports wherever possible, or manually set as on ipominer for example.
but that doesn't help, fixed jobs die in 30 min maximum

What was the diff on these ports? If it was 4096 like in that order # you provided - that is not high diff port, that is low diff port. It would have been high diff port 1 year ago, but not today with 400MHs titans running around.
hero member
Activity: 588
Merit: 501

Your pool isn't using high enough difficulty.


this only means nicehash is incompatible with its vardiff behaviour these days,
becoz when i started, the diff was insane 90k not 4k.
coinmine.pw, coinotron, ipominer, and even 3-4 pools on suprnova, the same shit.
all of them were ok a month ago, that's why i asked what changed ...
i just noticed the fixed rent gets killed every time when price jumps

Most of pools offer you ability to choose difficulty (via password for example) or they have high diff ports. Most of Scrypt pools are still stuck with old diff configs, when Scrypt was mined with GPUs. Diffs below 1024 were normal that time, but todays ASICs are 100-500x times faster thus they need 100-500x higher diff.

As explained already 2 pages back to another person who had the same problem, fixed orders have very small tolerance for dead time They get cancelled if being dead for more than 10% of the time.

well, that's it, 10%, and seems i've no use of fixed orders then.
as per theory, 6**** ports of cryptopia are just those high diff ones,
but that doesn't help, and suprnova "nicehash" ports don't help either,
those 10% deadtime happen to occur no matter,
or at least nicehash engine counts like that.
thanks anyway.....

Contact the pool you mine at and ask them for a diff raise. Using a diff 16384 is nothing unusual today and this is still very low diff for fast modern ASICs. It is just a matter of setting value in pool's config.
hero member
Activity: 588
Merit: 501

Your pool isn't using high enough difficulty.


this only means nicehash is incompatible with its vardiff behaviour these days,
becoz when i started, the diff was insane 90k not 4k.
coinmine.pw, coinotron, ipominer, and even 3-4 pools on suprnova, the same shit.
all of them were ok a month ago, that's why i asked what changed ...
i just noticed the fixed rent gets killed every time when price jumps

Most of pools offer you ability to choose difficulty (via password for example) or they have high diff ports. Most of Scrypt pools are still stuck with old diff configs, when Scrypt was mined with GPUs. Diffs below 1024 were normal that time, but todays ASICs are 100-500x times faster thus they need 100-500x higher diff.

As explained already 2 pages back to another person who had the same problem, fixed orders have very small tolerance for dead time They get cancelled if being dead for more than 10% of the time.
hero member
Activity: 588
Merit: 501

NiceHash on P2Pool.

I'm new to P2Pool. What's the best way to do this? I know latency time to the pool node is imperative, but when using Nice/West is that the time from the Nice/West servers or from the miners themselves? How does one determine what is the best node to use?

Use node that is closest to Amsterdam if you plan to use NiceHash or closest to San Jose (CA) if you plan to use WestHash.

Thanks for the info. Maybe someday you can set up P2Pool nodes right in your facilities in Amsterdam and San Jose, for maximum efficiency. That way we will always know exactly what node to connect to. I would happily pay a small fee for that much efficiency.

Any professionally hosted node in Amsterdam or San Jose will have <3 ms latency to us. We do not have plans to make such nodes on our own.
hero member
Activity: 503
Merit: 500

NiceHash on P2Pool.

I'm new to P2Pool. What's the best way to do this? I know latency time to the pool node is imperative, but when using Nice/West is that the time from the Nice/West servers or from the miners themselves? How does one determine what is the best node to use?

Use node that is closest to Amsterdam if you plan to use NiceHash or closest to San Jose (CA) if you plan to use WestHash.

Thanks for the info. Maybe someday you can set up P2Pool nodes right in your facilities in Amsterdam and San Jose, for maximum efficiency. That way we will always know exactly what node to connect to. I would happily pay a small fee for that much efficiency.
hero member
Activity: 588
Merit: 501
this system kills all of my fixed scrypt orders sooner or later,
actually i can't rent anymore, 12 different pools - no luck.
how that happened, what's changed ?

Give us order # and we will take a look into it. In most cases, problem is too low difficulty. Just make sure you use high difficulty and everything will be fine.

my last attempts that were killed #495299, #495264.
the rest of them simply couldn't start...

I ran your pool through pool verificator and got following result:


Your pool isn't using high enough difficulty.

NiceHash on P2Pool.

I'm new to P2Pool. What's the best way to do this? I know latency time to the pool node is imperative, but when using Nice/West is that the time from the Nice/West servers or from the miners themselves? How does one determine what is the best node to use?

Use node that is closest to Amsterdam if you plan to use NiceHash or closest to San Jose (CA) if you plan to use WestHash.
hero member
Activity: 503
Merit: 500
NiceHash on P2Pool.

I'm new to P2Pool. What's the best way to do this? I know latency time to the pool node is imperative, but when using Nice/West is that the time from the Nice/West servers or from the miners themselves? How does one determine what is the best node to use?
hero member
Activity: 588
Merit: 501
this system kills all of my fixed scrypt orders sooner or later,
actually i can't rent anymore, 12 different pools - no luck.
how that happened, what's changed ?

Give us order # and we will take a look into it. In most cases, problem is too low difficulty. Just make sure you use high difficulty and everything will be fine.
legendary
Activity: 1694
Merit: 1002
Go Big or Go Home.....
uh my deposit is always take so looooooooooooooooooooooooong to confirmed, it happen from 2 days ago..
it caused by bitcoin stressed test or what?



My deposits are quick, but I always send with a 6block speed. Not the fee-less that times out always.

On another note, the issue I've had with my fixed orders seems to be all set now. Thanks nicehash support on here for helping out.
I seemed irate, but I've never had issues with using the pools with no difficulty set before, and all of the sudden my fixed orders were getting canceled.
Seemed suspect. Seems ok now though if I specify correctly difficulty manually now.

Thanks.
Jump to: