Bitcoin Forum

Other => Beginners & Help => Topic started by: Etnad on April 07, 2013, 03:49:12 AM



Title: Current Workaround for Slush's Pool
Post by: Etnad on April 07, 2013, 03:49:12 AM
Hi everyone, I've been here for a long time without any posts, but now I find some problem that I have a solution. Since I don't have permission to post in other section, I could only post this here.

At this moment, when your mining rigs try to connect to Slush's pool with the newest guiminer (20121203), you may find that it will randomly show an error message:

"No connections could be made because the target machine actively refused it",

causing your rigs to idle.

Here is my workaround:

1.Fall back to guiminer 20120219.
2.Because this version of guiminer does not support Stratum, you also need Slush's mining proxy to operate normally without warning message.
3.Start proxy, and then change your guiminer pool site to Other (localhost), with the same id and password for your miners in Slush's pool. Although this would appear as Solo mining, actually you'll be mining in Slush's pool via proxy.

Hope this could help :)