Read-only forum archive. PROHASHING has closed. Posting, registration, and account access are unavailable. Preserved from the April 3, 2026 server backup.

Chat archive · 2017-07

FRISKIE · · #11404

wit it ut, take a while :D

FRISKIE · · #11405

Just think, if thos Konov fixed 100H and other big orders are facign PH, they ar losing such huge money right now!

Steve Sokolowski · · #11406

good morning!

fattygrub · · #11407

looks ok now..

Steve Sokolowski · · #11408

I’m not sure what is going on here

mickeekung · · #11409

Good morning Steve ^^

Steve Sokolowski · · #11410

there is lots of text chat but no overview

mickeekung · · #11411

You just got DDoS attack about an hour ago and Worker Workers: 11592.

Steve Sokolowski · · #11412

are you sure there was an attack?

Steve Sokolowski · · #11413

that’s a really difficult type of attack to execute

mickeekung · · #11414

During that time stale share 100 percent lost.

FRISKIE · · #11415

y to express how much steve and chris are loved

fattygrub · · #11416

started around 6:00 am EST ...started noticing delay in shares which grew to about a one hour delay...meanwhile pool hash dropped slowly to about 150G ... while number of workers rose and rose to aver 11,000 .. everyone seemed to not be able to connect well if at all

mickeekung · · #11417

The attackers might gone when you wakes up Steve.

Steve Sokolowski · · #11418

that sounds more like a bug than an attack

Steve Sokolowski · · #11419

I’ll do some research later today

Steve Sokolowski · · #11420

for now, it seems to me that the system is back to normal

Steve Sokolowski · · #11421

I’ll monitor this, but I don’t think there was an attack

FRISKIE · · #11422

What about Konov and the NH manipulation, any thoughts?

AvPro · · #11423

Steve Sokolowski wrote: that’s a really difficult type of attack to execute
we rocketed from 2000workers to 12,000 workers in a couple hours

FRISKIE · · #11424

Which coins would have benefitted?

AvPro · · #11425

It was long enough downtime for probably a lot of coins to cycle through a low diff period

Steve Sokolowski · · #11426

AvPro wrote:
Steve Sokolowski wrote: that’s a really difficult type of attack to execute
we rocketed from 2000workers to 12,000 workers in a couple hours
it sounds like a bug where something happened that caused existing miners to reconnect and the mining server didn’t close the old connections

LMC · · #11427

Steve Sokolowski wrote:
AvPro wrote:
Steve Sokolowski wrote: that’s a really difficult type of attack to execute
we rocketed from 2000workers to 12,000 workers in a couple hours
it sounds like a bug where something happened that caused existing miners to reconnect and the mining server didn’t close the old connections
I just sent thru an email on @ghost@ miners...

Steve Sokolowski · · #11428

LMC wrote:
Steve Sokolowski wrote:
AvPro wrote: we rocketed from 2000workers to 12,000 workers in a couple hours
it sounds like a bug where something happened that caused existing miners to reconnect and the mining server didn’t close the old connections
I just sent thru an email on @ghost@ miners...
To which address? I didn’t receive a notification

LMC · · #11429

contact"....

Forum notification · · #11430

has started a new topic: Status as of Saturday, July 8, 2017

wkying79 · · #11431

hey guys, would a period of over an hour of 100% rejection be caused from this bug/attack? That’s what happened to me from 5-6am. taking a loss because of it

taka · · #11432

I joined bitcoin club in Thailand so almost people mining by gbu seldom mining by asic or antminer >

taka · · #11433

Mickeekung

mickeekung · · #11434

Yes :)

fattygrub · · #11435

anyone else having trouble with connecting to pool with NH? keeps getting error timed out

fattygrub · · #11436

shares are 7 minutes delayed

fattygrub · · #11437

there is something wrong again...

fattygrub · · #11438

cannot connect from hicehash

fattygrub · · #11439

occassionally the nicehash "verificator" tool will connect but..

fattygrub · · #11440

if you are familiar with NH’s "pool verificator tool" try it, see what you get. [11:00] ok that time it connected but again i am sending: Pool pass: n=fattythree d=8192 h=1000 g=off and getting back: Received mining.set_difficulty... OK: difficulty=16384

fattygrub · · #11441

so there is something wrong with the diff

fattygrub · · #11442

as well as not being able to place NH orders at all right now

FRISKIE · · #11443

I'm profitable on NH all day, what;s up?

FRISKIE · · #11444

Stupid Konov trying to mess us up, he;s a fool, you can work around it :D

fattygrub · · #11445

orders won’t come out of the NH red/dead zone and their pool verificator is either not connecting at all or getting back a bogus diff from PH

FRISKIE · · #11446

what are your args?

FRISKIE · · #11447

can you see thishttps://ibb.co/ipvahv

FRISKIE · · #11448

https://ibb.co/ipvahv

fattygrub · · #11449

same as they’ve been for a month and a half: d=8192 h=1000 g=off

fattygrub · · #11450

yeah that order graph looks good... guess i’ll just keep trying

FRISKIE · · #11451

Standard order are or working for me very well, . . monitoring them and moving up and down a little and adding in shashrate sometimes is profitable

FRISKIE · · #11452

sure mate, its working find, you hit a ad luck time :)

fattygrub · · #11453

nope: Establishing connection with pool 192.3.198.21:3333... Error: Read timed out

FRISKIE · · #11454

do you have a VPN?

FRISKIE · · #11455

Use it

fattygrub · · #11456

nope. everything the same this end as it’s been .... yesterday mad 22.3% on 600 bucks.... today looks like it going to be nothing

FRISKIE · · #11457

with a VPN?

FRISKIE · · #11458

fire up your VPN , then try connections again

fattygrub · · #11459

thanks really for your help, but even if i ever used vpn, how would that fix the apparent connection problem between PH and NH?

FRISKIE · · #11460

Theres a chance you have a blacklisted IP over there, Konov is an ass

FRISKIE · · #11461

Often a VPN is its a good one supporting all protocols just presents a fresh stat and everything goes well

FRISKIE · · #11462

Nothing lost to try it, right? so just do it :D

fattygrub · · #11463

no i finally got in on that last run...burning 30G’s for a few minutes at 50%+ hehe

FRISKIE · · #11464

lovely, post the graph for me?

fattygrub · · #11465

there is a bot on the USA side right now that i can’t beat right now...so... looks like i’m in the EU for a minute 8-)

FRISKIE · · #11466

I'm i UE as well . . easier to push a high G rate

fattygrub · · #11467

yes and sometimes the peeps there seem a little more laid back

FRISKIE · · #11468

uhum, I see it too, that;s when I go away and read a book, I am in no hurry :Z

FRISKIE · · #11469

Konov is losing, too manyz paople findingout its ok to be patient, set your order low enough to be profitable, and go away :D

FRISKIE · · #11470

meanwhile his bit 100G orders try to make NH uunusable for the normal guys , but it failed.

FRISKIE · · #11471

KONOV IS A FAILURE

FRISKIE · · #11472

I am making moneyy and enjoying myself by making money in calm ways ,

wkying79 · · #11473

can anyone point me out to the proper channels to ask for a missed payout? Last night’s payout didn’t happen for me and i was above the threshold

fattygrub · · #11474

contact@prohashing.com unless you can get a ticket into support.prohashing.com

wkying79 · · #11475

k

wkying79 · · #11476

turnaround times the same for email and/or support tickets?

fattygrub · · #11477

they jsut sent the support site up... it just worked for to set up ccount, set password, etc.... so i would start using that first

wkying79 · · #11478

yea i like support ticket systems more myself.. will give it a go

mickeekung · · #11479

@wkying79 Which payout coin? Please let me know.

fattygrub · · #11480

same deal for last half hour cannot get NH to connect... losing money because PH is not working ... Establishing connection with pool 192.3.198.21:3333... Error: Read timed out

wkying79 · · #11481

@mickeekung my BTC payouts didn’t kick in

fattygrub · · #11482

and again from NH: Establishing connection with pool 192.3.198.21:3333... Error: Read timed out

wkying79 · · #11483

i just checked pool verificator on NH and the USA server timed out. then europe one worked. then USA worked

wkying79 · · #11484

so maybe that means its in and out?

fattygrub · · #11485

right, they are on and off, off then on, then sending back bogus diff, then off again, and so on and on and on and on

fattygrub · · #11486

never seenthis behavior between PH & NH before... so something is up...uh....again

fattygrub · · #11487

NH again: Establishing connection with pool 192.3.198.21:3333... Error: Read timed out

mickeekung · · #11488

Is it possible that Nicehash block Prohashing?

fattygrub · · #11489

not unless they are doing it intermittently.. cause i ran great from there 3 hours this morning then two+ hours this afternoon.

fattygrub · · #11490

maybe they do have someone clicking a "turn prohashing on" and a "turn prohashing off": button but i seriously doubt it.

fattygrub · · #11491

From NH: Establishing connection with pool 192.3.198.21:3333... Error: Read timed out

siberianbreaks · · #11492

100% negative delta at nh

mickeekung · · #11493

me too related to read time out

tmopar · · #11494

mickeekung wrote: Is it possible that Nicehash block Prohashing?
I have considered this also but it would mean that they are actively competing against them otherwise it would not make sense to cut off a legit source of orders

fattygrub · · #11495

i just tested my nicehash connection to three other pools, and everything checked out ok. so either : 1. nicehash is unable to connect with PH or 2. PH is unable to accept NH connects 3. or both i cannot be the only only one experiencing this. i proved it by verifying with others on different machines on different ip’s with the same bad results. tickets have been sent to PH and NH support.

Steve Sokolowski · · #11496

Chris is trying to determine where the problem lies

fattygrub · · #11497

thanks steve, this is very upsetting right now. i appreciate your attention.

mickeekung · · #11498

Nicehash seem like OK right now.

fattygrub · · #11499

right now yes, try again in one minute ... i just got Received mining.set_difficulty... OK: difficulty=16384 when i ask for d=8192... and ny order is still dead

FRISKIE · · #11500

keep difficulty at 16384 or above

FRISKIE · · #11501

This is a usual standard now across any pools I work with, anyway be on the safe side, a bit to high difficulty will not do you badly, and you can calibrate it later\

andrianto · · #11502

Does anyone use miningrigrental ?

tmopar · · #11503

most of us run our own hardware or use NH... but they have been ahving problems lately