Chris working to resolve more connectivity issues

[Steve Sokolowski]

Chris spent the entire night troubleshooting the issue. He was able to discover that about 2% of packets going to the server are being dropped, so at least the issue is finally reproducible. Most people, though, don't have any problem at all and have never seen a disconnect.

We don't have any clue as to how to proceed to troubleshoot the issue, so Chris will be doing some Internet research today. Unfortunately, we do not have an ETA for when this problem will be resolved.

[LeGino]

Thank you for the update.
FYI, as of 08/31/17 15:00 EST both my ASIC X11s (DR2 & DR3) still cannot latch on.

[olkah]

Steve Chris no withdrawal BTC

[Steve Sokolowski]

"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 is no longer necessary to update your DNS cache. No action is required because it's been long enough that the DNS records should have propagated across the entire Internet already by now.

[LeGino]

My 2 ASIC X11 miners have been working all morning long now, after almost 3 days of been dropped.
Thank you.

[matthewlane2009]

I have been unable to direct my miner to your pool since the switch of the DNS.

Does anyone have any idea why, and how this problem can be solved on my end?

Thanks

traceroute to prohashing.com (167.88.15.87), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.267 ms 0.350 ms 0.212 ms
2 96.120.8.145 (96.120.8.145) 9.646 ms 9.861 ms 8.703 ms
3 te-0-1-0-4-sur02.scranton.pa.pitt.comcast.net (68.85.53.217) 9.004 ms 9.137 ms 8.625 ms
4 162.151.220.218 (162.151.220.218) 10.402 ms 8.956 ms 8.908 ms
5 96.108.4.237 (96.108.4.237) 14.129 ms 14.183 ms 14.299 ms
6 hu-0-15-0-0-ar01.mckeesport.pa.pitt.comcast.net (69.139.168.141) 21.885 ms 21.930 ms 23.110 ms
7 be-7016-cr02.ashburn.va.ibone.comcast.net (68.86.91.25) 44.771 ms 28.241 ms 28.492 ms
8 hu-0-10-0-1-pe04.ashburn.va.ibone.comcast.net (68.86.82.210) 27.460 ms 29.607 ms 29.696 ms
9 23.30.206.206 (23.30.206.206) 27.337 ms 27.321 ms 28.552 ms
10 89.149.141.245 (89.149.141.245) 68.678 ms xe-4-0-5.cr1-chi1.ip4.gtt.net (89.149.141.173) 58.822 ms 89.149.141.245 (89.149.141.245) 56.981 ms
11 427.xe2-0-0.br1.ch2.newcontinuum.net (173.205.36.74) 66.835 ms 56.525 ms 69.621 ms
12 xe2-0-3.br0.newcontinuum.net (173.243.122.246) 65.880 ms 60.630 ms 57.934 ms
13 29-96-79-64.as20278.net (64.79.96.29) 57.249 ms 64.362 ms 56.855 ms
14 87-15-88-167.reverse-dns (167.88.15.87) 57.526 ms 56.160 ms 56.265 ms

[gnode]

Are you using

stratum+tcp://prohashing.com:3333

instead of just prohashing.com:3333?

[matthewlane2009]

No, I was not, I was just copying and pasting the URL from the help page.

I just switched to exactly what you typed above and it still showing dead

Thanks for trying to help though!

[Steve Sokolowski]

No, I was not, I was just copying and pasting the URL from the help page.

I just switched to exactly what you typed above and it still showing dead

Thanks for trying to help though!

Someone reported that there might be an issue with specific usernames. We're going to investigate this on Thursday, as we may have a reproducible test case. We'll keep everyone informed about what we find.

[matthewlane2009]

I made a new username as well to matthewlane2017, and that did not change the status, if this helps you at all.

Thanks