i have also another error " incorrect size of extranonce2"
Do you see this error in the proxy logs or on your miner ? If in the proxy logs, could you send me the log file ?
Topic: New stratum/getwork proxy with Web-based GUI and pools management - page 19. (Read 120883 times)
November 06, 2014, 11:12:22 AM
Do you see this error in the proxy logs or on your miner ? If in the proxy logs, could you send me the log file ?
November 06, 2014, 11:10:26 AM
i have also another error " incorrect size of extranonce2"
ok found it "WARN: CGMiner 3.7.2 is not compatible with Stratum proxies (this one and others) due to a bug on the extranonce2 size management. You can use sgminer instead or some forks of cgminer which include the fix. If using cgminer 3.7.2, you will have 100% rejects (generally with message Share above target).
This bug has been fixed in later version of cgminer, but it no more supports scrypt mining.
EDIT: You can use the Getwork protocol instead of stratum with CGminer 3.7.2."
my rented rig are probably using cgminer 3.7.2, this is why i'm getting all those error
ok found it "WARN: CGMiner 3.7.2 is not compatible with Stratum proxies (this one and others) due to a bug on the extranonce2 size management. You can use sgminer instead or some forks of cgminer which include the fix. If using cgminer 3.7.2, you will have 100% rejects (generally with message Share above target).
This bug has been fixed in later version of cgminer, but it no more supports scrypt mining.
EDIT: You can use the Getwork protocol instead of stratum with CGminer 3.7.2."
my rented rig are probably using cgminer 3.7.2, this is why i'm getting all those error
November 06, 2014, 11:08:11 AM
unfortunately is scrypt 
Sorry, no solution at the moment.
You can open a bug on github to remember me the feature request. (but I really do not know when I will be able to add it).
November 06, 2014, 10:34:45 AM
unfortunately is scrypt
November 06, 2014, 10:15:25 AM
"no subscribe request recieved from..."
Where do you see this message ? What is your configuration ?
all ok now
another question, it's possible to set share diff?
because the miner pointed to this send low share diff which are then rejected by the pool connected to this stratum
If you mine on SHA-256 pool and your miner is connected to the proxy with the Getwork protocol you can use the parameter:
"validateSha26GetworkShares": true
This parameter will compute the real difficulty of the shares submitted by the miner before submitting them to the pool. If the difficulty of a share is too low, the share is discarded. This option only works for Getwork and SHA-256 (this it was added to supply some old miners behavior) and will increase the proxy CPU consumption.
November 06, 2014, 09:21:01 AM
"no subscribe request recieved from..."
Where do you see this message ? What is your configuration ?
all ok now
another question, it's possible to set share diff?
because the miner pointed to this send low share diff which are then rejected by the pool connected to this stratum
November 05, 2014, 04:56:45 PM
i can't connect my miners 
it says pool is dead using dragon miner
set at pool #1 : stratum+tcp://192.168.1.3:3333
tried http://192.168.1.3:8332
tried http://127.0.0.1:3333
worker name is x and password is x since worker and password is already set in config file or via web interface but also no joy if i leave worker + password in miner.
no joy at all but i manage to launch stratum with a very basic config file and i can view it via web using 192.168.1.3:8888 or 127.0.0.1:8888.
any help is appreciated.
it says pool is dead using dragon minerset at pool #1 : stratum+tcp://192.168.1.3:3333
tried http://192.168.1.3:8332
tried http://127.0.0.1:3333
worker name is x and password is x since worker and password is already set in config file or via web interface but also no joy if i leave worker + password in miner.
no joy at all but i manage to launch stratum with a very basic config file and i can view it via web using 192.168.1.3:8888 or 127.0.0.1:8888.
any help is appreciated.
I will need your configuration file and the proxy log file.
figured it all out running couple of instances, many thx for the sweet program !
+1 , 2 thumbs up for contributing to the community !
November 05, 2014, 11:28:25 AM
"no subscribe request recieved from..."
Where do you see this message ? What is your configuration ?
November 05, 2014, 11:26:56 AM
i can't connect my miners it says pool is dead using dragon miner
set at pool #1 : stratum+tcp://192.168.1.3:3333
tried http://192.168.1.3:8332
tried http://127.0.0.1:3333
worker name is x and password is x since worker and password is already set in config file or via web interface but also no joy if i leave worker + password in miner.
no joy at all but i manage to launch stratum with a very basic config file and i can view it via web using 192.168.1.3:8888 or 127.0.0.1:8888.
any help is appreciated.
it says pool is dead using dragon minerset at pool #1 : stratum+tcp://192.168.1.3:3333
tried http://192.168.1.3:8332
tried http://127.0.0.1:3333
worker name is x and password is x since worker and password is already set in config file or via web interface but also no joy if i leave worker + password in miner.
no joy at all but i manage to launch stratum with a very basic config file and i can view it via web using 192.168.1.3:8888 or 127.0.0.1:8888.
any help is appreciated.
I will need your configuration file and the proxy log file.
November 05, 2014, 11:24:54 AM
November 04, 2014, 06:29:02 PM
"no subscribe request recieved from..."
i can't connect from my host to my VM, using this stratum proxy
i can't connect from my host to my VM, using this stratum proxy
October 30, 2014, 10:05:27 PM
Can someone please post a working config file for nicehash sha-256 config please, I would like to point several S3 Antminers to my box thats running this program and then point the box at nicehash.. Any help would be much appreciated.
This basic configuration file should work (just replace the "user" value with your BTC address) :
Code:
{
"pools" : [ {
"name" : "Nicehash SHA-256",
"host" : "stratum.nicehash.com:3334",
"user" : "19wv8FQKv3NkwTdzBCQn1AGsb9ghqBPWXi",
"password" : "d=2048",
"enableExtranonceSubscribe" : true,
} ]
}
This configuration file is the minimal configuration with default values for all other parameters.
If you want to use Stratum, just point your miner to stratum+tcp://proxyIp:3333. Else, to use Getwork, point your miner to http://proxyIp:8332. The username and password configured in your miner can be anything.
I did the exact same think but my miner won't start mining. Proxy launches successfully. Web interface is great. The ip of my lappy is 192.168.1.3 which is running the stratum proxy. I'm using dragon miner it shows pool (my ip address) dead. I've tried various add such as with and without stratum, port 3333,8332 etc as described. Running on win8.
TIA for your help.
October 30, 2014, 04:50:17 PM
i can't connect my miners it says pool is dead using dragon miner
set at pool #1 : stratum+tcp://192.168.1.3:3333
tried http://192.168.1.3:8332
tried http://127.0.0.1:3333
worker name is x and password is x since worker and password is already set in config file or via web interface but also no joy if i leave worker + password in miner.
no joy at all but i manage to launch stratum with a very basic config file and i can view it via web using 192.168.1.3:8888 or 127.0.0.1:8888.
any help is appreciated.
it says pool is dead using dragon minerset at pool #1 : stratum+tcp://192.168.1.3:3333
tried http://192.168.1.3:8332
tried http://127.0.0.1:3333
worker name is x and password is x since worker and password is already set in config file or via web interface but also no joy if i leave worker + password in miner.
no joy at all but i manage to launch stratum with a very basic config file and i can view it via web using 192.168.1.3:8888 or 127.0.0.1:8888.
any help is appreciated.
October 27, 2014, 05:58:18 PM
wow, much to read & learn... following thx to op for contributing his time & help to the community ! +1
October 27, 2014, 08:03:24 AM
Pool A <---+
(Active) |
|
|
Pool B <---+ StratumProxy <-------------+ Rig1
(Active) |
|
|
Pool C <---+
(Active)
Hello! It is possible to have this config? Eventually with more Rig ... ?
October 20, 2014, 04:02:29 PM
#notls seems to not sort any effect, it can't find the pool.
bfgminer version is BFGminer_4.3.1_ZEUS_Windows and bfgminer 4.9 for reference .
bfgminer version is BFGminer_4.3.1_ZEUS_Windows and bfgminer 4.9 for reference .
October 20, 2014, 07:19:38 AM
i have error connecting with bfgminer for zeus( https://litecointalk.org/index.php?topic=20477.0 ):
with cgminer no problem, just to check if there is something wrong
Code:
2014-10-19 22:18:49,318 ERROR [/2.234.124.164:56220-Thread]:strat.mining.stratum.proxy.network.StratumConnection - JSON-RPC Parsing error with line: {"id": "auth", "method": "mining.authorize", "params": ["user", "pass"]}
2014-10-19 22:19:22,616 ERROR [/2.234.124.164:50062-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /2.234.124.164:50062. Failed to parse line ÉÅTD Êö¹�!0‹[ónSèsRÕ G)]J�éWÖ¾}¥J\ÀÀ.
2014-10-19 22:19:22,617 ERROR [/2.234.124.164:50062-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /2.234.124.164:50062. Failed to parse line À.
2014-10-19 22:19:22,618 ERROR [/2.234.124.164:50062-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /2.234.124.164:50062. Failed to parse line 42 .
2014-10-19 22:19:22,619 ERROR [/2.234.124.164:50062-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /2.234.124.164:50062. Failed to parse line .
bfgminer firstly tries to open a SSL connection before using a RAW TCP connection. I have tried to fix this kind of error, but it seems it is not fixed.
Try to add this parameter at the end of the URL in bfgminer: #notls
October 19, 2014, 03:23:14 PM
i have error connecting with bfgminer for zeus( https://litecointalk.org/index.php?topic=20477.0 ):
with cgminer no problem, just to check if there is something wrong
Code:
2014-10-19 22:18:49,318 ERROR [/2.234.124.164:56220-Thread]:strat.mining.stratum.proxy.network.StratumConnection - JSON-RPC Parsing error with line: {"id": "auth", "method": "mining.authorize", "params": ["user", "pass"]}
2014-10-19 22:19:22,616 ERROR [/2.234.124.164:50062-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /2.234.124.164:50062. Failed to parse line ÉÅTD Êö¹�!0‹[ónSèsRÕ G)]J�éWÖ¾}¥J\ÀÀ.
2014-10-19 22:19:22,617 ERROR [/2.234.124.164:50062-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /2.234.124.164:50062. Failed to parse line À.
2014-10-19 22:19:22,618 ERROR [/2.234.124.164:50062-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /2.234.124.164:50062. Failed to parse line 42 .
2014-10-19 22:19:22,619 ERROR [/2.234.124.164:50062-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection /2.234.124.164:50062. Failed to parse line .
October 15, 2014, 08:11:36 AM
Is it possible to set the acceptable difficulty limit in the proxy?
No, there is no such feature.
October 15, 2014, 06:32:51 AM
Is it possible to set the acceptable difficulty limit in the proxy?
Jump to: