Issues when Miners using Stratum Proxy

[crypto-expert]

Issues when Miners using Stratum Proxy

[ahmedbodi]

yeah ive noticed the getwork port on the pool has failed due to this. i guess i will have to rewrite it or get obigal to rewrite it when we get the chance @obigal

[litecoinsblog]

Thanks ahmed. Great work by the way!

[ahmedbodi]

no problem and thanks :)

[obigal]

Point me to the stratum proxy and Ill take a look and see what it's doing, I had some initial concerns there might be an issue with proxies, I already know vardiff will not work with 'getwork' proxies and will never be able to.

[ahmedbodi]

ahh then i guess ill have to remove that, its 1 function ill miss haha

[ahmedbodi]

the stratum proxy would be in slush0's repo i think although im not sure

[obigal]

I think the proxy should work if you connect to the stratum port on the proxy, getwork requests do not have any ids associated with them so they will never be able to work correctly with vardiff.

[litecoinsblog]

I can confirm that the miner having the issue is using
https://github.com/slush0/stratum-mining-proxy

He is using Getwork as CPU miners only support Getwork. This is why he had to use a proxy in the first place. This explains it then.

[obigal]

the latest version of poolers cpu miner supports stratum, if he has a bunch of machines and needs the proxy to 'get out' of his network try connecting to the stratum port on the proxy and see if that works.

[litecoinsblog]

Thank you. Will feed this back to the Miner.

[ahmedbodi]

great that its sorted. Im going to set the code so that getwork will only work when vardiff is disabled