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

[crysx]

I'm trying to point my S9's at NiceHash for SHA256 mining. Unfortunately I'm seeing a large percentage of rejects (around 30%). Most of the rejects seem to be duplicate shares:

Code:

2016-11-07 08:26:41,291 INFO     [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s92@192.168.80.102 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]
2016-11-07 08:26:45,510 INFO     [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s91@192.168.80.101 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]

I tried to work around this by enabling and disabling extranonce and by setting a reasonable minimum difficulty. I also tried both syntaxes for specifying the extranonce to NiceHash (i.e. adding "#xnsub" and "/#xnsub" to the URL).

I've also tried a single worker behind the proxy, in case the issue is related to multiple workers.

Nothing I change seems to help.

When I point the S9s directly at NiceHash, they work fine with almost no rejects. But of course that defeats the purpose of a proxy.

Any recommendations for getting this proxy to work with NiceHash?

i have been using this proxy for a long time now with the nicehash system ...

i have not had any real issues - except for the idle disconnection issues which has been fixed ...

though the proxy works - it has never been tested with any asic miner ...

what is the s9 - scrypt? ... sha256d? ...

which port are you mining on? ... how long are you mining for? ... are these errors immediate or after sometime? ...

these are some of things i think will answer the issues ... at least i hope ...

#crysx

[scyth33]

I'm trying to point my S9's at NiceHash for SHA256 mining. Unfortunately I'm seeing a large percentage of rejects (around 30%). Most of the rejects seem to be duplicate shares:

Code:

2016-11-07 08:26:41,291 INFO     [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s92@192.168.80.102 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]
2016-11-07 08:26:45,510 INFO     [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s91@192.168.80.101 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]

I tried to work around this by enabling and disabling extranonce and by setting a reasonable minimum difficulty. I also tried both syntaxes for specifying the extranonce to NiceHash (i.e. adding "#xnsub" and "/#xnsub" to the URL).

I've also tried a single worker behind the proxy, in case the issue is related to multiple workers.

Nothing I change seems to help.

When I point the S9s directly at NiceHash, they work fine with almost no rejects. But of course that defeats the purpose of a proxy.

Any recommendations for getting this proxy to work with NiceHash?

i have been using this proxy for a long time now with the nicehash system ...

i have not had any real issues - except for the idle disconnection issues which has been fixed ...

though the proxy works - it has never been tested with any asic miner ...

what is the s9 - scrypt? ... sha256d? ...

which port are you mining on? ... how long are you mining for? ... are these errors immediate or after sometime? ...

these are some of things i think will answer the issues ... at least i hope ...

#crysx

was there a fix for the idle disconnection issue?

[crysx]

I'm trying to point my S9's at NiceHash for SHA256 mining. Unfortunately I'm seeing a large percentage of rejects (around 30%). Most of the rejects seem to be duplicate shares:

Code:

2016-11-07 08:26:41,291 INFO     [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s92@192.168.80.102 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]
2016-11-07 08:26:45,510 INFO     [Pool-NiceHash-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - REJECTED share (diff: 32768.0) from s91@192.168.80.101 on NiceHash. Booo !!!!. Error: JsonRpcError [code_=22, message=Duplicate share., traceback=null]

I tried to work around this by enabling and disabling extranonce and by setting a reasonable minimum difficulty. I also tried both syntaxes for specifying the extranonce to NiceHash (i.e. adding "#xnsub" and "/#xnsub" to the URL).

I've also tried a single worker behind the proxy, in case the issue is related to multiple workers.

Nothing I change seems to help.

When I point the S9s directly at NiceHash, they work fine with almost no rejects. But of course that defeats the purpose of a proxy.

Any recommendations for getting this proxy to work with NiceHash?

i have been using this proxy for a long time now with the nicehash system ...

i have not had any real issues - except for the idle disconnection issues which has been fixed ...

though the proxy works - it has never been tested with any asic miner ...

what is the s9 - scrypt? ... sha256d? ...

which port are you mining on? ... how long are you mining for? ... are these errors immediate or after sometime? ...

these are some of things i think will answer the issues ... at least i hope ...

#crysx

was there a fix for the idle disconnection issue?

yup ...

it turned out that it was not from the stratum proxy at all - it was the nicehash stratums banning the ip for 10mins at a time ( or longer if you stay connected ) for having no miner through the open connection ...

only way you can get around that is to connect and disconnect the miner when idle ...

or - get whitelisted on the nicehash list ... the will whitelist your ip - only if you have a good reason to have the connections active there all the time ...

otherwise the stratum just puts you on the ban list ...

#crysx

[aarons6]

how does the weights work?
i tried to set to weightedroundrobin..
i have the weighted time to 60, im guessing thats minutes?

then i set up 2 pools, with priority 0? and i put them 30/30 for weights? i want to mine on them each the same.

but nothing happens..

[crysx]

how does the weights work?
i tried to set to weightedroundrobin..
i have the weighted time to 60, im guessing thats minutes?

then i set up 2 pools, with priority 0? and i put them 30/30 for weights? i want to mine on them each the same.

but nothing happens..

if your weighted time in total is 60 - then you can look at it as being 60mins ...

if the pools roundrobin time is setup as 30 - then that will mean that each pool will connect ( in turn from first to second and back - unless a stratum proxy restart / reset is done ) every 30mins ...

if it doesnt - then there is a setup issue - a connection ( to the pools ) issue - or a typo / setup problem in the conf ...

an easy way of informing us - is showing us ... what does your setup look like ( the conf ) ...

#crysx

[aarons6]

how does the weights work?
i tried to set to weightedroundrobin..
i have the weighted time to 60, im guessing thats minutes?

then i set up 2 pools, with priority 0? and i put them 30/30 for weights? i want to mine on them each the same.

but nothing happens..

if your weighted time in total is 60 - then you can look at it as being 60mins ...

if the pools roundrobin time is setup as 30 - then that will mean that each pool will connect ( in turn from first to second and back - unless a stratum proxy restart / reset is done ) every 30mins ...

if it doesnt - then there is a setup issue - a connection ( to the pools ) issue - or a typo / setup problem in the conf ...

an easy way of informing us - is showing us ... what does your setup look like ( the conf ) ...

#crysx

i am making the changes in the gui, the conf is the default one..

i think i figured it out, and now i have the pools switching..
but one more question.. if i have it setup this way and one pool goes down, does it just mine on the working pool?

[crysx]

how does the weights work?
i tried to set to weightedroundrobin..
i have the weighted time to 60, im guessing thats minutes?

then i set up 2 pools, with priority 0? and i put them 30/30 for weights? i want to mine on them each the same.

but nothing happens..

if your weighted time in total is 60 - then you can look at it as being 60mins ...

if the pools roundrobin time is setup as 30 - then that will mean that each pool will connect ( in turn from first to second and back - unless a stratum proxy restart / reset is done ) every 30mins ...

if it doesnt - then there is a setup issue - a connection ( to the pools ) issue - or a typo / setup problem in the conf ...

an easy way of informing us - is showing us ... what does your setup look like ( the conf ) ...

#crysx

i am making the changes in the gui, the conf is the default one..

i think i figured it out, and now i have the pools switching..
but one more question.. if i have it setup this way and one pool goes down, does it just mine on the working pool?

no it doesnt mine on just that pool ...

it will continue to switch ... but the mechanics of the switching is the same ...

it will continue to try and connect to the pool - and if it cant - will failover to the switched pool anyway ...

so in effect - it will just do what it does best ... connect to the next working pool in the list ...

#crysx

[manotroll]

As I start it has no EXE file

[crysx]

As I start it has no EXE file

its java based ...

so run it from a java container ...

if in windows ( judging by the 'exe' you are expecting - you are ) and you have the latest java installed - just double click it ( i think - i dont use windows ) ...

#crysx

[manotroll]

As I start it has no EXE file

its java based ...

so run it from a java container ...

if in windows ( judging by the 'exe' you are expecting - you are ) and you have the latest java installed - just double click it ( i think - i dont use windows ) ...

#crysx

Internal Server Error
Jar file was not found

     1: org.glassfish.grizzly.http.server.CLStaticHttpHandler.getJarFile(CLStaticHttpHandler.java:349)
     2: org.glassfish.grizzly.http.server.CLStaticHttpHandler.handle(CLStaticHttpHandler.java:288)
     3: strat.mining.stratum.proxy.grizzly.CLStaticHttpHandlerWithIndexSupport.handle(CLStaticHttpHandlerWithIndexSupport.java:60)
     4: org.glassfish.grizzly.http.server.StaticHttpHandlerBase.service(StaticHttpHandlerBase.java:188)
     5: org.glassfish.grizzly.http.server.HttpHandler$1.run(HttpHandler.java:219)
     6: org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:565)
     7: org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:545)
     8: java.lang.Thread.run(Unknown Source)

