Update on the pool downtime

News updates about the Prohashing pool
Forum rules
The News forum is only for updates about the Prohashing pool.

Replies to posts in this forum should be related to the news being announced. If you need support on another issue, please post in the forum related to that topic or seek one of the official support options listed in the top right corner of the forums page or on prohashing.com/about.

For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
siberianbreaks
Posts: 17
Joined: Mon May 08, 2017 3:49 pm

Re: Update on the pool downtime

Post by siberianbreaks » Tue Jun 20, 2017 5:06 pm

Thank you for the hard work
radriga
Posts: 4
Joined: Tue Jun 20, 2017 5:13 pm

Re: Update on the pool downtime

Post by radriga » Tue Jun 20, 2017 5:16 pm

Hi Steve and Chris.

Thanks a lot for you work.
28 hours for VPN setup is too much time.
If in future you will need assistance from qualified linux system administrator, you can ask me ;)
User avatar
Chris Sokolowski
Site Admin
Posts: 945
Joined: Wed Aug 27, 2014 12:47 pm
Location: State College, PA

Re: Update on the pool downtime

Post by Chris Sokolowski » Tue Jun 20, 2017 5:36 pm

To be fair, it wasn't just a simple VPN. My challenge was in networking - getting the networking config right for a single VPN server that accepts data from four different clients with four different subnets and distributes data to four external IP addresses. Also, I had to make sure that our actual IP addresses are blocked from external access and completely untraceable and that all this is resilient to system restarts and internet outages.
User avatar
FRISKIE
Posts: 117
Joined: Sun Apr 16, 2017 12:51 pm

Re: Update on the pool downtime

Post by FRISKIE » Tue Jun 20, 2017 5:41 pm

I have enough of a hosting services background to appreciate the challenge you describe!

What's left to do before mining can resume?
Nalith
Posts: 5
Joined: Fri Apr 28, 2017 2:08 pm

Re: Update on the pool downtime

Post by Nalith » Tue Jun 20, 2017 5:47 pm

Thanks for all the effort you guys are putting in to bring the service back and make it more resilient.
User avatar
VanessaEzekowitz
Posts: 24
Joined: Sun Apr 16, 2017 4:01 pm

Re: Update on the pool downtime

Post by VanessaEzekowitz » Tue Jun 20, 2017 6:35 pm

I'm glad to see things are starting to get back to normal here. Thanks for all the hard work, guys!
Join Hashflare, make some money, and help a crabby old battle axe earn too, using my referral link:
https://hashflare.io/r/19027B79
User avatar
Steve Sokolowski
Posts: 4585
Joined: Wed Aug 27, 2014 3:27 pm
Location: State College, PA

Re: Update on the pool downtime

Post by Steve Sokolowski » Tue Jun 20, 2017 6:48 pm

Chris has gotten everything back online.

People who mine during the first hour or so are going to earn a fortune, perhaps with scrypt profitability as high as a dollar, because the coin networks are all at a low difficulty from not having been mined for so long.

Feel free to report any issues. Thanks for your patience! Chris will be working with Comcast for a solution that will cut 15ms off the latencies in the future.
User avatar
GGabox
Posts: 1
Joined: Tue Jun 20, 2017 7:50 pm

Re: Update on the pool downtime

Post by GGabox » Tue Jun 20, 2017 7:52 pm

Live worker status (0)

No connection.
European IP address.

All machines restarted.

Image
edonkey
Posts: 11
Joined: Thu Aug 27, 2015 9:48 am

Re: Update on the pool downtime

Post by edonkey » Tue Jun 20, 2017 9:10 pm

I can't get to the main prohashing.com site. Still shows as server unavailable.

But when I use one of those sites that double checks availability, it says the site is live:

http://downforeveryoneorjustme.com/prohashing.com

Maybe there's a routing problem where the site is working for some locations but not others?
edonkey
Posts: 11
Joined: Thu Aug 27, 2015 9:48 am

Re: Update on the pool downtime

Post by edonkey » Tue Jun 20, 2017 10:23 pm

I can see the main site now.

Looks like there's a tweet that I didn't see rcommending purging the DNS cache. I didn't see that before.

Maybe my problem earlier was a stale DNS entry?

Anyway, looks like you guys are back. Good work! I know that this stuff is hard.
Locked