Quote from: Theo1355 on December 08, 2013, 08:50:36 PM

Quote from: pluMmet on December 08, 2013, 04:11:35 PM

Quote from: sidehack on December 08, 2013, 03:22:25 PM

What's your command line look like for the proxy?

I wanted it to use Eligius so I used (Dogies suggestion): mining_proxy.py -o mining.eligius.st -p 3334 -cu 1yourSweetCoinsComeToThisAddress -cp x

Not only did it not work the terminal ignored that and was trying to connect to Slushs pool.

I ended up just doing: mining_proxy.py which had the slushs stuff already going and the blades synced up right away.

It looks like the proxy.py has been nurfed to just use slushes pool. I d/l'd two days ago for the slushes pool site and it's not .tar anymore but .zip. Still linux of course.. well py anyway.

I have them running now even though slushs pool is not awarding me anything.

Beyond that this is ridiculous. I had been using getwork just fine for months.. I obviously know how to do that but the blades just won't do it.

v2 blades btw.

Dude, I'm having the same problem with getwork-- it's so frustrating, especially when I didn't change anything, the blades just stopped connecting.

Let me know if you get it figured out; I'll reciprocate if I discover what's happening.

Will do, thanks.

It's a serious issue as I've tried lots of getwork pools and the blades don't work on any of them.