Topic: New stratum/getwork proxy with Web-based GUI and pools management - page 2. (Read 120837 times)

Algos like ETH will not work.

ANY Algo that has changed the headers/structure of it's mining mechanism like ETH will not work with this proxy, due to the proxy being a passive method of transferring the data through it. This includes mining (and especially) mining headers, which Algos like coins like ETH (EtHash and EquiHash) have messed with good and proper.

The proxies you are looking for require specialized code to cater for these Algos, and can be found if looking for them.

#crysx

There's no list of supported algos, but I gave it a shot with ethereum, since its an old coin, should've worked. But it doesn't. -2 days on my side 

Should I create BAT file to run stratum proxy ?
i m using cryptonight stratum proxy without any problem on Windows.
But i also need stratum proxy for x13 algo.

I have managed to get it working on slushpool, without any extra settings. I have enabled extranonce, I'm not sure if it's required for slush...
My question is, did any of you notice any negative impact on performance while using stratehm?

Hello,

I cant use cpuminer with the proxy :
on my local computer :
./cpuminer -a x11 -o stratum+tcp://x11.eu.nicehash.com:3336 -u 3JiLakn3G9mHWjnC5Mr65MnXrXcTX4Hue9 -x http://nicmar.fr:3333

my configuration file on the server :
{"pools" : [{"host" : "x11.eu.nicehash.com:3336","user" : "3JiLakn3G9mHWjnC5Mr65MnXrXcTX4Hue9"}]}

the error logs :

New connection on /0.0.0.0:3333 from /176.137.53.155:38496.
2018-01-07 08:44:47,125 ERROR [176.137.53.155-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Parsing error on worker connection 176.137.53.155. Failed to parse line CONNECT x11.eu.nicehash.com:3336 HTTP/1.1.
com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'CONNECT': was expecting ('true', 'false' or 'null')
at [Source: CONNECT x11.eu.nicehash.com:3336 HTTP/1.1; line: 1, column: 8]
at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1486)
at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:518)
at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._reportInvalidToken(ReaderBasedJsonParser.java:2300)
at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1459)
at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:683)
at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3600)
at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3545)
at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2576)
at strat.mining.stratum.proxy.network.StratumConnection.onLineRead(StratumConnection.java:225)
at strat.mining.stratum.proxy.network.StratumConnection.access$2(StratumConnection.java:221)
at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:163)

Where is the problem ?

Thanks

Nico

Also notice thet appending worker name on nicehash results is disconnects.

I noticed that changing pools vir the web gui is problematic. Is the api better? Or should one just kill the proxy and restart?

Ok so I moved the program to a lower level folder with no spaces and now it works

D:\temp\stratum-proxy-0.8.1

When running the proxy on a windows 7 systems with Jave 8 I can't seem to be able to connecto the web gui.

on 127.0.0.1:8888 i get this

Internal Server Error Jar file was not found



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

the config file is here https://github.com/Stratehm/stratum-proxy/files/1482574/Neoscrypt.conf.txt

Am I missing somehting?

Got this working today. I should say...WOW. Really cool way to be able to pool hop and centralize the submissions. I really like the GUI too.

Obviously having a local proxy is not needed, but as i stated, I want to centralize the management. I may want to mine different coins in the future and swap for BTC or whatever...Flexibility!

Having just got my first S9 2 days ago, i still have a lot to learn before the next 11 show up (5 S9 and 6 L3+). So, here is what I have, and please advise if something is wrong/OK...

I was working with the assumption that i needed to use getWork protocol locally in my LAN. I struggled with that and could not get the miner to connect. The only way i could get the S9 to connect to the local proxy was using the stratum tag and port as can be seen in the CURRENT working config. So, it seems I have a local stratum to remote stratum connection. Is this OK? Should I use getwork? If so, what are the matching configs need to make this work?

Here should be the relevant screenshots and code :

I want to use the API to switch between pools using this proxy.

Should I enable/disable a pool to have the proxy switch between pools or is changing the proxy priority sufficient?

