[Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 22.

vesperwillow

hero member

Activity: 616

Merit: 500

Quote from: ccplz on November 20, 2013, 11:56:44 AM

Quote from: vesperwillow on November 20, 2013, 11:45:03 AM

Change your secondary DNS to match your primary. No need for it to point to an external because if you're offline it's moot.

Also, I would suggest using BFGMiner as a proxy instead of slush's. I've seen slush's have issues which couldn't be explained, but BFGMiner is always spot-on.

If possible, use a port other than 8332 to rule out port issues. I usually suggest folks use 8339 or something else easy to remember. Make sure the change is in blade setup, and the proxy knows to listen on the same port.

Yeah,I thought of using BFGminer,however I read somewhere that using it as a proxy requires a x32 OS.
Is it true?

They have x64 builds for Windows, but not sure if they have the built-in proxy support for Windows 8x64. You could always give it a shot.

Still, I'd focus on your port and DNS settings. Make the changes and see what happens. If you have an older computer you can toss XP or Ubuntu on, even better, because you could use BFGMiner for sure.

ccplz

full member

Activity: 258

Merit: 116

Quote from: vesperwillow on November 20, 2013, 11:45:03 AM

Change your secondary DNS to match your primary. No need for it to point to an external because if you're offline it's moot.

Also, I would suggest using BFGMiner as a proxy instead of slush's. I've seen slush's have issues which couldn't be explained, but BFGMiner is always spot-on.

If possible, use a port other than 8332 to rule out port issues. I usually suggest folks use 8339 or something else easy to remember. Make sure the change is in blade setup, and the proxy knows to listen on the same port.

Yeah,I thought of using BFGminer,however I read somewhere that using it as a proxy requires a x32 OS.
Is it true?

vesperwillow

hero member

Activity: 616

Merit: 500

Change your secondary DNS to match your primary. No need for it to point to an external because if you're offline it's moot.

Also, I would suggest using BFGMiner as a proxy instead of slush's. I've seen slush's have issues which couldn't be explained, but BFGMiner is always spot-on.

If possible, use a port other than 8332 to rule out port issues. I usually suggest folks use 8339 or something else easy to remember. Make sure the change is in blade setup, and the proxy knows to listen on the same port.

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: ccplz on November 20, 2013, 11:35:02 AM

Quote from: xyzzy099 on November 20, 2013, 11:21:37 AM

Quote from: ccplz on November 20, 2013, 11:14:48 AM

Well, everything I can see looks right. As long as your user/pass field is 'user:passe,user:pass', the only other thing I can think of is a firewall issue that is blocking port 8332 between your blade and the proxy machine. If that's not it, I don't have any other suggestions.

Well,thanks for trying.
Oh and one last question.
Could it have anything to do with my OS?(Win8 x64)

Well, I guess anything is possible, but I am using Win 7 x64 with no problems. I have not heard of any problems specific to Win 8.

One more experiment you might want to try, just to rule out proxy misconfiguration... If you kill the proxy and start bitcoin-qt, the blade should be able to connect directly to bitcoin-qt to solo mine. If that doesn't work, you definitely have a network problem of some sort. If it does work, you have a proxy problem.

ccplz

full member

Activity: 258

Merit: 116

Quote from: xyzzy099 on November 20, 2013, 11:21:37 AM

Quote from: ccplz on November 20, 2013, 11:14:48 AM

Well, everything I can see looks right. As long as your user/pass field is 'user:passe,user:pass', the only other thing I can think of is a firewall issue that is blocking port 8332 between your blade and the proxy machine. If that's not it, I don't have any other suggestions.

Well,thanks for trying.
Oh and one last question.
Could it have anything to do with my OS?(Win8 x64)

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: ccplz on November 20, 2013, 11:14:48 AM

Well, everything I can see looks right. As long as your user/pass field is 'user:passe,user:pass', the only other thing I can think of is a firewall issue that is blocking port 8332 between your blade and the proxy machine. If that's not it, I don't have any other suggestions.

ccplz

full member

Activity: 258

Merit: 116

I'm banging my head against the wall,so I may have blanked some unnecessary parts.(6 hours of staring at the configuration screen will do that to you)

xyzzy099

legendary

Activity: 1065

Merit: 1077

Can you post a screen shot of your blade config window (with your username/pw blanked)?

I have never used that proxy, but it looks like it is connected to the pool and just waiting on a miner to connect.

ccplz

full member

Activity: 258

Merit: 116

Quote from: xyzzy099 on November 20, 2013, 10:58:11 AM

Quote from: ccplz on November 20, 2013, 10:51:04 AM

Quote from: xyzzy099 on November 20, 2013, 10:46:25 AM

Quote from: ccplz on November 20, 2013, 10:32:49 AM

Nope,no other programs running.

Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have 'http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header.

That edit box should just contain '192.168.1.x, 192.168.1.x'.

Negative,no HTTP in the address box.

Something is trying to talk HTTP to the proxy:

See the protocol error? It is failing to decode an HTTP header. If you don't have any edit boxes in your configuration window with an 'http://' prefix, then I don't get it...

That picture was from the previous error when I was trying to use port 3333.
Now that I'm using port 8332,it's stuck at

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: ccplz on November 20, 2013, 10:51:04 AM

Quote from: xyzzy099 on November 20, 2013, 10:46:25 AM

Quote from: ccplz on November 20, 2013, 10:32:49 AM

Nope,no other programs running.

Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have 'http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header.

That edit box should just contain '192.168.1.x, 192.168.1.x'.

Negative,no HTTP in the address box.

Something is trying to talk HTTP to the proxy:

See the protocol error? It is failing to decode an HTTP header. If you don't have any edit boxes in your configuration window with an 'http://' prefix, then I don't get it...

ccplz

full member

Activity: 258

Merit: 116

Quote from: xyzzy099 on November 20, 2013, 10:46:25 AM

Quote from: ccplz on November 20, 2013, 10:32:49 AM

Nope,no other programs running.

Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have 'http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header.

That edit box should just contain '192.168.1.x, 192.168.1.x'.

Negative,no HTTP in the address box.

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: ccplz on November 20, 2013, 10:32:49 AM

Nope,no other programs running.

Just a shot in the dark here... In the edit box where you enter the server address, you don't happen to have 'http://192.168.1.X' do you? I notice in the screenshot you posted that the proxy is failing to understand an HTTP header.

That edit box should just contain '192.168.1.x, 192.168.1.x'.

ccplz

full member

Activity: 258

Merit: 116

Quote from: xyzzy099 on November 20, 2013, 10:28:36 AM

Quote from: ccplz on November 20, 2013, 10:14:29 AM

Quote from: CarneMuerta on November 20, 2013, 10:07:16 AM

Quote from: ccplz on November 20, 2013, 09:39:04 AM

Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.

What I did was:

1)Open mining proxy(on default settings)
2)Set both the server addresses to my IP(as seen in cmd using /ipconfig)
3)Set the ports to 3333,8332
4)Set the account info to username_workername:password,username_workername:password

