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

[djbert]

it has been sometime since I posted here and I am glad to see this post is still kicking! Well, I came here to ask if any thought has been made towards making a Synology NAS package for this proxy? I know there are Java packages for Synology NAS's, so I am guessing it would be a rather simple cross-over. Of course I am asking this because would love to use my NAS as my hub of sorts for all my miners, as opposed to running the proxy on my computer all the time. Thoughts anyone? 

[yslyung]

any new developements ? is it possible to add quota function ? want to split hashes to diff pools.

tia

[psjw4450]

2014-12-15 07:38:05,940 ERROR    [Grizzly-worker(4)]:strat.mining.stratum.proxy.worker.GetworkRequestHandler - Unsupported request content from 192.168.1.2: {"id": 0, "method": "getblocktemplate", "params": [{"capabilities": ["coinbasetxn", "workid", "coinbase/append"]}]}
2014-12-15 07:38:21,994 ERROR    [Grizzly-worker(4)]:strat.mining.stratum.proxy.worker.GetworkRequestHandler - Unsupported request content from 192.168.1.2: {"id": 0, "method": "getblocktemplate", "params": [{"capabilities": ["coinbasetxn", "workid", "coinbase/append"]}]}
2014-12-15 07:38:27,737 INFO     [Pool-NICEHASH-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool NICEHASH.
2014-12-15 07:38:37,360 ERROR    [Grizzly-worker(4)]:strat.mining.stratum.proxy.worker.GetworkRequestHandler - Unsupported request content from 192.168.1.2: {"id": 0, "method": "getblocktemplate", "params": [{"capabilities": ["coinbasetxn", "workid", "coinbase/append"]}]}

I keep getting this error when I try to connect my miner. 

[Pfool]

Your mining software try to connect on the proxy with the GetBlockTemplate protocol. This protocol is not supported by the proxy.

You should configure your mining software to use getwork instead. I know that cgminer/sgminer try to connect the first time with getblocktemplate then fallback to getwork if the first request fails (there is no problem with this behavior on this proxy).

[Zelek Uther]

Thanks Pfool for this awesome software! I'm trying to get it working so I can connect my miners to WestHash/NiceHash.

My configuration file looks like this (bitcoin address snipped):

Code:

{
 "logDirectory" : "/tmp/"
,"logLevel" : "INFO"
,"validateSha26GetworkShares": true
,"pools" :
  [
    {
     "name" : "WestHash SHA-256"
    ,"host" : "stratum.westhash.com:3334"
    ,"user" : "16k...br"
    ,"password" : ""
    ,"enableExtranonceSubscribe" : true
    }
  , {
     "name" : "NiceHash SHA-256"
    ,"host" : "stratum.nicehash.com:3334"
    ,"user" : "16k..br"
    ,"password" : ""
    ,"enableExtranonceSubscribe" : true
    }
  ]
}

What I see when I run it (again, bitcoin address snipped):

Code:

java -jar stratum-proxy.jar -f /home/zelek/stratum-proxy-0.5.1/stratum-proxy.conf
Use log directory /tmp
2014-12-17 07:00:35,486 INFO     [main]:strat.mining.stratum.proxy.configuration.ConfigurationManager - Using INFO LogLevel.
2014-12-17 07:00:35,491 INFO     [main]:strat.mining.stratum.proxy.configuration.ConfigurationManager - API log level not set. API logging disabled.
2014-12-17 07:00:35,507 INFO     [main]:strat.mining.stratum.proxy.configuration.ConfigurationManager - Database directory not specified. Using default one: /home/zelek/stratum-proxy-0.5.1/database.
2014-12-17 07:00:35,516 INFO     [main]:strat.mining.stratum.proxy.database.DatabaseManager - Starting DatabaseManager...
2014-12-17 07:00:36,086 INFO     [main]:strat.mining.stratum.proxy.database.DatabaseManager - DatabaseManager started.
2014-12-17 07:00:36,087 INFO     [main]:strat.mining.stratum.proxy.Launcher - Using pools: [Pool [name=WestHash SHA-256, host=stratum.westhash.com:3334, username=16kefMjm83C6Wb6D3p8db1pgD864dx6hbr, password=, readySince=null, isReady=false, isEnabled=true, isStable=false, priority=0, weight=1], Pool [name=NiceHash SHA-256, host=stratum.nicehash.com:3334, username=16kefMjm83C6Wb6D3p8db1pgD864dx6hbr, password=, readySince=null, isReady=false, isEnabled=true, isStable=false, priority=1, weight=1]].
2014-12-17 07:00:36,761 ERROR    [main]:strat.mining.stratum.proxy.pool.Pool - Failed to connect the pool NiceHash SHA-256.
java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:579)
	at java.net.Socket.connect(Socket.java:528)
	at strat.mining.stratum.proxy.pool.Pool.startPool(Pool.java:185)
	at strat.mining.stratum.proxy.manager.ProxyManager.startPools(ProxyManager.java:134)
	at strat.mining.stratum.proxy.Launcher.initProxyManager(Launcher.java:369)
	at strat.mining.stratum.proxy.Launcher.main(Launcher.java:126)
