Quote from: miningpoolhub on October 18, 2017, 02:07:47 AM

Quote from: not.you on October 17, 2017, 11:33:14 AM

Quote from: miningpoolhub on October 17, 2017, 02:34:14 AM

Quote from: not.you on October 16, 2017, 03:24:23 PM

I am completely unable to connect to ethereum pool. I have two miners which are already connected and they seem to be working but reconnecting another miner is not working at all. I have tried europe, US, and asia servers and I have tried direct and through a local proxy and nothing seems to work.

EDIT: So looks like claymore miner will connect. Can't get the proxy (I think it's slush's stratum proxy not entirely sure on that though) or genoil to connect.

slush's stratum proxy will not work with ETH pools.
Use claymore miner. It's well tested and performs well.

Unfortunately I get a lower hashrate with claymore. My other two miners that have stayed connected are using genoil and the local proxy (whatever it is) so it seems to work once it's going, its the connecting part that may have changed.

Whatever the problem is, it is new, maybe since the fork. This software combination had been working fine for more than a year. And as I say, the other two miners are still working.

What error do you get from genoil + proxy?
Please send me screenshot or some error message.

Maybe doing some "ipconfig /flushdns" command would help. This flushes old ip addresses.

FYI, ETH proxy degrades your hashrate about 9% because it polls every few seconds, not receives new block info in realtime.
If you want to stick to genoil, please mine with -S option which connects directly in stratum mode.

Proxy looks like this:

Quote from: ethproxy

C:\Users\admin\Documents\EthProxy>C:\Users\admin\Documents\EthProxy\mining_proxy.exe -o europe.ethereum.miningpoolhub.com -p 20535
2017-10-19 13:30:02,857 INFO proxy jobs. # C extension for midstate not available. Using default implementation instead.
2017-10-19 13:30:03,138 WARNING proxy mining_proxy.main # Stratum proxy version: 1.5.7
2017-10-19 13:30:03,138 WARNING proxy mining_proxy.main # Trying to connect to Stratum pool at europe.ethereum.miningpoolhub.com:20535
2017-10-19 13:30:03,278 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2017-10-19 13:30:03,278 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at europe.ethereum.miningpoolhub.com:20535
2017-10-19 13:30:03,278 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2017-10-19 13:30:03,403 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at europe.ethereum.miningpoolhub.com:20535
2017-10-19 13:30:03,403 INFO stats stats.print_stats # 0 peers connected, statechanged 1 times
2017-10-19 13:30:06,210 INFO stats stats.print_stats # 1 peers connected, statechanged 1 times
2017-10-19 13:30:06,210 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at europe.ethereum.miningpoolhub.com:20535
2017-10-19 13:30:06,210 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs
2017-10-19 13:30:06,351 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at europe.ethereum.miningpoolhub.com:20535
2017-10-19 13:30:06,351 INFO stats stats.print_stats # 0 peers connected, statechanged 1 times

It just cycles through that connected\disconnected process endlessly. It does this no matter what MPH server I try and use.

However I did get Genoil to work direct to the pool. Apparently the command line to connect to the pool needed to be slightly different than when connecting to the proxy, not just the -S switch, the user\password part as well.