Now I'm getting two different results.

On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0
On port 8332 nothing happens.

Would appreciate any help,thanks in advance.

3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps

Thanks for the quick reply.

Tried that too,still doesn't work Sad

Current Server: 192.168.1.X:8332

No hashes Sad

Do you also have a Bitcoin-QT or bitcoind running on your machine? If so, it will use port 8332 by default and you will be conflicting. I use BFGMiner as the proxy on port 8330. I have never used the slush proxy, but I imagine you can tell it to use a different port than 8332 for incoming connections.

Nope,no other programs running.

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: ccplz on November 20, 2013, 10:14:29 AM

Quote from: CarneMuerta on November 20, 2013, 10:07:16 AM

Quote from: ccplz on November 20, 2013, 09:39:04 AM

Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.

What I did was:

1)Open mining proxy(on default settings)
2)Set both the server addresses to my IP(as seen in cmd using /ipconfig)
3)Set the ports to 3333,8332
4)Set the account info to username_workername:password,username_workername:password

Now I'm getting two different results.

On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0
On port 8332 nothing happens.

Would appreciate any help,thanks in advance.

3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps

Thanks for the quick reply.

Tried that too,still doesn't work Sad

Current Server: 192.168.1.X:8332

No hashes Sad

Do you also have a Bitcoin-QT or bitcoind running on your machine? If so, it will use port 8332 by default and you will be conflicting. I use BFGMiner as the proxy on port 8330. I have never used the slush proxy, but I imagine you can tell it to use a different port than 8332 for incoming connections.