2014-12-17 07:00:36,768 INFO     [main]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool NiceHash SHA-256 in 5.0 seconds.
2014-12-17 07:00:36,772 INFO     [main]:strat.mining.stratum.proxy.manager.ProxyManager - ServerSocket opened on /0.0.0.0:3333.
2014-12-17 07:00:36,878 INFO     [Pool-WestHash SHA-256-Thread]:strat.mining.stratum.proxy.pool.Pool - Extranonce change subscribed on pool WestHash SHA-256.
2014-12-17 07:00:37,052 INFO     [Pool-WestHash SHA-256-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 256.0 on pool WestHash SHA-256.
2014-12-17 07:00:37,053 INFO     [Pool-WestHash SHA-256-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool WestHash SHA-256.
2014-12-17 07:00:37,054 INFO     [Pool-WestHash SHA-256-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool WestHash SHA-256 started
2014-12-17 07:00:37,055 WARN     [Pool-WestHash SHA-256-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool WestHash SHA-256 is STABLE.
2014-12-17 07:00:37,059 WARN     [Pool-WestHash SHA-256-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool WestHash SHA-256 is UP.
2014-12-17 07:00:37,516 ERROR    [main]:strat.mining.stratum.proxy.Launcher - Failed to start the proxy.
javax.ws.rs.ProcessingException: Failed to start Grizzly HTTP server: Address already in use
	at org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpServerFactory.createHttpServer(GrizzlyHttpServerFactory.java:244)
	at org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpServerFactory.createHttpServer(GrizzlyHttpServerFactory.java:87)
	at strat.mining.stratum.proxy.Launcher.initGetwork(Launcher.java:349)
	at strat.mining.stratum.proxy.Launcher.main(Launcher.java:129)
Caused by: java.net.BindException: Address already in use
	at sun.nio.ch.Net.bind0(Native Method)
	at sun.nio.ch.Net.bind(Net.java:444)
	at sun.nio.ch.Net.bind(Net.java:436)
	at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
	at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
	at org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler.bindToChannelAndAddress(TCPNIOBindingHandler.java:132)
	at org.glassfish.grizzly.nio.transport.TCPNIOBindingHandler.bind(TCPNIOBindingHandler.java:88)
	at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:233)
	at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:213)
	at org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:204)
	at org.glassfish.grizzly.http.server.NetworkListener.start(NetworkListener.java:680)
	at org.glassfish.grizzly.http.server.HttpServer.start(HttpServer.java:276)
	at org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpServerFactory.createHttpServer(GrizzlyHttpServerFactory.java:241)
	... 3 more
2014-12-17 07:00:40,275 INFO     [Pool-WestHash SHA-256-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool WestHash SHA-256.
2014-12-17 07:00:41,771 INFO     [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool$2 - Trying reconnect of pool ReconnectTask-NiceHash SHA-256...
2014-12-17 07:00:42,088 ERROR    [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool - Failed to connect the pool NiceHash SHA-256.
java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:579)
	at java.net.Socket.connect(Socket.java:528)
	at strat.mining.stratum.proxy.pool.Pool.startPool(Pool.java:185)
	at strat.mining.stratum.proxy.pool.Pool$2.run(Pool.java:673)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
2014-12-17 07:00:42,090 INFO     [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool NiceHash SHA-256 in 5.0 seconds.
2014-12-17 07:00:47,090 INFO     [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool$2 - Trying reconnect of pool ReconnectTask-NiceHash SHA-256...
2014-12-17 07:00:47,398 ERROR    [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool - Failed to connect the pool NiceHash SHA-256.
java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:579)
	at java.net.Socket.connect(Socket.java:528)
	at strat.mining.stratum.proxy.pool.Pool.startPool(Pool.java:185)
	at strat.mining.stratum.proxy.pool.Pool$2.run(Pool.java:673)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
2014-12-17 07:00:47,400 INFO     [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool NiceHash SHA-256 in 5.0 seconds.
2014-12-17 07:00:52,400 INFO     [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool$2 - Trying reconnect of pool ReconnectTask-NiceHash SHA-256...
2014-12-17 07:00:52,781 ERROR    [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool - Failed to connect the pool NiceHash SHA-256.
java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:579)
	at java.net.Socket.connect(Socket.java:528)
	at strat.mining.stratum.proxy.pool.Pool.startPool(Pool.java:185)
	at strat.mining.stratum.proxy.pool.Pool$2.run(Pool.java:673)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
2014-12-17 07:00:52,783 INFO     [TimerExecutorThread-0]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool NiceHash SHA-256 in 5.0 seconds.
^C2014-12-17 07:00:53,571 INFO     [Thread-0]:strat.mining.stratum.proxy.database.DatabaseManager - Close databases.
[db4o 8.0.249.16098   2014-12-17 07:00:53] 
 '/home/zelek/stratum-proxy-0.5.1/database/dbpools' closed by ShutdownHook.
2014-12-17 07:00:53,657 INFO     [Thread-0]:strat.mining.stratum.proxy.Launcher$1 - User requested shutdown... Gracefuly kill all connections...
2014-12-17 07:00:53,657 INFO     [Thread-0]:strat.mining.stratum.proxy.manager.ProxyManager - Closing the server socket on /0.0.0.0:3333.
2014-12-17 07:00:53,658 INFO     [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - Stop to listen incoming connection on /0.0.0.0:3333.
2014-12-17 07:00:53,659 WARN     [Thread-0]:strat.mining.stratum.proxy.manager.ProxyManager - Pool WestHash SHA-256 is DOWN. Moving connections to another one.
2014-12-17 07:00:53,666 INFO     [Thread-0]:strat.mining.stratum.proxy.pool.Pool - Pool WestHash SHA-256 stopped.
2014-12-17 07:00:53,666 INFO     [Thread-0]:strat.mining.stratum.proxy.Launcher$1 - Shutdown !

I'm trying to get this running on a laptop on Linux Mint 16.

Looking at this again... is it actually working? If it is connecting to WestHash, why does it try to connect to NiceHash, and why does that fail? I tried connecting one of my miners, but couldn't get it working. I was using 127.0.0.1:8888, but I'll try again with the IP address of the laptop.

Also, I can't get the web page working. I tried:
http://proxyIp:8888
where proxyIp is the IP address of the stratum proxy server (i.e. my laptop).

[Zelek Uther]

Got one miner working through the proxy server.

When I add new miners, it doesn't seem that the proxy server is picking them up. Do I have to restart the proxy server every time I add a new miner?

[Zelek Uther]

Does the appendWorkerNames feature work with NiceHash / WestHash?

I keep getting "worker not authorized" errors, and it seems that only one worker makes it through to the pool.

[Pfool]

Does the appendWorkerNames feature work with NiceHash / WestHash?

I keep getting "worker not authorized" errors, and it seems that only one worker makes it through to the pool.

I do not remember if Nicehash is able to track each of your worker individually (with a worker name like that BTC_ADDRESS.WORKER_NAME). But I think that only one worker can be authorized by TCP connection on Nicehash. If so, the appendWorkerNames will not work (and should indeed send this kind of error).

For your others errors:
-Do you now have access to the WebClient ?
-Do you connect your workers to the proxy through stratum or getwork ?

[Zelek Uther]

Does the appendWorkerNames feature work with NiceHash / WestHash?

I keep getting "worker not authorized" errors, and it seems that only one worker makes it through to the pool.

I do not remember if Nicehash is able to track each of your worker individually (with a worker name like that BTC_ADDRESS.WORKER_NAME). But I think that only one worker can be authorized by TCP connection on Nicehash. If so, the appendWorkerNames will not work (and should indeed send this kind of error).

For your others errors:
-Do you now have access to the WebClient ?
-Do you connect your workers to the proxy through stratum or getwork ?

NiceHash/WestHash does allow individual worker names by appending .workername to the BTC address.

The WebClient still isn't working, still getting a grizzly error.

All workers are connecting through stratum.

A new issue I have is that I'm trying to do another install of the stratum proxy on a Raspberry Pi (for use at one of my mining locations).
I'm using Raspbian "Wheezy".

Code:

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ uname -a
Linux raspberrypi5 3.12.22+ #691 PREEMPT Wed Jun 18 18:29:58 BST 2014 armv6l GNU/Linux

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ cat /proc/version
Linux version 3.12.22+ (dc4@dc4-arm-01) (gcc version 4.7.2 20120731 (prerelease) (crosstool-NG linaro-1.13.1+bzr2458 - Linaro GCC 2012.08) ) #691 PREEMPT Wed Jun 18 18:29:58 BST 2014

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ cat /etc/issue
Raspbian GNU/Linux 7 \n \l

This is the error:

Code:

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ java -version
java version "1.6.0_32"
OpenJDK Runtime Environment (IcedTea6 1.13.4) (6b32-1.13.4-1~deb7u1+rpi1)
OpenJDK Zero VM (build 23.25-b01, mixed mode)

pi@raspberrypi5 ~/stratum-proxy-0.5.1 $ java -jar /home/pi/stratum-proxy-0.5.1/stratum-proxy.jar -f /home/pi/stratum-proxy-0.5.1/stratum-proxy.conf
Exception in thread "main" java.lang.UnsupportedClassVersionError: strat/mining/stratum/proxy/Launcher : Unsupported major.minor version 51.0
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:643)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
	at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
Could not find the main class: strat.mining.stratum.proxy.Launcher. Program will exit.

This is the Java version that was installed by the command:
sudo apt-get install default-jre

[Pfool]

For the grizzly error, it seems that the Getwork TCP port is already in user by another program (The Getwork error prevents the WebClient to start). If you do not use Getwork, you can disable it with the "disableGetwork": true option.

I have seen your post on the Nicehash thread and the nicehash response. I was not aware of this bug with the appendWorkerName and I do not understand why it does not work. I will try to contact Nicehash to get some details on this bug.

For your raspberry problem, the proxy only works with java >= 1.7 (the installed one is 1.6). You can try to install it with: sudo apt-get install openjdk-7-jre

[Zelek Uther]

For the grizzly error, it seems that the Getwork TCP port is already in user by another program (The Getwork error prevents the WebClient to start). If you do not use Getwork, you can disable it with the "disableGetwork": true option.

I have seen your post on the Nicehash thread and the nicehash response. I was not aware of this bug with the appendWorkerName and I do not understand why it does not work. I will try to contact Nicehash to get some details on this bug.

For your raspberry problem, the proxy only works with java >= 1.7 (the installed one is 1.6). You can try to install it with: sudo apt-get install openjdk-7-jre

Thanks for the tips Pfool, I'll try the disableGetwork parameter.

It would be awesome if appendWorkerName could work with Nice/WestHash!

I solved the Java issue a different way (which I'll post up just for reference). Next time I install it I'll try the command you suggest as it is easier than the method I used. (EDIT: done, and altered the instructions to use the simpler Java install command you suggested).

[Zelek Uther]

How to install Pfool's stratum proxy on a Raspberry Pi running Raspbian

Noob note: the lines below with a colon at the end are headings to describe each section. You only need to type the commands underneath them.

Get latest updates:
sudo apt-get update
sudo apt-get dist-upgrade

Get Java:
sudo apt-get install openjdk-7-jre

Pfool's stratum proxy install:
wget https://github.com/Stratehm/stratum-proxy/releases/download/0.5.1/stratum-proxy-0.5.1.zip
unzip stratum-proxy-0.5.1.zip

EDIT: simplify the instructions.

[Zelek Uther]

Is it possible to connect to a stratum proxy server in a remote location? Would the traffic be high? Would the added delay be unacceptable?

The reason I ask is that my mining rig is split across three locations, and it would be handy to not have to set up and maintain three stratum proxy servers.

[Zelek Uther]

I have the following workers on WestHash:

Code:

Worker  Speed accepted  Speed rejected     Diff       Time (minutes)  Multi-algo parameters  Extranonce subscription
VWG       38.4829       274.8779 (87.72%)   128.0000  381		                     Y
Home    5981.3433         0.0000 (0.00%)   4096.0000  299		                     Y
SP30B   4104.8434         0.0000 (0.00%)   4096.0000   27		                     N
Not all workers are using extranonce.subscribe. Check out how to optimise your mining speed with extranonce.subscribe.

The "VWG" and "Home" workers are stratum servers. "Home" should be 6.6TH/s and "VWG" should be 3.1TH/s.
SB30B is a directly connected SP30, I plan to put it and SP30A on a stratum proxy to avoid the disconnects. SP30A is offline right now, no idea why.

Why is VWG so low? It was previously showing us as 3000, now it is very low with a high percentage of speed rejected.
I have "validateSha26GetworkShares": true , I thought this would prevent any rejected shares?

I'm pointing 18TH/s at WestHash, but only being recognised for 10TH/s.

[Pfool]

I have "validateSha26GetworkShares": true , I thought this would prevent any rejected shares?

The "validateSha26GetworkShares" option only validate shares that are submitted by Getwork workers. It has no impact on stratum.

Code:

Worker  Speed accepted  Speed rejected     Diff       Time (minutes)  Multi-algo parameters  Extranonce subscription
VWG       38.4829       274.8779 (87.72%)   128.0000  381		                     Y
Home    5981.3433         0.0000 (0.00%)   4096.0000  299		                     Y
SP30B   4104.8434         0.0000 (0.00%)   4096.0000   27		                     N
Not all workers are using extranonce.subscribe. Check out how to optimise your mining speed with extranonce.subscribe.

These numbers are through the proxy or with miners directly connected to Nicehash/Westhash ?

Is it possible to connect to a stratum proxy server in a remote location? Would the traffic be high? Would the added delay be unacceptable?

The reason I ask is that my mining rig is split across three locations, and it would be handy to not have to set up and maintain three stratum proxy servers.

No problem to connect workers on the proxy remotly. Just be sure that the port 3333 of the proxy is reachable from Internet. However, take care of the network latency between your worker and the proxy and between the proxy and the pool. A high latency will increase the reject rate of your workers.

[cloudhashing_patrick]

First of all, excellent work, this works very well (which is something I cannot say for the majority of mining related software).

A few suggestions:

The documentation could be more complete, especially around the available configuration options.

Validation for stratum submissions would be pretty useful (there are certain clients which attempt to submit work on re-connect even if extranoonce1 changes).

Consider making multiple connections to the upstream pool to support > 256 clients. (Possibly this could simply be equally weighted round robin).

Ability to specify the source address for the upstream pool's tcp connection, lots of pools have various rate limiting restrictions which can be effectively side stepped this way.

[smracer]

I have been fucking around with Slush's stratum-mining-proxy for 2 days.  It would run for 15min - 1 hour and then disconnect with Duplicate shares errors.

I installed this server in 15 min and it has been stable thus far with 247 workers.

It it stays up for a few hours I am sending you a tip.

Thanks!

[Pfool]

First of all, excellent work, this works very well (which is something I cannot say for the majority of mining related software).

A few suggestions:

The documentation could be more complete, especially around the available configuration options.

Validation for stratum submissions would be pretty useful (there are certain clients which attempt to submit work on re-connect even if extranoonce1 changes).

Consider making multiple connections to the upstream pool to support > 256 clients. (Possibly this could simply be equally weighted round robin).

Ability to specify the source address for the upstream pool's tcp connection, lots of pools have various rate limiting restrictions which can be effectively side stepped this way.

Indeed, the documentation is out of date, I will try to find time to update it.

The stratum validation and outgoing connection local address binding are already in the todo list. Multiple connections to pools is a bit harder to implement, so I cannot promise you it will be done one day.

[Pfool]

I have been fucking around with Slush's stratum-mining-proxy for 2 days.  It would run for 15min - 1 hour and then disconnect with Duplicate shares errors.

I installed this server in 15 min and it has been stable thus far with 247 workers.

It it stays up for a few hours I am sending you a tip.

Thanks!

I hope it will be fine. Please, let me know the result of your testing.

Thanks

[jk9694]

OK so I am tired of beating my head on the desk,

2014-12-23 21:45:06,882 ERROR    [/107.170.50.27:25404-Thread]:strat.mining.stratum.proxy.network.StratumConnection - JSON-RPC Parsing error with line: {"id":"auth","method":"mining.authorize","params":["x","x"]}

Can anyone shed some light on this.

Conf...

{
  "isScrypt" : true,
  "hashrateDatabaseSamplingPeriod": 10,
  "stratumListenPort" : 3333,
  "stratumListenAddress" : "192.168.1.10",
  "disableStratum": false,
  "getworkListenPort" : 3332,
  "getworkListenAddress" : "192.168.1.10",
  "disableGetwork": true,
  "apiListenPort" : 8888,
  "apiListenAddress" : "0.0.0.0",
  "databaseDirectory": "database2",
  "noMidstate": false,
  "pools" :
  [
  {
    "name" : "------------",
    "host" : "---------------------------------",
    "user" : "---------------------------------",
    "password" : "x",
    "enableExtranonceSubscribe" : false
  }
  ]
}

I get this error whenever I try to connect with stratum+tcp://192.168.1.10:3333 user:x pass:x

noMidstate is probably not needed, just trying other options blindly...