Looking at your settings and your proxy - you are having your proxy pass through the user names in your cubes rather than defining it proxy-wide, via the "-cu" and "-cp" switches. You can do that of course, but then you have to be sure that the usernames in your cube setups will work on the pool directly.
I don't know how to use the -cu or -cp switch. Can you give me an example? Thanks!
You got it right with your guess. Here's what I use when I want the proxy to send a user/pass combination for all devices that are being proxied versus what's in the cube/blade config:
Code:
mining_proxy -q -rt -gp 8330 -o server.address.com -p serverport -cu worker.name -cp worker.pass
(I don't use the .exe since I linux but the structure's the same)
The result should be that all devices using the proxy show up under whatever worker name you set up in the mining proxy with "-cu" This of course can be problematic for trouble-shooting, but if you switch coins a lot like I do, it's easiest. If not, it's best to do it in the cube/blade configuration. I have my cubes/blades set up with miners for ghash.io and only use the -cu/-cp switches when I go to other pools where my worker names don't match.