ccplz

full member

Activity: 258

Merit: 116

Quote from: CarneMuerta on November 20, 2013, 10:07:16 AM

Quote from: ccplz on November 20, 2013, 09:39:04 AM

Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.

What I did was:

1)Open mining proxy(on default settings)
2)Set both the server addresses to my IP(as seen in cmd using /ipconfig)
3)Set the ports to 3333,8332
4)Set the account info to username_workername:password,username_workername:password

Now I'm getting two different results.

On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0
On port 8332 nothing happens.

Would appreciate any help,thanks in advance.

3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps

Thanks for the quick reply.

Tried that too,still doesn't work Sad

Current Server: 192.168.1.X:8332

No hashes Sad

CarneMuerta

newbie

Activity: 17

Merit: 0

Quote from: ccplz on November 20, 2013, 09:39:04 AM

Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.

What I did was:

1)Open mining proxy(on default settings)
2)Set both the server addresses to my IP(as seen in cmd using /ipconfig)
3)Set the ports to 3333,8332
4)Set the account info to username_workername:password,username_workername:password

Now I'm getting two different results.

On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0
On port 8332 nothing happens.

Would appreciate any help,thanks in advance.

3333 is a sratum port, 8332 is getwork port, blades use getwork so if you use 8332 twice for your ports you should be good... Hope that helps

ccplz

full member

Activity: 258

Merit: 116

Just received my blade,sailed smoothly through the hardware stuff,however I'm stuck at the configuration page.

What I did was:

1)Open mining proxy(on default settings)
2)Set both the server addresses to my IP(as seen in cmd using /ipconfig)
3)Set the ports to 3333,8332
4)Set the account info to username_workername:password,username_workername:password

Now I'm getting two different results.

On port 3333,mining proxy goes batshit crazy,but the hashrate is still stuck at 0
On port 8332 nothing happens.

Would appreciate any help,thanks in advance.

P.S. My ISP uses dynamic IPs,is there any way to setup the configuration without having to change the server addresses all the time?

EDIT:This is the batshit crazy part.

Ally_Rob

newbie

Activity: 52

Merit: 0

Just done! I was trolling, found another post which mentioned the router being x.x.1.254 default..

Its working, shit i killed like 3 hours working on this lol Roll Eyes

now just got to get the proxy and off to the races.

thanks again

vesperwillow

hero member

Activity: 616

Merit: 500

Quote from: Ally_Rob on November 20, 2013, 12:08:37 AM

Hey...
How did you run power to the board?
I took a 4-pin-molex which was to power 2 sata. I snipped stripped and did as you see. 4 blacks; 2 yellows.
Cant get the access via the webserver .
The led flashes once in a blue moon.

my router is setup, to end its dhcp server at 254, i just ungraded it to include 254. I still cant get access to the webserver. my internal ip is 192.168.2.xxx
ive tried new ethernet cables, still cant wrapped my head around it.. thanks
rob
this is my power

my board

It's your IP setting probably, default blade address is 192.168.1.254, but you're on 192.168.2.x

As long as your router is a switching router, just change on of your computer's IPs to 192.168.1.x (x = unused IP, say 20 or something), and then try connecting to the blade at http://192.168.1.254:8000

Ally_Rob

newbie

Activity: 52

Merit: 0

Hey...
How did you run power to the board?
I took a 4-pin-molex which was to power 2 sata. I snipped stripped and did as you see. 4 blacks; 2 yellows.
Cant get the access via the webserver .
The led flashes once in a blue moon.

my router is setup, to end its dhcp server at 254, i just ungraded it to include 254. I still cant get access to the webserver. my internal ip is 192.168.2.xxx
ive tried new ethernet cables, still cant wrapped my head around it.. thanks
rob
this is my power

my board

Topic: [Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 22. (Read 580761 times)