Oh, nice change! I'll merge this in and release a new version ASAP.

There may still be problems with SC3; It's been deprecated by Sauce Labs and it's acting kind of shaky. But we can at least give you the possibility of using it.

Thank you @DylanLacey
I wans't aware that sauce_connect 3 is deprecated.
How would one know about it?
So what is the supported way of using sauce_ruby? Download a sc4 binary, move somewhere on the disk and add the binary's path to config[:sauce_connect_4_executable] ?
Many Thanks,
David

There's been a bit of discussion about this internally. ATM the process is to download a binary and set config[:sauce_connect_4_executable]. I want to patch the gem to download the latest binary based on the installing platform, but that's on the 'todo' list. The eventual goal is to get a natively bound version.

SC 3 was deprecated about a year ago; Sauce Labs emailed all customers at the time and removed download links for SC3 but didn't EOL Sauce Connect 3 at the time. We've just set an EOL date for Sauce Connect 3 support for the small number of customers still using it - 1 August 2015.

But, SC3 stopped working reliably some time ago because of various protocol deprecations, security scares for the community in general and because much of the Sauce Connect effort was focused on improving SC4.