Quote from: sidehack on December 12, 2013, 03:38:36 PM

If you wait a moment, does it start listening for work? Sometimes mine give errors like that but then fire up just fine.

Also I was testing a bit with running two proxies the other day, and was having some issues with the second one connecting on 8333. 8332 and 8335 work just fine on my setup, not sure if using two ports so close is messing it up or what.

Yes it finds work on the slush mining port, 8332. That works fine, but the blade I have setup for BTCguild doesn't find any work. The ports on the blade are set to 8333,8333 and correct user:pass but it just never finds any work. I've tried 8335 as well.

I've had the BTCguild settings working through a cloud proxy but just not through my own proxy.

Thanks for your help though, I'll keep at it.