Quote from: pinamalina on April 12, 2018, 09:44:47 PM

Quote from: kadok29 on April 12, 2018, 09:06:30 PM

Quote from: terrya on April 12, 2018, 07:25:48 PM

The connection issue still persist.
if you reboot router with dynamid ip
the miner cant connect to ethermine.org pool
you need to manual close and relaunch the program to connect
70-80% of rigs have this problem occur
while some can connect after router reboot

i'm agree... The connection issue still persist.

I did observe this problem when my dynamic IP changed by the ISP. However in my case Phoenix 2.8c auto-recovered from the situation on its own.
It attempted to connect to the main pool several times waiting 20 sec in between and then after 3 or so failed attempts successfully connected to the next pool from my epools.txt.

Possible workaround: Add second (or more) pool(s) to the epools.txt list. You can add the same pool there twice.
Example of epools.txt:
# Ethermine.org
# Main pool listed in the config.txt file: POOL: eu1.ethermine.org:4444, WALLET: %WALLET%.%WORKER%, PSW: x, WORKER: , ESM: 0, ALLPOOLS: 0
POOL: us1.ethermine.org:4444, WALLET: %WALLET%.%WORKER%, PSW: x, WORKER: , ESM: 0, ALLPOOLS: 0
POOL: us2.ethermine.org:4444, WALLET: %WALLET%.%WORKER%, PSW: x, WORKER: , ESM: 0, ALLPOOLS: 0
POOL: asia1.ethermine.org:4444, WALLET: %WALLET%.%WORKER%, PSW: x, WORKER: , ESM: 0, ALLPOOLS: 0
POOL: asia2.ethermine.org:4444, WALLET: %WALLET%.%WORKER%, PSW: x, WORKER: , ESM: 0, ALLPOOLS: 0

might works but other address will have different geo location which has higher ping time thus higher stale share...