New stratum/getwork proxy with Web-based GUI and pools management

[Delivereath]

You're right. It's working now. Thanks.

How do I add pools and configure priority for each ?

[Gamer67]

Excellent.

Always good to have more connection options.

[bestsponsor]

Is this proxy can work with betarigs.com ?

[Pfool]

Is this proxy can work with betarigs.com ?

It works between pools and betarigs...never tested between betarigs and miners...but it should work...

[Pfool]

You're right. It's working now. Thanks.

How do I add pools and configure priority for each ?

you can add several pools on the command line (check the usage with "java -jar --usage"). Priority is the order of pools on command line. The first pool has the highest priority (priority 0). When the proxy is already running, you can change the priority through the API. (Check the first page of the github project).

If you compile the latest version of the proxy, you can add/remove pools through the API too. At the moment, I haven't yet developped a front-end for this API so you will have to use this kind of plugins to call the API methods:
https://addons.mozilla.org/fr/firefox/addon/poster/

[Delivereath]

Ok, I tried it once more but I don't really understand I a user and a password are needed for each pool. Can't I use the workers already configured in my rigs ? I still want to have individual workers for each rig.

It would be nice to be have to override the workers with a single user/password or to keep the workers/password already provided by the rig.

[Pfool]

Ok, I tried it once more but I don't really understand I a user and a password are needed for each pool. Can't I use the workers already configured in my rigs ? I still want to have individual workers for each rig.

It would be nice to be have to override the workers with a single user/password or to keep the workers/password already provided by the rig.

Yes, you have to provide a username and password for each pool. You loose the per worker monitoring of your pool but you can use the worker monitoring of the proxy. It is done like that since the aim of the proxy is to centralize pool configuration so you just have to put the proxy address in your miner (and no failover). Since the proxy manages pools, you configure the usernames and passwords in the proxy.

But you are right, it could be cool to keep the worker monitoring on the pool. I think I will add more options to configure pools like:
--pool-append-worker-names true/false: to append the worker name to the username configured for the pool
--pool-worker-name-separator string: the separator to use to append the worker name

For example, java -jar -h pool1.com pool2.com -u Stratehm Pfool -p x x --pool-append-worker-names true false --pool-worker-name-separator _

will use Stratehm_workerName to submit shares on pool1 and will just use Pfool to submit shares on the failover pool2.

Is it ok for you ?

[Delivereath]

Yes, that would be really nice.

Will this also allow to have a different worker difficulty for each rig ? I've different rig sizes so having the same difficulty for all rigs is not the most efficient strategy.

[Pfool]

For the difficulty, I think it will not be possible due to the difficulty management in the stratum protocol. (Connection based and not worker based).

[Delivereath]

Then, if really needed, I could run one proxy instance for each rig and have independent difficulty per worker.

[Delivereath]

Are you planning to add different pool management strategies like failover, loadbalance ?

[Pfool]

Failover is already available.

For loadbalancing: maybe, one day. It is not the priority. But, feel free to fork the project and to add it...

[leicas]

I have some trouble understanding the way the failover is working.
I have multiple workers set on my stratum, and they don't always switch on my pool with priority 0.
For example, on the following picture, only one worker is on the favorite pool (which is online from some time already).
http://s21.postimg.org/dfox0eehz/Capture.png

Is there a way to fix this ?

[Pfool]

All workers should be on the same pool everytime. All workers should switch to pool with priority 1 when pool with priority 0 is down. If you have some workers staying on the lower priority pool when higher priority one is UP, it may be a bug. Could you please send me the log file of the proxy ?

(0 is the highest priority)

[Pfool]

0.2.0 version released with following improvements and fixes. The upgrade is highly recommended:

-Fix a bug when using failover pools. Some connections where left on lower priority pools when higher ones came back online.
-Return a JSON status on some API methods
-Update API
-Fix a log display issue when retry connection on pool
-Add pool/add and pool/remove API
-Add user management API methods (Kick, ban, unban, list banned)
-Add --pool-append-worker-names, --pool-worker-name-separator and --pool-use-worker-password options to allow some pools to see the workers through the proxy.
-Improve compatibility with some pools with which do not fully respect the stratum protocol.

https://github.com/Stratehm/stratum-proxy/releases

[bestsponsor]

Is this proxy can work with betarigs.com ?

It works between pools and betarigs...never tested between betarigs and miners...but it should work...

between betarigs and miners
betagigs uses API sgminer for monitoring rigs. You can integrate these API methods?

[Pfool]

Is this proxy can work with betarigs.com ?

It works between pools and betarigs...never tested between betarigs and miners...but it should work...

between betarigs and miners
betagigs uses API sgminer for monitoring rigs. You can integrate these API methods?

Which API methods are needed ?

[bestsponsor]

I`m not programmer.
Please ask on https://www.betarigs.com

[Pfool]

I have just tested the proxy between my miners and betarigs and it works fine as is. Betarigs is just a pool like others and it does not use sgminer API (I have seen anything about that on their website). Where have you seen that ?

[bestsponsor]

but ccminer with betarigs not working