Please see the log for more detail.
Grizzly 2.3.16
??
I use the latest version of java

[toptek]

nice hash has a guide for how to use this with windows , i have used it on a windows PC using  on other pools not just nice hash using there guide.

https://www.nicehash.com/index.jsp?p=asic

I use it on PI type PC's not just with RPI either, i wish it worked with ZEC and ETH mining that would be great but it looks like the DEV Has no plans to go beyond whats done now and others have offered to pay to have more done i guess he lost interest or doesn't deal with btc any more mining or may be even no time even if the price is right.

and WeightedRoundRobin works great once you know or understand how to use it, I wish more was done with this or i had the skill to add more, i would and ask for nothing in return but that's allwys the case those want to, can't and those that can, won't .

thanks top

[crysx]

hi all ...

its been a while since ive changed any of the config file - and the simplest of things ive actually forgotten how to do ...

how do i change the config file to accept the workers username:password as the credentials for the pool that the stratum proxy is pointing to ...

ie - make is a passive stratum proxy ... NOT appending the worker username:password ...

#crysx

[evilcode1]

Anyone can help me guys  ?

im mining XMR
im using windows  , let say that the windows computer that my client conected to it is 10.0.0.1
and the port is 7070
and i want to mine to xm-eu.dwrfpool.com with this port 8050

how i configure this proxy to do this job ?

[chrysophylax]

Anyone can help me guys  ?

im mining XMR
im using windows  , let say that the windows computer that my client conected to it is 10.0.0.1
and the port is 7070
and i want to mine to xm-eu.dwrfpool.com with this port 8050

how i configure this proxy to do this job ?

from memory ...

the stratum proxy does not support cryptonight / cryptonite algo ...

i could be wrong - as we have never mined these algos through this proxy ...

if anyone can verify? ...

#crysx

[evilcode1]

i think it work , i want the full comand line to test with options i post in the prev reply , or is there any sugest ?

[jukico]

Hello,

I am starting the proxy and L3+ with setting as captures.
But the miner can't connect to stratum-proxy.
Please help me.

(Stratum-proxy dashboard can connect, My server ip: 192.168.1.33)

https://ibb.co/gC9KS5
https://ibb.co/nOJqZk

[MonkeyBusiness]

Hi
I am receiving error when I am trying to connect to Nicehash Scrypt server.
"The worker connection does not support setExtranonce notification" . What can I do with this?
http://joxi.ru/KAxXk6OH4ZgEkA
Also, I have another problem with connecting to Equihash and DaggerHashimoto Nicehash servers.
http://joxi.ru/EA41YDMtDoBkqr

Please, help me solve this problems.

[MonkeyBusiness]

Switching off "enableExtranonceSubscribe" dont work.

[tedyx]

-Support Extranonce notification to avoid disconnection when switching pool.

Does this actually work?

I've tried it with several pools, some of them keep getting disconnected (assuming the pool don't support it) but even when proxy is connected and subscribed to 2 pools at the same time, when I change pools it says:
Close connection x.x.x.x since the on-the-fly extranonce change is not supported.

Why is on-the-fly change not supported? Does it mean that pool don't support it, or misconfiguration with proxy?


Thanks!

[gr33k]

Is this under development still? Love this thing and can't seem to find any alternatives

The Settings tab doesn't work, and the proxy seems to struggle with multipools (or perhaps switching coins on the fly by editing existing pool configs via the web gui).

Some other minor things like the graph glitches on the pool (Main graph) sometimes, but reallly like it

Pfool you still working on this ?

Thank you for the current work you've already put in as well