Difficulty in connecting minerd to BTC Guild.

[usao]

Ive created an account at BTC Guild, and have a USB miner on order. While im waiting for that to show up (backordered), I thought I would try to get a micro-BTC or two using the cpuminer (minerd.exe).
However, im getting an error as shown below. Im using my real username and the _1 (worker suffix). BTC Guild said the password was not required, so just used a dummy one "123" per their notes. I already checked that I can ping the host and port, so it's not a network firewall or other issue that im familiar with.

$ ./minerd.exe -o "http://stratum.btcguild.com:3333" -O "username_1:123"
[2013-12-09 16:23:04] Binding thread 0 to cpu 0
[2013-12-09 16:23:04] Binding thread 2 to cpu 2
[2013-12-09 16:23:04] 8 miner threads started, using 'scrypt' algorithm.
[2013-12-09 16:23:04] Binding thread 6 to cpu 6
[2013-12-09 16:23:04] Binding thread 7 to cpu 7
[2013-12-09 16:23:04] Binding thread 5 to cpu 5
[2013-12-09 16:23:04] Binding thread 1 to cpu 1
[2013-12-09 16:23:04] Binding thread 3 to cpu 3
[2013-12-09 16:23:04] Binding thread 4 to cpu 4
[2013-12-09 16:23:26] HTTP request failed: Failed connect to stratum.btcguild.com:3333; No error
[2013-12-09 16:23:26] json_rpc_call failed, retry after 30 seconds

[1714052729]

1714052729

[1714052729]

1714052729

[1714052729]

1714052729

[sweetNlow]

Seems like you're trying to mine in scrypt algorithm, need to change it to sha-256, was able to find this for minerd, hope it helps!

Q: What's the difference between the two available algorithms, scrypt and sha256d?
A: They are completely different proof-of-work algorithms. You must use scrypt for Litecoin, and you must use sha256d for Bitcoin. The default algorithm is scrypt, so for Bitcoin mining you have to specify --algo=sha256d.

[usao]

Tried that algorithm, and it didn't really change the results...

$ ./minerd.exe -a sha256d -o "https://stratum.btcguild.com:3333" -O "username_1:123"
[2013-12-09 16:59:01] Binding thread 0 to cpu 0
[2013-12-09 16:59:01] Binding thread 1 to cpu 1
[2013-12-09 16:59:01] Binding thread 2 to cpu 2
[2013-12-09 16:59:01] Binding thread 3 to cpu 3
[2013-12-09 16:59:01] Binding thread 4 to cpu 4
[2013-12-09 16:59:01] Binding thread 5 to cpu 5
[2013-12-09 16:59:01] Binding thread 6 to cpu 6
[2013-12-09 16:59:01] 8 miner threads started, using 'sha256d' algorithm.
[2013-12-09 16:59:01] HTTP request failed: Protocol https not supported or disabled in libcurl
[2013-12-09 16:59:01] json_rpc_call failed, retry after 30 seconds
[2013-12-09 16:59:01] Binding thread 7 to cpu 7

[sweetNlow]

hmmm... try removing the https:// from the host, see if that works

[usao]

It changed the error message to:

[2013-12-09 17:12:12] HTTP request failed: Empty reply from server

[sweetNlow]

Hmmm I'm not sure bud. I found this for your previous error message:

3.21 Protocol xxx not supported or disabled in libcurl

When passing on a URL to curl to use, it may respond that the particular protocol is not supported or disabled. The particular way this error message is phrased is because curl doesn't make a distinction internally of whether a particular protocol is not supported (i.e. never got any code added that knows how to speak that protocol) or if it was explicitly disabled. curl can be built to only support a given set of protocols, and the rest would then be disabled or not supported.

Note that this error will also occur if you pass a wrongly spelled protocol part as in "htpt://example.com" or as in the less evident case if you prefix the protocol part with a space as in " http://example.com/".

If you're still stuck hopefully someone more knowledgable will come along and shed some light.

Edit: In my command line for cgminer I use "stratum.btcguild.com:3333" to connect, not sure if it's the same with minerd.