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

[nico579]

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

[mcsaba]

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?

[igotek]

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.

[BlackPrapor]

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 

[chrysophylax]

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 

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

[crypto_trader#43xzEXrP]

For example:
1. I have scrypt-asic, rented on https://miningrigrentals.com/
2. I have the wallet of coin with SCRYPT algorithm.
3. I have enabled RPC-server to do mining, using getwork method, after connecting by http

ccminer -a scrypt -o http://127.0.0.1:5000 -u rpcuser -p rpcpassword

or just without http:

ccminer -a scrypt -o 127.0.0.1:5000 -u rpcuser -p rpcpassword

4. I cann't do solo mining, using stratum+tcp://

ccminer -a scrypt -o stratum+tcp://127.0.0.1:5000 -u rpcuser -p rpcpassword

there is an errors after connecting...
5. Inside the account in https://miningrigrentals.com
I can specify only stratum+tcp:// mining pool.

SO CAN I CONNECT THE STRATUM-MINER using this proxy
and do SOLO MINING to RPC-server, using getwork-method?
If yes, how to configure this proxy for SCRYPT algo?

Also, is there any local stratum mining pools for windows?

[chrysophylax]

For example:
1. I have scrypt-asic, rented on https://miningrigrentals.com/
2. I have the wallet of coin with SCRYPT algorithm.
3. I have enabled RPC-server to do mining, using getwork method, after connecting by http

ccminer -a scrypt -o http://127.0.0.1:5000 -u rpcuser -p rpcpassword

or just without http:

ccminer -a scrypt -o 127.0.0.1:5000 -u rpcuser -p rpcpassword

4. I cann't do solo mining, using stratum+tcp://

ccminer -a scrypt -o stratum+tcp://127.0.0.1:5000 -u rpcuser -p rpcpassword

there is an errors after connecting...
5. Inside the account in https://miningrigrentals.com
I can specify only stratum+tcp:// mining pool.

SO CAN I CONNECT THE STRATUM-MINER using this proxy
and do SOLO MINING to RPC-server, using getwork-method?
If yes, how to configure this proxy for SCRYPT algo?

Also, is there any local stratum mining pools for windows?

Simple answer - No ...

This is why this is called a STRATUM PROXY.

You also need to realize that MOST coins these days do not have getwork implemented into their codebase and as such, you cannot mine solo. If in this coin you can, then you need to setup a stratum to mine directly to the getwork RPC, THEN the stratum-proxy to the stratum you setup. Hence why most people do not bother and mine directly with pools (who have stratums setup) with this proxy.

Hope that helps.

#crysx

[crypto_trader#43xzEXrP]

Simple answer - No ...

This is why this is called a STRATUM PROXY.

You also need to realize that MOST coins these days do not have getwork implemented into their codebase and as such, you cannot mine solo. If in this coin you can, then you need to setup a stratum to mine directly to the getwork RPC, THEN the stratum-proxy to the stratum you setup. Hence why most people do not bother and mine directly with pools (who have stratums setup) with this proxy.

Hope that helps.

#crysx

Thanks for your answer.
Hmm... But... Is there any local stratum pool for windows, to solo mining - using scrypt algorithm?
For example, I want to mining GEERTCOIN (scrypt-algo),
just to confirm transactions in the mainnet,
because I have more than 1 million GEERT,
and I want to holding this coins some years or decades.
I can do solo-mining this coin, using GPUs, after connecting to my wallet through RPC-server, over http.
In this case using getwork-method...
But difficulty is so high for GPU mining, and I want to using rented ASIC...

The main problem is that this ASIC's connecting by stratum+tcp://,
and this ASICS not connected over HTTP to RPC-server (if port-forwarding enabled).

Therefore, I was looking for a stratum proxy or local stratum pool,
if this illiquid coin will be delisted from some online stratum-pools.

[chrysophylax]

Simple answer - No ...

This is why this is called a STRATUM PROXY.

You also need to realize that MOST coins these days do not have getwork implemented into their codebase and as such, you cannot mine solo. If in this coin you can, then you need to setup a stratum to mine directly to the getwork RPC, THEN the stratum-proxy to the stratum you setup. Hence why most people do not bother and mine directly with pools (who have stratums setup) with this proxy.

Hope that helps.

#crysx

Thanks for your answer.
Hmm... But... Is there any local stratum pool for windows, to solo mining - using scrypt algorithm?
For example, I want to mining GEERTCOIN (scrypt-algo),
just to confirm transactions in the mainnet,
because I have more than 1 million GEERT,
and I want to holding this coins some years or decades.
I can do solo-mining this coin, using GPUs, after connecting to my wallet through RPC-server, over http.
In this case using getwork-method...
But difficulty is so high for GPU mining, and I want to using rented ASIC...

The main problem is that this ASIC's connecting by stratum+tcp://,
and this ASICS not connected over HTTP to RPC-server (if port-forwarding enabled).

That is the point ...

Because sCrypt ASIC's dominate this Algo, the only 'real' way to mine is via a pool. So is there no pools for this coin?

It won't matter whether stratum software is Linux or windows based (as you can always create a VM locally or VPS in the cloud), though most are Linux based. Stratum-mining is the most popular one, though I think it would be overkill to try setting it up. Is the Git for the coin available to you right now? We can have a look a little later for you if you like to see what effort we need to build a pool in our platform.

Apart from that, this StratumProxy is an efficient one. So when a pool is setup, you can push ALL the hashrate through it if you wish as long as it is pointed at a stratum to mine.

#crysx

[crypto_trader#43xzEXrP]

That is the point ...

Because sCrypt ASIC's dominate this Algo, the only 'real' way to mine is via a pool.
So is there no pools for this coin?

Yeap, but this pools are unstable and most from the pools - not working: https://bitcointalk.org/index.php?topic=1789401.0
For example, this unstable online statum pool - working sometimes:
https://theminingpoolstratum.selfip.com/geertcoin/public/index.php?page=statistics&action=blocks

But, i think, this illiquid coin,
will be delisted from many pools, after delisting from cryptopia...

So I want to setup my own stratum local pool on windows, and don't know how-to.

Is the Git for the coin available to you right now?

I'm not sure, but here's the source code.

Need to connect stratum miners to RPC server on wallet with getwork.

_{I see this (stratum miners -> to getwork wallet): https://github.com/fireduck64/SockThing (JAR files too),
but I don't understand how it works...
Is this supporting SCRYPT algo??
Can you make two-way proxy "stratum<->getwork", using this code?}

[aarons6]

That is the point ...

Because sCrypt ASIC's dominate this Algo, the only 'real' way to mine is via a pool.
So is there no pools for this coin?

Yeap, but this pools are unstable and most from the pools - not working: https://bitcointalk.org/index.php?topic=1789401.0
For example, this unstable online statum pool - working sometimes:
https://theminingpoolstratum.selfip.com/geertcoin/public/index.php?page=statistics&action=blocks

But, i think, this illiquid coin,
will be delisted from many pools, after delisting from cryptopia...

So I want to setup my own stratum local pool on windows, and don't know how-to.

Is the Git for the coin available to you right now?

I'm not sure, but here's the source code.

Need to connect stratum miners to RPC server on wallet with getwork.

_{I see this (stratum miners -> to getwork wallet): https://github.com/fireduck64/SockThing (JAR files too),
but I don't understand how it works...
Is this supporting SCRYPT algo??
Can you make two-way proxy "stratum<->getwork", using this code?}

what you want isnt going to work.. bitmain mostly disabled mining to RPC through core wallet-qt in the cgminer fork.


if the coin isnt listed whats the point tho?

[crypto_trader#43xzEXrP]

what you want isnt going to work.. bitmain mostly disabled mining to RPC through core wallet-qt in the cgminer fork.

The solo mining to RPC-server with getwork-method working
after connection to RPC-server over HTTP,
but rented asics connected using stratum+tcp:// - not HTTP.
And maybe, using stratum protocol for mining with getblocktemplate, not getwork...
So did I try to find the proxy "stratum miners -> getwork HTTP"

if the coin isnt listed whats the point tho?

If this coin will be delisted long time...
To make the working mainnet from two peers (after 3 years for example),
need to confirm the transactions in the mainnet, find the blocks, and need to do solo mining!
So I cann't do this myself, using rented asics.

Now, I can only do mining, using online pools...
But... If this coin will be illiquid the long time, this will be delisted from this online pools.

[aarons6]

what you want isnt going to work.. bitmain mostly disabled mining to RPC through core wallet-qt in the cgminer fork.

The solo mining to RPC-server with getwork-method working
after connection to RPC-server over HTTP,
but rented asics connected using stratum+tcp:// - not HTTP.
And maybe, using stratum protocol for mining with getblocktemplate, not getwork...
So did I try to find the proxy "stratum miners -> getwork HTTP"

if the coin isnt listed whats the point tho?

If this coin will be delisted long time...
To make the working mainnet from two peers (after 3 years for example),
need to confirm the transactions in the mainnet, find the blocks, and need to do solo mining!
So I cann't do this myself, using rented asics.

Now, I can only do mining, using online pools...
But... If this coin will be illiquid the long time, this will be delisted from this online pools.

so you are trying to keep a dead coin with no dev team alive by solo mining it..

like i said, the bitmain miners that you are trying to rent hash from wont be able to connect to your rpc.. ever.. it wont work.

you might be able to mine yourself on cpu or gpu.. but l3+'s cant solo mine on the core wallet like you want.
you have to get the source code for the yiimp pool and build a server with an actual stratum pool.

since you are mining it by yourself, a gpu miner with bfgminer in stratum mode via rpc could probably work. you wont need alot of hash rate if you are the only one mining the coin.. you can possible even get away with one of those moonlander usb sticks they use bfgminer.


i do have to tell you tho, it takes more then just one person mining a coin to keep it alive.. its not just going to pop back in and be popular in 3 years just because.
i understand you probably have a huge bag of these coins and you put money into mining them.. the coin has zero volume and that wont just change over time.

[crypto_trader#43xzEXrP]

@aarons6, thanks for the info.

GEERTCOIN is not dead coin,
just devs, maybe leave this coin, and official block-explorer is not working.
Also, this coin, for some reason (maybe, mining profitability)
was disabled on last working block explorer, inside the site: https://prohashing.com/explorer/
And cryptopia.co.nz stop trading, and delisting this coin, according delisting policy
But, this coin still trading here, with low volumes: https://www.coinexchange.io/market/GEERT/BTC
And mainnet is alive, transaction is confirming, because we can do mining on this pool.

So, I'm interested to make workin sync-node, and do solo mining
to support this network from any time, even if this coin will be inactive.
You say about I need to install my own open source stratum multipool yiimp/yaamp... And maybe - Iquidus block explorer!..
Ok. Good idea... But this soft not for Windows, and working on Ubuntu.
Therefore, I was looking for the proxy "stratum+tcp:// -> http rpc"...

Yea, I can do solo mining to RPC directly, with low difficulty, using GPU and processor.
And I could do to run solo mining only when any transactions
exist in the response of the console command "getrawmempool".
Now I can do mining, using public pools, but after several years - I'm not sure...  

Thanks, for the info about moonlander usb sticks ASICs.
Now, I think, I can install ubuntu, yiimp and iquidus on microSD or on USB too (liveUSB)!
And even if this all will not be online, this can be able to save (for my subnetwork),
the coin performance and full functionality, within long-time holding...
If our peers will stay last, we will be the first.

Also, the volumes of trading we can raise. We have bitcoins.
I think it would make sense all over the World,
during the upcoming elections in the Netherlands.

Have a nice day.

[SecretRecipe]

Does anyone know if its possible to get this proxy to work for multiple users? Not just multiple workers.. like I need it so that me and a couple friends can all mine to it and it will forward the hash like normal but we each can use our own wallet addresses also.. If this can't be made to do that can someone make me one or can someone recommend something else that will do the trick? This would be greatly appreciated and there is a tip for anyone that can deliver!

[chrysophylax]

Does anyone know if its possible to get this proxy to work for multiple users? Not just multiple workers.. like I need it so that me and a couple friends can all mine to it and it will forward the hash like normal but we each can use our own wallet addresses also.. If this can't be made to do that can someone make me one or can someone recommend something else that will do the trick? This would be greatly appreciated and there is a tip for anyone that can deliver!

Currently no ...

This is a feature we have been wanting for a long time, but since the results were basically that it would need a heavy rewrite, and pfool has left the project, then it would be a no go for almost anyone to do.

If there is someone that could port this proxy to C/C++, then my team could definitely work with you/anyone on this - or even take over the project. As it is stands though, being Java has a huge amount of limitations. Unless of course pfool would like to work on this with us on a private port full time of course

#crysx

[rsarkar]

Anybody can please suggest what might be the problem here

Everytime a worker tries to connect, the pool disconnects it and no share is submitted.

Code:

2019-11-29 00:50:48,289 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(2) started
2019-11-29 00:50:48,290 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool MRR X11(2) for 5 seconds.
2019-11-29 00:50:48,290 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is UP.
2019-11-29 00:50:48,318 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X11(3).
2019-11-29 00:50:48,319 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(3).
2019-11-29 00:50:48,519 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X11(2).
2019-11-29 00:50:48,520 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(2).
2019-11-29 00:50:53,039 WARN     [TimerExecutorThread-3]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X16r is STABLE.
2019-11-29 00:50:53,139 WARN     [TimerExecutorThread-3]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is STABLE.
2019-11-29 00:50:53,291 WARN     [TimerExecutorThread-3]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is STABLE.
2019-11-29 00:50:53,919 INFO     [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.99.19.169:52414.
2019-11-29 00:50:53,923 INFO     [192.99.19.169-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.99.19.169 subscribed. 1 connections active on pool MRR X16r.
2019-11-29 00:51:06,090 ERROR    [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X11(3), host=us-central01.miningrigrentals.com:50926, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=2, weight=1].
java.io.EOFException: Connection closed.
	at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:167)
2019-11-29 00:51:06,092 WARN     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is DOWN. Moving connections to another one.
2019-11-29 00:51:06,093 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(3) stopped.
2019-11-29 00:51:06,094 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X11(3) in 5.0 seconds.
2019-11-29 00:51:06,124 ERROR    [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X16r, host=us-east01.miningrigrentals.com:51116, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=0, weight=9].
java.io.EOFException: Connection closed.
	at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:167)
2019-11-29 00:51:06,125 WARN     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X16r is DOWN. Moving connections to another one.
2019-11-29 00:51:06,125 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Switching worker connections from pool MRR X16r to pool MRR X11(2).
2019-11-29 00:51:06,126 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Rebind connection 192.99.19.169 from pool MRR X16r to pool MRR X11(2) with setExtranonce notification.
2019-11-29 00:51:06,131 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X16r stopped.
2019-11-29 00:51:06,132 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X16r in 5.0 seconds.
2019-11-29 00:51:06,196 ERROR    [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X11(2), host=us-west01.miningrigrentals.com:50736, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=1, weight=2].
java.io.EOFException: Connection closed.
	at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:167)
2019-11-29 00:51:06,196 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is DOWN. Moving connections to another one.
2019-11-29 00:51:06,197 ERROR    [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Failed to rebind workers connections. No pool is available. Closing all workers connections.
strat.mining.stratum.proxy.exception.NoPoolAvailableException: No pool available. [Pool [name=MRR X16r, host=us-east01.miningrigrentals.com:51116, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=false, isEnabled=true, isStable=false, priority=0, weight=9], Pool [name=MRR X11(2), host=us-west01.miningrigrentals.com:50736, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=false, isEnabled=true, isStable=false, priority=1, weight=2], Pool [name=MRR X11(3), host=us-central01.miningrigrentals.com:50926, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=false, isEnabled=true, isStable=false, priority=2, weight=1]]
	at strat.mining.stratum.proxy.manager.strategy.PriorityFailoverStrategyManager.computeCurrentPool(PriorityFailoverStrategyManager.java:142)
	at strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager.checkConnectionsBinding(MonoCurrentPoolStrategyManager.java:65)
	at strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager.onPoolDown(MonoCurrentPoolStrategyManager.java:120)
	at strat.mining.stratum.proxy.manager.ProxyManager.onPoolStateChange(ProxyManager.java:468)
	at strat.mining.stratum.proxy.pool.Pool.stopPool(Pool.java:286)
	at strat.mining.stratum.proxy.pool.Pool.onDisconnectWithError(Pool.java:661)
	at strat.mining.stratum.proxy.pool.PoolConnection.onDisconnectWithError(PoolConnection.java:63)
	at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:171)
2019-11-29 00:51:06,198 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(2) stopped.
2019-11-29 00:51:06,199 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X11(2) in 5.0 seconds.
2019-11-29 00:51:11,094 INFO     [TimerExecutorThread-3]:strat.mining.stratum.proxy.pool.Pool$3 - Trying reconnect of pool ReconnectTask-MRR X11(3)...
2019-11-29 00:51:11,133 INFO     [TimerExecutorThread-2]:strat.mining.stratum.proxy.pool.Pool$3 - Trying reconnect of pool ReconnectTask-MRR X16r...
2019-11-29 00:51:11,155 INFO     [TimerExecutorThread-3]:strat.mining.stratum.proxy.pool.Pool - Suggest the difficulty 0.01 to the pool MRR X11(3).
2019-11-29 00:51:11,199 INFO     [TimerExecutorThread-3]:strat.mining.stratum.proxy.pool.Pool$3 - Trying reconnect of pool ReconnectTask-MRR X11(2)...
2019-11-29 00:51:11,201 INFO     [TimerExecutorThread-3]:strat.mining.stratum.proxy.pool.Pool - Suggest the difficulty 0.01 to the pool MRR X11(2).
2019-11-29 00:51:11,205 INFO     [TimerExecutorThread-2]:strat.mining.stratum.proxy.pool.Pool - Suggest the difficulty 0.01 to the pool MRR X16r.
2019-11-29 00:51:11,602 WARN     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown response type on connection Pool-MRR X11(3). methodName: mining.suggest_difficulty, result: true
2019-11-29 00:51:11,677 WARN     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown response type on connection Pool-MRR X16r. methodName: mining.suggest_difficulty, result: true
2019-11-29 00:51:11,833 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown response type on connection Pool-MRR X11(2). methodName: mining.suggest_difficulty, result: true
2019-11-29 00:51:12,002 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X16r started
2019-11-29 00:51:12,003 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool MRR X16r for 5 seconds.
2019-11-29 00:51:12,003 WARN     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X16r is UP.
2019-11-29 00:51:12,027 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(3) started
2019-11-29 00:51:12,027 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool MRR X11(3) for 5 seconds.
2019-11-29 00:51:12,028 WARN     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is UP.
2019-11-29 00:51:12,127 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X16r.
2019-11-29 00:51:12,128 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X16r.
2019-11-29 00:51:12,203 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X11(3).
2019-11-29 00:51:12,204 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(3).
2019-11-29 00:51:12,236 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(2) started
2019-11-29 00:51:12,236 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool MRR X11(2) for 5 seconds.
2019-11-29 00:51:12,237 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is UP.
2019-11-29 00:51:12,468 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X11(2).
2019-11-29 00:51:12,469 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.99.19.169 closed. 0 connections active on pool MRR X11(2). Cause: Socket closed
2019-11-29 00:51:12,469 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(2).

would be much appreciated

[chrysophylax]

Anybody can please suggest what might be the problem here

Everytime a worker tries to connect, the pool disconnects it and no share is submitted.

Code:

2019-11-29 00:50:48,289 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(2) started
2019-11-29 00:50:48,290 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool MRR X11(2) for 5 seconds.
2019-11-29 00:50:48,290 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is UP.
2019-11-29 00:50:48,318 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X11(3).
2019-11-29 00:50:48,319 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(3).
2019-11-29 00:50:48,519 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X11(2).
2019-11-29 00:50:48,520 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(2).
2019-11-29 00:50:53,039 WARN     [TimerExecutorThread-3]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X16r is STABLE.
2019-11-29 00:50:53,139 WARN     [TimerExecutorThread-3]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is STABLE.
2019-11-29 00:50:53,291 WARN     [TimerExecutorThread-3]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is STABLE.
2019-11-29 00:50:53,919 INFO     [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /192.99.19.169:52414.
2019-11-29 00:50:53,923 INFO     [192.99.19.169-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 192.99.19.169 subscribed. 1 connections active on pool MRR X16r.
2019-11-29 00:51:06,090 ERROR    [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X11(3), host=us-central01.miningrigrentals.com:50926, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=2, weight=1].
java.io.EOFException: Connection closed.
	at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:167)
2019-11-29 00:51:06,092 WARN     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is DOWN. Moving connections to another one.
2019-11-29 00:51:06,093 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(3) stopped.
2019-11-29 00:51:06,094 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X11(3) in 5.0 seconds.
2019-11-29 00:51:06,124 ERROR    [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X16r, host=us-east01.miningrigrentals.com:51116, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=0, weight=9].
java.io.EOFException: Connection closed.
	at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:167)
2019-11-29 00:51:06,125 WARN     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X16r is DOWN. Moving connections to another one.
2019-11-29 00:51:06,125 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Switching worker connections from pool MRR X16r to pool MRR X11(2).
2019-11-29 00:51:06,126 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Rebind connection 192.99.19.169 from pool MRR X16r to pool MRR X11(2) with setExtranonce notification.
2019-11-29 00:51:06,131 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X16r stopped.
2019-11-29 00:51:06,132 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X16r in 5.0 seconds.
2019-11-29 00:51:06,196 ERROR    [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X11(2), host=us-west01.miningrigrentals.com:50736, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=1, weight=2].
java.io.EOFException: Connection closed.
	at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:167)
2019-11-29 00:51:06,196 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is DOWN. Moving connections to another one.
2019-11-29 00:51:06,197 ERROR    [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Failed to rebind workers connections. No pool is available. Closing all workers connections.
strat.mining.stratum.proxy.exception.NoPoolAvailableException: No pool available. [Pool [name=MRR X16r, host=us-east01.miningrigrentals.com:51116, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=false, isEnabled=true, isStable=false, priority=0, weight=9], Pool [name=MRR X11(2), host=us-west01.miningrigrentals.com:50736, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=false, isEnabled=true, isStable=false, priority=1, weight=2], Pool [name=MRR X11(3), host=us-central01.miningrigrentals.com:50926, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 00:50:48 UTC 2019, isReady=false, isEnabled=true, isStable=false, priority=2, weight=1]]
	at strat.mining.stratum.proxy.manager.strategy.PriorityFailoverStrategyManager.computeCurrentPool(PriorityFailoverStrategyManager.java:142)
	at strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager.checkConnectionsBinding(MonoCurrentPoolStrategyManager.java:65)
	at strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager.onPoolDown(MonoCurrentPoolStrategyManager.java:120)
	at strat.mining.stratum.proxy.manager.ProxyManager.onPoolStateChange(ProxyManager.java:468)
	at strat.mining.stratum.proxy.pool.Pool.stopPool(Pool.java:286)
	at strat.mining.stratum.proxy.pool.Pool.onDisconnectWithError(Pool.java:661)
	at strat.mining.stratum.proxy.pool.PoolConnection.onDisconnectWithError(PoolConnection.java:63)
	at strat.mining.stratum.proxy.network.StratumConnection$1.run(StratumConnection.java:171)
2019-11-29 00:51:06,198 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(2) stopped.
2019-11-29 00:51:06,199 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X11(2) in 5.0 seconds.
2019-11-29 00:51:11,094 INFO     [TimerExecutorThread-3]:strat.mining.stratum.proxy.pool.Pool$3 - Trying reconnect of pool ReconnectTask-MRR X11(3)...
2019-11-29 00:51:11,133 INFO     [TimerExecutorThread-2]:strat.mining.stratum.proxy.pool.Pool$3 - Trying reconnect of pool ReconnectTask-MRR X16r...
2019-11-29 00:51:11,155 INFO     [TimerExecutorThread-3]:strat.mining.stratum.proxy.pool.Pool - Suggest the difficulty 0.01 to the pool MRR X11(3).
2019-11-29 00:51:11,199 INFO     [TimerExecutorThread-3]:strat.mining.stratum.proxy.pool.Pool$3 - Trying reconnect of pool ReconnectTask-MRR X11(2)...
2019-11-29 00:51:11,201 INFO     [TimerExecutorThread-3]:strat.mining.stratum.proxy.pool.Pool - Suggest the difficulty 0.01 to the pool MRR X11(2).
2019-11-29 00:51:11,205 INFO     [TimerExecutorThread-2]:strat.mining.stratum.proxy.pool.Pool - Suggest the difficulty 0.01 to the pool MRR X16r.
2019-11-29 00:51:11,602 WARN     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown response type on connection Pool-MRR X11(3). methodName: mining.suggest_difficulty, result: true
2019-11-29 00:51:11,677 WARN     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown response type on connection Pool-MRR X16r. methodName: mining.suggest_difficulty, result: true
2019-11-29 00:51:11,833 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.network.StratumConnection - Unknown response type on connection Pool-MRR X11(2). methodName: mining.suggest_difficulty, result: true
2019-11-29 00:51:12,002 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X16r started
2019-11-29 00:51:12,003 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool MRR X16r for 5 seconds.
2019-11-29 00:51:12,003 WARN     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X16r is UP.
2019-11-29 00:51:12,027 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(3) started
2019-11-29 00:51:12,027 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool MRR X11(3) for 5 seconds.
2019-11-29 00:51:12,028 WARN     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is UP.
2019-11-29 00:51:12,127 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X16r.
2019-11-29 00:51:12,128 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X16r.
2019-11-29 00:51:12,203 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X11(3).
2019-11-29 00:51:12,204 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(3).
2019-11-29 00:51:12,236 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(2) started
2019-11-29 00:51:12,236 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Testing stability of pool MRR X11(2) for 5 seconds.
2019-11-29 00:51:12,237 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is UP.
2019-11-29 00:51:12,468 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Set difficulty 24.0 on pool MRR X11(2).
2019-11-29 00:51:12,469 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Worker connection 192.99.19.169 closed. 0 connections active on pool MRR X11(2). Cause: Socket closed
2019-11-29 00:51:12,469 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(2).

would be much appreciated

X16R ...

Does his Stratum Proxy support X16R?

As for X11 via MRR - it seems that you have at least one of the MRR stratum parameters to NiceHash, as I recognise the closing of the pool connections. If that is so, this probably due to you using D3 ASIC's as the miners AND the ExtraNonce Subscribe issues that seem to prevalent with the NiceHash stratum connections. You will find that if this is the case, that if you point the ASIC directly to NH, and in most cases add the #xnsub parameter to the end of the URL) that these disconnection issues disappear. Via the Straum Proxy (and MRR) the issue seems to always reappear.

If there is a known fix that anyone has with this, it would be helpful to share.

Other than that, I cannot see anything else in what you have posted that could be casuing this disconnection issue.

#crysx

[rsarkar]

Im using stratehm-stratum proxy, ALgo x11 , x16r

basically what I want to try here is

Using a miner located in a remote ip --- > proxy stratum ---- > MRR
Keeping in mind the IP is not exposed.
But my workers keep getting disconnected for some reason that I can't see here:

Code:

2019-11-29 01:09:53,601 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(3).
2019-11-29 01:09:53,680 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(2) started
2019-11-29 01:09:53,681 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is UP.
2019-11-29 01:09:53,910 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(2).
2019-11-29 01:09:58,310 WARN     [TimerExecutorThread-1]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X16r is STABLE.
2019-11-29 01:09:58,426 WARN     [TimerExecutorThread-1]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is STABLE.
2019-11-29 01:09:58,681 WARN     [TimerExecutorThread-1]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is STABLE.
2019-11-29 01:10:00,469 INFO     [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /158.69.27.41:43132.
2019-11-29 01:10:00,472 INFO     [158.69.27.41-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 158.69.27.41 subscribed. 1 connections active on pool MRR X16r.
2019-11-29 01:10:09,178 ERROR    [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X16r, host=us-east01.miningrigrentals.com:51116, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 01:09:53 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=0, weight=9].
2019-11-29 01:10:09,180 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Switching worker connections from pool MRR X16r to pool MRR X11(2).
2019-11-29 01:10:09,181 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Rebind connection 158.69.27.41 from pool MRR X16r to pool MRR X11(2) with setExtranonce notification.
2019-11-29 01:10:09,183 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X16r stopped.
2019-11-29 01:10:09,184 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X16r in 5.0 seconds.
2019-11-29 01:10:09,191 WARN     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is DOWN. Moving connections to another one.
2019-11-29 01:10:09,192 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X11(3) in 5.0 seconds.
2019-11-29 01:10:09,424 ERROR    [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X11(2), host=us-west01.miningrigrentals.com:50736, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 01:09:53 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=1, weight=2].
2019-11-29 01:10:09,425 ERROR    [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Failed to rebind workers connections. No pool is available. Closing all workers connections.
2019-11-29 01:10:09,427 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X11(2) in 5.0 seconds.

[chrysophylax]

Im using stratehm-stratum proxy, ALgo x11 , x16r

basically what I want to try here is

Using a miner located in a remote ip --- > proxy stratum ---- > MRR
Keeping in mind the IP is not exposed.
But my workers keep getting disconnected for some reason that I can't see here:

Code:

2019-11-29 01:09:53,601 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(3).
2019-11-29 01:09:53,680 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X11(2) started
2019-11-29 01:09:53,681 WARN     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is UP.
2019-11-29 01:09:53,910 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New block detected on pool MRR X11(2).
2019-11-29 01:09:58,310 WARN     [TimerExecutorThread-1]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X16r is STABLE.
2019-11-29 01:09:58,426 WARN     [TimerExecutorThread-1]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is STABLE.
2019-11-29 01:09:58,681 WARN     [TimerExecutorThread-1]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(2) is STABLE.
2019-11-29 01:10:00,469 INFO     [StratumProxyManagerSeverSocketListener]:strat.mining.stratum.proxy.manager.ProxyManager$1 - New connection on /0.0.0.0:3333 from /158.69.27.41:43132.
2019-11-29 01:10:00,472 INFO     [158.69.27.41-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - New WorkerConnection 158.69.27.41 subscribed. 1 connections active on pool MRR X16r.
2019-11-29 01:10:09,178 ERROR    [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X16r, host=us-east01.miningrigrentals.com:51116, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 01:09:53 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=0, weight=9].
2019-11-29 01:10:09,180 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Switching worker connections from pool MRR X16r to pool MRR X11(2).
2019-11-29 01:10:09,181 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.worker.StratumWorkerConnection - Rebind connection 158.69.27.41 from pool MRR X16r to pool MRR X11(2) with setExtranonce notification.
2019-11-29 01:10:09,183 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Pool MRR X16r stopped.
2019-11-29 01:10:09,184 INFO     [Pool-MRR X16r-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X16r in 5.0 seconds.
2019-11-29 01:10:09,191 WARN     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.manager.ProxyManager - Pool MRR X11(3) is DOWN. Moving connections to another one.
2019-11-29 01:10:09,192 INFO     [Pool-MRR X11(3)-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X11(3) in 5.0 seconds.
2019-11-29 01:10:09,424 ERROR    [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Disconnection of pool Pool [name=MRR X11(2), host=us-west01.miningrigrentals.com:50736, username=rslsrkr.132864, password=x, readySince=Fri Nov 29 01:09:53 UTC 2019, isReady=true, isEnabled=true, isStable=true, priority=1, weight=2].
2019-11-29 01:10:09,425 ERROR    [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.manager.strategy.MonoCurrentPoolStrategyManager - Failed to rebind workers connections. No pool is available. Closing all workers connections.
2019-11-29 01:10:09,427 INFO     [Pool-MRR X11(2)-Thread]:strat.mining.stratum.proxy.pool.Pool - Trying reconnect of pool MRR X11(2) in 5.0 seconds.

Read above ...

It really depends on what miner, the setup, and where the proxy is pointing. You are supplying almost NO information other than the miners disconnect. I stated earlier that that looks like an issue that has been documented in the past about miners such as D3 and NiceHash pointing through this proxy, but without YOUR specific setup, how is any one going to help?

#crysx