I moved all of my miners over to the 3333. I'll test 443 again later and let you know. Thanks for being on top of it!

Happy to help!

Just as a follow up, it doesn't happen when using prohashing.com:3333.

Hi;

I've been noticing over the past few days that some of my miners are suffering a reconnect every 15 minutes or so using the proxy.prohashing.com:443 settings. Is something up?

I have friends and colleagues in the data center industry that pay bulk rates for their power, not per kWh, and hence, the power would be covered in the cost of the hosted racks.

There's good deals on power if you look in the right places.

Thanks for the info. I'll keep you on the up and up as/if plans turn closer into reality.

A question for Chris and Steve (but open to everyone): I've been reviewing and attempting to plan out a major hashing setup. I was wondering if there is a theoretical limit on what a single user can contribute, in total hash rate, to the pool, before it would be considered overwhelming or too much? ...

I realize this is an old problem, but I do not see if it was resolved or not. I was thinking of trying Minera as well as a distribution for controllers, but with the problems I've faced recently I was able to track them back down to the version of BFGMiner I was using and using a static difficulty a...

As another follow up for fellow Zeus operators, I updated my BFGMiner software on all my controllers to 5.4. Some of the 5.2 versions seemed to be inconsistent and causing some problems too. In short, I use d=2048 r=0.35 and BFGMiner 5.4 and things are now running more smoothly (with a slightly high...

Pleased to report that after the system maintenance yesterday and my miners restarting their daemons, the errors have gone away.