ETHash Issues | Connection error

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.
Locked
DennYoDeluxe
Posts: 4
Joined: Fri Mar 19, 2021 4:39 pm

ETHash Issues | Connection error

Post by DennYoDeluxe » Fri Mar 19, 2021 5:27 pm

Connection and Authorization Errors since 06:15 CET

----1st Miner, AMD GPU 8GB Card----------
1st Miner on eu.prohashing.com:
Lost Conenction to stratum server eu.prohashing.com:3339 or server not reachable

Same Miner with prohashing.com:
Worker xxx not authorized

Sometimes I receive jobs, often I got the above errors.

----2nd miner, NVidia 4GB Card----
I have a second miner with 4096 GB of RAM which I needed to configure using only 3072 and give password l=3
This one is completely not working, immediate looses conenction.
Error:
Connection Errors Detected
DISCONNECT (268)
6 seconds ago
The worker does not meet the DAG requirement of all available coins in the algorithm.

It used to work until today morning. What happend? Any CHanges? It was good for Expanses...

----debug info----

nslookup:

Nicht autorisierende Antwort:
Name: eu.prohashing.com
Address: 5.254.118.160

Name: prohashing.com
Address: 50.220.121.209

ping:
Ping wird ausgeführt für eu.prohashing.com [5.254.118.160] mit 32 Bytes Daten:
Antwort von 5.254.118.160: Bytes=32 Zeit=34ms TTL=52
Antwort von 5.254.118.160: Bytes=32 Zeit=33ms TTL=52
Antwort von 5.254.118.160: Bytes=32 Zeit=33ms TTL=52
Antwort von 5.254.118.160: Bytes=32 Zeit=33ms TTL=52

Ping wird ausgeführt für prohashing.com [50.220.121.209] mit 32 Bytes Daten:
Antwort von 50.220.121.209: Bytes=32 Zeit=107ms TTL=49
Antwort von 50.220.121.209: Bytes=32 Zeit=105ms TTL=49
Antwort von 50.220.121.209: Bytes=32 Zeit=105ms TTL=49
Antwort von 50.220.121.209: Bytes=32 Zeit=105ms TTL=49

Miner:
lolminer 1.21


regards,
Dennis
Top
Nosferatu272
Posts: 5
Joined: Mon Feb 15, 2021 12:19 pm

Re: ETHash Issues | Connection error

Post by Nosferatu272 » Fri Mar 19, 2021 5:37 pm

#metoo xD
eu does not respond at all, main gives jobs above my gpu ram limit (4gb) and i cannot set to static (expanse or nekonium) cause it shows there is no such coin available to mine
Top
DennYoDeluxe
Posts: 4
Joined: Fri Mar 19, 2021 4:39 pm

Re: ETHash Issues | Connection error

Post by DennYoDeluxe » Mon Mar 22, 2021 5:34 pm

Still having huge connection losses, also one of my friends (other city, other provider, ...)

tcping -t eu.prohashing.com 3339

** Pinging continuously. Press control-c to stop **

Probing 5.254.118.160:3339/tcp - No response - time=2000.698ms
Probing 5.254.118.160:3339/tcp - No response - time=2015.427ms
Probing 5.254.118.160:3339/tcp - No response - time=2002.557ms
Probing 5.254.118.160:3339/tcp - No response - time=2019.314ms
Probing 5.254.118.160:3339/tcp - No response - time=2002.438ms
Probing 5.254.118.160:3339/tcp - No response - time=2002.313ms
Top
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: ETHash Issues | Connection error

Post by Steve Sokolowski » Tue Mar 23, 2021 8:51 am

DennYoDeluxe wrote: ↑Mon Mar 22, 2021 5:34 pm Still having huge connection losses, also one of my friends (other city, other provider, ...)

tcping -t eu.prohashing.com 3339

** Pinging continuously. Press control-c to stop **

Probing 5.254.118.160:3339/tcp - No response - time=2000.698ms
Probing 5.254.118.160:3339/tcp - No response - time=2015.427ms
Probing 5.254.118.160:3339/tcp - No response - time=2002.557ms
Probing 5.254.118.160:3339/tcp - No response - time=2019.314ms
Probing 5.254.118.160:3339/tcp - No response - time=2002.438ms
Probing 5.254.118.160:3339/tcp - No response - time=2002.313ms
I'll create a ticket about this and assign it to Chris for investigation.
Top
Locked

Return to “System support”