2017-10-22 10:24:35,837 ERROR    [192.168.1.11-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - No pool available for the connection 192.168.1.11. Sending error and close the connection.
2017-10-22 10:24:35,850 INFO     [192.168.1.11-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.168.1.11 closed. 0 connections active on pool None. Cause: Connection closed.
2017-10-22 10:24:35,960 INFO     [TimerExecutorThread-527]:strat.mining.stratum.proxy.pool.Pool$3 - Trying reconnect of pool ReconnectTask-Nicehash LTC...
2017-10-22 10:24:36,020 INFO     [TimerExecutorThread-527]:strat.mining.stratum.proxy.pool.Pool - Suggest the difficulty 0.01 to the pool Nicehash LTC.
2017-10-22 10:24:36,100 ERROR    [Pool-Nicehash LTC-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=Nicehash LTC, host=scrypt.eu.nicehash.com:3333, username=ggSFP7USSnLd9mq7yZDt2CoXuFKCnD6bRe.Proxy, password=d=0.02;p=0.24, readySince=null, isReady=false, isEnabled=true, isStable=false, priority=0, weight=9].
2017-10-22 10:24:36,103 WARN     [Pool-Nicehash LTC-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool Nicehash LTC is DOWN. Moving connections to another one.
2017-10-22 10:24:36,104 INFO     [Pool-Nicehash LTC-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool Nicehash LTC stopped.
2017-10-22 10:24:36,105 INFO     [Pool-Nicehash LTC-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool Nicehash LTC in 5.0 seconds.
2017-10-22 10:24:40,852 INFO     [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.168.1.11:46849.
2017-10-22 10:24:40,865 ERROR    [192.168.1.11-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - No pool available for the connection 192.168.1.11. Sending error and close the connection.

The miner says dead, something is not right

The part in the proxy config that says "enableExtranonceSubscribe" : true, is already telling the proxy to connect to the pool using the extranonce so I am pretty sure that you do not need the #xnsub in the miner config.

You need two separate proxy instances to run two different algos.  I am not positive, I am not using this proxy for some time, but I think you can run both proxy instances on the same pi using different ports and then configure the miners to connect to the appropriate proxy instance based on port number.

Sorry if this has already been answered, I've only looked through 8 random pages. I have the proxy running on a Raspberry Pi.

What URL do I enter on the ASICs? It is currently stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub

Is it stratum+tcp://192.168.1.4:3333#xnsub or just 192.168.1.4:3333 ?

Is the proxy clever enough to handle both the L3+ and D3 at the same time? Assuming that I have this in the config. Or is it one pool at a time, meaning that I need 2 Pis?

 "pools" : [ {
    "name" : "Nicehash X11",
    "host" : "x11.eu.nicehash.com:3336",
    "user" : "19wv8FQKv3NkwTdzBCQn1AGsb9ghqBPWXi",
    "password" : "d=0.02;p=0.24",
    "enableExtranonceSubscribe" : true,
    "appendWorkerNames" : false,
    "workerNameSeparator" : ".",
    "useWorkerPassword" : false,
    "weight" : 9,
    "isEnabled": true
  }, {
    "name" : "Nicehash Script",
    "host" : "scrypt.eu.nicehash.com:3333",
    "user" : "19wv8FQKv3NkwTdzBCQn1AGsb9ghqBPWXi",
    "password" : "d=0.02;p=0.24",
    "enableExtranonceSubscribe" : true,
    "appendWorkerNames" : false,
    "workerNameSeparator" : ".",
    "useWorkerPassword" : false,
    "weight" : 9,
    "isEnabled": true
  } ]

yes you can use this for solo mining.


just set up stratuhm proxy same as you would set up your s9... then s9 point to proxy address and port .


U need at least 10 s9 to have a chance to take some block reward in few months. I do not recomand to solo mine if u have under 10 s9

try this in your setup

    "pools" : [ {
    "name" : "nicehash ltc",
    "host" : "scrypt.eu.nicehash.com:3333",
    "user" : "31wuZD2B92nUBxxxxxcca1zXH7kAUUQjUP",
    "password" : "x",
    "enableExtranonceSubscribe" : true,
    "appendWorkerNames" : false,
    "workerNameSeparator" : "_",
    "useWorkerPassword" : false,
    "weight" : 3,
    "isEnabled": true\


    "enableExtranonceSubscribe" : true,-------this is the important line for nicehash to work

Hi, I have a couple of questions, I hope you guys can help me out.

Is it possible to use this proxy to solo mine directly to the wallet?
We have Antminer S9, is this a issue? Some proxys dont 'like' Antminer S7 and S9, so it would be nice to get this confirmed.

Thanks in advance. Best regards, Jan

I am having absolutely the same issue. Did you manage to solve your problem?

Thanks in advance

your setup is correct ...

the proxy does not support these newer / nonstandard algos ...

#crysx