Prohashing Mining Pool Forums

I am having connect issues also. I have a few L3+ miners. They show up on the pool hashing for some time then dissapear.

I check the miner status and it shows a Dead status on the stratum+tcp://prohashing.com:3333 for some time then they connect again after sometime or whenever.

I noticed it happened to me two days ago, they all went down and I had zero miners.. It may have been hours so I switched to another pool for a couple days.

Came back today and I am getting the same thing of miners dropping off after a while and showing Dead status on my L3+ miner status.

Am i on the wrong stratum+tcp?

Anyone else having similar problems with the L3+ ??

still happening today randomly.

as an update I have 10 of my miners Dead. Whats causing them to drop?

Also, to test this out yourself easily, just use http://www.letmecheck.it/tcp-ping.php

Here is the results for prohashing.com:

Ping Output:

Pinging prohashing.com (167.88.15.87) via TCP on port 3333 using IPv4.
From prohashing.com (167.88.15.87): seq=1 (filtered)
From prohashing.com (167.88.15.87): seq=2 (filtered)
From prohashing.com (167.88.15.87): seq=3 (filtered)
From prohashing.com (167.88.15.87): seq=4 (filtered)

--- prohashing.com ping statistics ---
4 connections attempted, 0 successful, 100% loss, time 52477 ms

---- Finished ------


For comparison here is zpool:

Ping Output:

Pinging scrypt.mine.zpool.ca (149.56.122.79) via TCP on port 3433 using IPv4.
TCP Handshake from scrypt.mine.zpool.ca (149.56.122.79): seq=1 time=103 ms
TCP Handshake from scrypt.mine.zpool.ca (149.56.122.79): seq=2 time=102 ms
TCP Handshake from scrypt.mine.zpool.ca (149.56.122.79): seq=3 time=124 ms
TCP Handshake from scrypt.mine.zpool.ca (149.56.122.79): seq=4 time=104 ms

--- scrypt.mine.zpool.ca ping statistics ---
4 connections attempted, 4 successful, 0% loss, time 4539 ms

---- Finished ------

its possible they have ICMP turned off as it can be used to flood packets to the server, they are using javapipe remember. ICMP Ping does not mean the server is down

GregoryGHarding wrote:its possible they have ICMP turned off as it can be used to flood packets to the server, they are using javapipe remember. ICMP Ping does not mean the server is down

That very well might be the case, but that ping utility is supposed to use TCP not ICMP. My understanding is that there is no real TCP ping, but they basically just open up a connection and check if that works. That should be useful in this case since that seems to be what is going wrong. I could be mistaken, but the result matches what I was expecting. I will turn up the connection attempts and make sure that at least one eventually goes though.

Ok, Here we go, you can see that some did get through. 90% failure rate though:

Ping Output:

Pinging prohashing.com (167.88.15.87) via TCP on port 3333 using IPv4.
From prohashing.com (167.88.15.87): seq=1 (filtered)
From prohashing.com (167.88.15.87): seq=2 (filtered)
From prohashing.com (167.88.15.87): seq=3 (filtered)
From prohashing.com (167.88.15.87): seq=4 (filtered)
TCP Handshake from prohashing.com (167.88.15.87): seq=5 time=1157 ms
From prohashing.com (167.88.15.87): seq=6 (filtered)
From prohashing.com (167.88.15.87): seq=7 (filtered)
From prohashing.com (167.88.15.87): seq=8 (filtered)
From prohashing.com (167.88.15.87): seq=9 (filtered)
From prohashing.com (167.88.15.87): seq=10 (filtered)
From prohashing.com (167.88.15.87): seq=11 (filtered)
From prohashing.com (167.88.15.87): seq=12 (filtered)
From prohashing.com (167.88.15.87): seq=13 (filtered)
From prohashing.com (167.88.15.87): seq=14 (filtered)
TCP Handshake from prohashing.com (167.88.15.87): seq=15 time=167 ms
From prohashing.com (167.88.15.87): seq=16 (filtered)
From prohashing.com (167.88.15.87): seq=17 (filtered)
From prohashing.com (167.88.15.87): seq=18 (filtered)
From prohashing.com (167.88.15.87): seq=19 (filtered)
From prohashing.com (167.88.15.87): seq=20 (filtered)

--- prohashing.com ping statistics ---
20 connections attempted, 2 successful, 90% loss, time 238076 ms

---- Finished ------

gestalt wrote:

GregoryGHarding wrote:its possible they have ICMP turned off as it can be used to flood packets to the server, they are using javapipe remember. ICMP Ping does not mean the server is down

That very well might be the case, but that ping utility is supposed to use TCP not ICMP. My understanding is that there is no real TCP ping, but they basically just open up a connection and check if that works. That should be useful in this case since that seems to be what is going wrong. I could be mistaken, but the result matches what I was expecting. I will turn up the connection attempts and make sure that at least one eventually goes though.

the tcp ping tool is a tool based on ICMP. its possible javapipe is throttling specific protocals

Chris is investigating whether there is some sort of Linux connection limit that is set at the default but can be increased. Hopefully, he'll have more information soon.

It's not a nicehash problem

Nicehash -> some other pool.. OK
Nicehash -> Prohashing... sucks
My local miner (R1 LTC) -> Prohashing. connecting to the remote pool.. after 30 minutes (approx) authorization failed / or connected for a while and then sucks


so please don't tell me it's nicehash related, because it's not. it's probably your ISP or linux server itself (check max_connections or some similar parameters).. also please hire some1 who you know and trust, to help you and Chris , because you 2 are not enough for this job, to be honest..

tomos81 wrote:It's not a nicehash problem

Nicehash -> some other pool.. OK
Nicehash -> Prohashing... sucks
My local miner (R1 LTC) -> Prohashing. connecting to the remote pool.. after 30 minutes (approx) authorization failed / or connected for a while and then sucks


so please don't tell me it's nicehash related, because it's not. it's probably your ISP or linux server itself (check max_connections or some similar parameters).. also please hire some1 who you know and trust, to help you and Chris , because you 2 are not enough for this job, to be honest..

We haven't heard from the lawyer today, and we need to hear from him before we can proceed any further. Until then, we're going to close registrations again.

We want to hire people as much as you do, but there are lots of rumors of representatives and senators wanting to introduce regulations that might make the business unprofitable. Once we get more certainty, then we may decide to move forward.