Chris believes that the connectivity issues that some miners are experiencing today are caused by the configuration of Javapipe, our DDoS protection provider. They told him that we are one of their biggest users of data in their datacenters, and that they wanted to perform some optimizations to their networks to see if they can make things work better for us.
Chris is working back and forth with them through their support ticketing system to determine the cause of the problem and to see what differentiates customers who experience connectivity issues from those who do not experience issues. He'll update everyone later tonight with his findings.
Chris working to resolve more connectivity issues
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.
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.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Chris working to resolve more connectivity issues
Hi Steve,
This is off topic but would you please explain what is an 'orphaned' block, I think my earnings are low today and I am guessing that might be reason.
This is off topic but would you please explain what is an 'orphaned' block, I think my earnings are low today and I am guessing that might be reason.
Re: Chris working to resolve more connectivity issues
Ok never mind I am reading the Help part of the main page.
Re: Chris working to resolve more connectivity issues
Dear All,
I'm also experiencing connection issues. I also read, that some of you also have.
So, if I connect from my home ISP, the trace is:
...
6 10 ms 11 ms 10 ms at-vie05b-ri3-ae12-0.aorta.net [213.46.173.125]
7 10 ms 12 ms 11 ms ae6.cr0-vie2.ip4.gtt.net [46.33.84.85]
8 128 ms 127 ms 127 ms xe-5-0-2.cr1-chi1.ip4.gtt.net [89.149.141.177]
9 130 ms 129 ms 130 ms 427.xe2-0-0.br1.ch2.newcontinuum.net [173.205.36.74]
10 130 ms 130 ms 130 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 131 ms 138 ms 130 ms 29-96-79-64.as20278.net [64.79.96.29]
12 131 ms 132 ms 132 ms 215-14-88-167.reverse-dns [167.88.14.215]
This works fine.
However, if I connect from my "mining site" (different ISP), I can see this:
...
6 18 ms 17 ms 17 ms 81.183.3.131
7 35 ms 35 ms 35 ms decix1.ixreach.com [80.81.194.132]
8 137 ms 137 ms 137 ms s1.thn.lon.ixreach.com [91.196.187.65]
9 140 ms 139 ms 139 ms 31.217.130.38
10 138 ms 139 ms 138 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 139 ms 145 ms 149 ms 29-96-79-64.as20278.net [64.79.96.29]
12 139 ms 139 ms 139 ms 215-14-88-167.reverse-dns [167.88.14.215]
This is problematic: it is ok for ~2-3 minutes, but then disconnects for ~5-10 minutes.
(I'm not sure if information can help, I'm just trying)
Thx
I'm also experiencing connection issues. I also read, that some of you also have.
So, if I connect from my home ISP, the trace is:
...
6 10 ms 11 ms 10 ms at-vie05b-ri3-ae12-0.aorta.net [213.46.173.125]
7 10 ms 12 ms 11 ms ae6.cr0-vie2.ip4.gtt.net [46.33.84.85]
8 128 ms 127 ms 127 ms xe-5-0-2.cr1-chi1.ip4.gtt.net [89.149.141.177]
9 130 ms 129 ms 130 ms 427.xe2-0-0.br1.ch2.newcontinuum.net [173.205.36.74]
10 130 ms 130 ms 130 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 131 ms 138 ms 130 ms 29-96-79-64.as20278.net [64.79.96.29]
12 131 ms 132 ms 132 ms 215-14-88-167.reverse-dns [167.88.14.215]
This works fine.
However, if I connect from my "mining site" (different ISP), I can see this:
...
6 18 ms 17 ms 17 ms 81.183.3.131
7 35 ms 35 ms 35 ms decix1.ixreach.com [80.81.194.132]
8 137 ms 137 ms 137 ms s1.thn.lon.ixreach.com [91.196.187.65]
9 140 ms 139 ms 139 ms 31.217.130.38
10 138 ms 139 ms 138 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 139 ms 145 ms 149 ms 29-96-79-64.as20278.net [64.79.96.29]
12 139 ms 139 ms 139 ms 215-14-88-167.reverse-dns [167.88.14.215]
This is problematic: it is ok for ~2-3 minutes, but then disconnects for ~5-10 minutes.
(I'm not sure if information can help, I'm just trying)
Thx
Re: Chris working to resolve more connectivity issues
I also got kicked off with my rigs. when i try to reconnect they instantly fail over to backup pool.
While you look at this would you confirm that my solo mining today have been working and credited apropriately for today, thank you.
While you look at this would you confirm that my solo mining today have been working and credited apropriately for today, thank you.
Running rigs: KNC Titan, Antminer D3 & L3+'s
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: Chris working to resolve more connectivity issues
You are connecting a miner from your home site? Is it the same type of miner as you are connecting from the mining site?Lord11 wrote:Dear All,
I'm also experiencing connection issues. I also read, that some of you also have.
So, if I connect from my home ISP, the trace is:
...
6 10 ms 11 ms 10 ms at-vie05b-ri3-ae12-0.aorta.net [213.46.173.125]
7 10 ms 12 ms 11 ms ae6.cr0-vie2.ip4.gtt.net [46.33.84.85]
8 128 ms 127 ms 127 ms xe-5-0-2.cr1-chi1.ip4.gtt.net [89.149.141.177]
9 130 ms 129 ms 130 ms 427.xe2-0-0.br1.ch2.newcontinuum.net [173.205.36.74]
10 130 ms 130 ms 130 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 131 ms 138 ms 130 ms 29-96-79-64.as20278.net [64.79.96.29]
12 131 ms 132 ms 132 ms 215-14-88-167.reverse-dns [167.88.14.215]
This works fine.
However, if I connect from my "mining site" (different ISP), I can see this:
...
6 18 ms 17 ms 17 ms 81.183.3.131
7 35 ms 35 ms 35 ms decix1.ixreach.com [80.81.194.132]
8 137 ms 137 ms 137 ms s1.thn.lon.ixreach.com [91.196.187.65]
9 140 ms 139 ms 139 ms 31.217.130.38
10 138 ms 139 ms 138 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 139 ms 145 ms 149 ms 29-96-79-64.as20278.net [64.79.96.29]
12 139 ms 139 ms 139 ms 215-14-88-167.reverse-dns [167.88.14.215]
This is problematic: it is ok for ~2-3 minutes, but then disconnects for ~5-10 minutes.
(I'm not sure if information can help, I'm just trying)
Thx
We can't reproduce this issue currently.
Re: Chris working to resolve more connectivity issues
I tested it with the same version of NVIDIA ccminer. When ccminer can not connect, at the same time, the Antminers can not connect. So I think the issue is somewhere on the network. (Of course, it can be even a problem by my local ISP)Steve Sokolowski wrote:You are connecting a miner from your home site? Is it the same type of miner as you are connecting from the mining site?Lord11 wrote:Dear All,
I'm also experiencing connection issues. I also read, that some of you also have.
So, if I connect from my home ISP, the trace is:
...
6 10 ms 11 ms 10 ms at-vie05b-ri3-ae12-0.aorta.net [213.46.173.125]
7 10 ms 12 ms 11 ms ae6.cr0-vie2.ip4.gtt.net [46.33.84.85]
8 128 ms 127 ms 127 ms xe-5-0-2.cr1-chi1.ip4.gtt.net [89.149.141.177]
9 130 ms 129 ms 130 ms 427.xe2-0-0.br1.ch2.newcontinuum.net [173.205.36.74]
10 130 ms 130 ms 130 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 131 ms 138 ms 130 ms 29-96-79-64.as20278.net [64.79.96.29]
12 131 ms 132 ms 132 ms 215-14-88-167.reverse-dns [167.88.14.215]
This works fine.
However, if I connect from my "mining site" (different ISP), I can see this:
...
6 18 ms 17 ms 17 ms 81.183.3.131
7 35 ms 35 ms 35 ms decix1.ixreach.com [80.81.194.132]
8 137 ms 137 ms 137 ms s1.thn.lon.ixreach.com [91.196.187.65]
9 140 ms 139 ms 139 ms 31.217.130.38
10 138 ms 139 ms 138 ms xe2-0-3.br0.newcontinuum.net [173.243.122.246]
11 139 ms 145 ms 149 ms 29-96-79-64.as20278.net [64.79.96.29]
12 139 ms 139 ms 139 ms 215-14-88-167.reverse-dns [167.88.14.215]
This is problematic: it is ok for ~2-3 minutes, but then disconnects for ~5-10 minutes.
(I'm not sure if information can help, I'm just trying)
Thx
We can't reproduce this issue currently.
The problem started around 8/29 11:00PM UTC
Re: Chris working to resolve more connectivity issues
How is the fix coming along?
I can't wait to re-direct my 2 PinIdea (DR2 & DR3) toward my favorite pool again!
I can't wait to re-direct my 2 PinIdea (DR2 & DR3) toward my favorite pool again!
Re: Chris working to resolve more connectivity issues
"update your DNS records" Where? On the computer? In a mine? On Router? Poioit "stupid blonde" please !!!!
It seems that the site blocks IP addresses, they found a way to get rid of users! Those posts inform you that you need to update the DNC. I did it, on Saturday and everything worked fine until Wednesday, and now 5 minutes of connection and falls off to the reserve pool!
It seems that the site blocks IP addresses, they found a way to get rid of users! Those posts inform you that you need to update the DNC. I did it, on Saturday and everything worked fine until Wednesday, and now 5 minutes of connection and falls off to the reserve pool!
Re: Chris working to resolve more connectivity issues
The hash rate is unexpected low last few days...
Can somebody explain wha's happen?
Can somebody explain wha's happen?