Ethereum Community Forum
Home› Mining› Pool Discussion
Vega Finally Unleashed! Fine-tuned performance and power consumption in a single chassis.

Ethereum Mining Pool Hub - 0% Fee, pays all kind of mining rewards, supports all miner programs

1…1314161819…22

Comments

  • miningpoolhubminingpoolhub Member Posts: 308 ✭✭
    adaseb said:

    By the way the us-east1.ethereum-classic.miningpoolhub.com:20556 is bad. It keeps disconnecting and reconnecting every 10 minutes or so on all my rigs.

    Any other stable USA type servers to use ?

    I tested us-east1 with 20556 port and it's working well.

    EthDcrMiner64.exe -epool us-east1.ethereum.miningpoolhub.com:20556 -ewal username.workername -eworker username.workername -esm 1 -epsw x -allpools 1 -dpool stratum+tcp://hub.miningpoolhub.com:20550 -dwal username.workername -dpsw x -dcoin sc

    Did you put -eworker option as well?
    10 minutes of reconnection means that pool found your miner setting is incorrect and blocked temporarily. This feature is to prevent from DDoS attacks, and to alarm normal miners who have wrong settings.

    Maybe share your command line and I will test and trace what's causing error.
    · Share on TwitterShare on Facebook
  • adasebadaseb Member Posts: 1,043 ✭✭✭
    edited August 2016
    It works 99% of the time but every 10-15 minutes or so there is a

    ETH: Stratum - socket send failed 10053, disconnect

    It reconnects very fast however and since the diff is low it submits shares again but its annoying with the fans changing speeds because it stops mining intermitantly.

    Here is my settings using claymore

    -esm 1
    -epool us-east1.ethereum-classic.miningpoolhub.com:20556
    -ewal adaseb.amd
    -eworker adaseb.amd
    · Share on TwitterShare on Facebook
  • hasherhasher Member Posts: 642 ✭✭✭
    Miningpoolhub's interface is a nightmare. Why can't you create something more easy to use like ethpool/ethermine? I'm sure you would attract many more miners if you had a much easier interface to use. @miningpoolhub
    · Share on TwitterShare on Facebook
  • miningpoolhubminingpoolhub Member Posts: 308 ✭✭
    adaseb said:

    It works 99% of the time but every 10-15 minutes or so there is a

    ETH: Stratum - socket send failed 10053, disconnect

    It reconnects very fast however and since the diff is low it submits shares again but its annoying with the fans changing speeds because it stops mining intermitantly.

    Here is my settings using claymore

    -esm 1
    -epool us-east1.ethereum-classic.miningpoolhub.com:20556
    -ewal adaseb.amd
    -eworker adaseb.amd

    @adaseb

    Did you put this option too?
    -allpools 1

    Maybe dev's fee gathering interruption?
    · Share on TwitterShare on Facebook
  • miningpoolhubminingpoolhub Member Posts: 308 ✭✭
    hasher said:

    Miningpoolhub's interface is a nightmare. Why can't you create something more easy to use like ethpool/ethermine? I'm sure you would attract many more miners if you had a much easier interface to use. @miningpoolhub

    Sorry about the nightmare interface. :D
    Actually miningpoolhub started small with only one pool (maxcoin at first), grew day by day, added hub feature, auto switching, auto exchange things.

    If miningpoolhub was just simple one coin pool like ethpool or ethermine, it should be much simpler.
    In other words, ethpool/ethermine can't provide several coin pool, auto switching, auto exchange things.

    I'll improve interface simpler and easier anyway.
    Thanks for your request.
    · Share on TwitterShare on Facebook
  • adasebadaseb Member Posts: 1,043 ✭✭✭
    miningpoolhub said:

    adaseb said:

    It works 99% of the time but every 10-15 minutes or so there is a

    ETH: Stratum - socket send failed 10053, disconnect

    It reconnects very fast however and since the diff is low it submits shares again but its annoying with the fans changing speeds because it stops mining intermitantly.

    Here is my settings using claymore

    -esm 1
    -epool us-east1.ethereum-classic.miningpoolhub.com:20556
    -ewal adaseb.amd
    -eworker adaseb.amd

    @adaseb

    Did you put this option too?
    -allpools 1

    Maybe dev's fee gathering interruption?
    Yes I have done that also. Same results. Every rig every 10 minutes or so gives that socket send failed error
    · Share on TwitterShare on Facebook
  • retherrether Member Posts: 258 ✭✭
    bitcanuck said:

    adaseb said:

    It works 99% of the time but every 10-15 minutes or so there is a

    ETH: Stratum - socket send failed 10053, disconnect

    It reconnects very fast however and since the diff is low it submits shares again but its annoying with the fans changing speeds because it stops mining intermitantly.

    Here is my settings using claymore

    -esm 1
    -epool us-east1.ethereum-classic.miningpoolhub.com:20556
    -ewal adaseb.amd
    -eworker adaseb.amd

    @adaseb
    I think this is a problem with claymore's stratum implementation. I was having similar problems until I switched to 20535 and esm 2.
    Yes, this is the same setting that fixed things for me too.
    · Share on TwitterShare on Facebook
  • michidamichida Member Posts: 31 ✭
    same thing here, use -esm 2 and the error will end
    · Share on TwitterShare on Facebook
  • edd_kedd_k Member Posts: 9 ✭
    I use Genoil's Miner 0.9.41-genoil-1.1.6 with eth-proxy 0.0.5.

    Wallet auth: all shares was rejected.
    Username auth: all fine except frequent disconnections and big ping. Like this:

    =============
    2016-08-03 10:05:40,309 INFO proxy # MAIN eth_submitWork 0x7e9417e9a5aeda26 by edd_k.main
    2016-08-03 10:05:40,448 INFO protocol # [136ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 10:05:42,085 INFO proxy # Disconnected from Stratum pool at asia1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 10:05:42,086 INFO stats # 2 peers connected, state changed 1 times
    2016-08-03 10:05:45,022 INFO stats # 3 peers connected, state changed 1 times
    2016-08-03 10:05:45,023 INFO proxy # Connected to Stratum pool at asia1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 10:05:45,457 INFO proxy # Disconnected from Stratum pool at europe1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 10:05:45,457 INFO stats # 2 peers connected, state changed 1 times
    2016-08-03 10:05:48,144 INFO stats # 3 peers connected, state changed 1 times
    2016-08-03 10:05:48,144 INFO proxy # Connected to Stratum pool at europe1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 10:05:49,194 INFO proxy # NEW_JOB MAIN_POOL
    ==============

    Also I see 5-15% of "Your Invalid" at the Dashboard.

    Using same software I had mined ETH at ethermine.org. Rare disconnections, ping about 50 ms, NO invalid shares at all.

    What actually can be wrong? Is it the server is overloaded?


    · Share on TwitterShare on Facebook
  • adasebadaseb Member Posts: 1,043 ✭✭✭
    -esm2 doesn't work with the ETH classic port.
    · Share on TwitterShare on Facebook
  • miningpoolhubminingpoolhub Member Posts: 308 ✭✭
    edd_k said:

    I use Genoil's Miner 0.9.41-genoil-1.1.6 with eth-proxy 0.0.5.

    Wallet auth: all shares was rejected.
    Username auth: all fine except frequent disconnections and big ping. Like this:

    =============
    2016-08-03 10:05:40,309 INFO proxy # MAIN eth_submitWork 0x7e9417e9a5aeda26 by edd_k.main
    2016-08-03 10:05:40,448 INFO protocol # [136ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 10:05:42,085 INFO proxy # Disconnected from Stratum pool at asia1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 10:05:42,086 INFO stats # 2 peers connected, state changed 1 times
    2016-08-03 10:05:45,022 INFO stats # 3 peers connected, state changed 1 times
    2016-08-03 10:05:45,023 INFO proxy # Connected to Stratum pool at asia1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 10:05:45,457 INFO proxy # Disconnected from Stratum pool at europe1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 10:05:45,457 INFO stats # 2 peers connected, state changed 1 times
    2016-08-03 10:05:48,144 INFO stats # 3 peers connected, state changed 1 times
    2016-08-03 10:05:48,144 INFO proxy # Connected to Stratum pool at europe1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 10:05:49,194 INFO proxy # NEW_JOB MAIN_POOL
    ==============

    Also I see 5-15% of "Your Invalid" at the Dashboard.

    Using same software I had mined ETH at ethermine.org. Rare disconnections, ping about 50 ms, NO invalid shares at all.

    What actually can be wrong? Is it the server is overloaded?


    Server load is fine.

    Seems like your eth-proxy is trying all server failover.
    Can you share your eth-proxy.conf near WALLET and ENABLE_WORKER_ID?

    WALLET = "0x0000000000000000000000000000000000000000"
    ENABLE_WORKER_ID = True


    ENABLE_WORKER_ID should be True. Please check this.
    · Share on TwitterShare on Facebook
  • miningpoolhubminingpoolhub Member Posts: 308 ✭✭
    adaseb said:

    -esm2 doesn't work with the ETH classic port.

    Did you try 20555 port?

    Maybe your commandline info would help me to investigate the issue as I don't have problem mining with 20555 currently.
    · Share on TwitterShare on Facebook
  • retherrether Member Posts: 258 ✭✭
    -esm2 works fine for me on 20555 port.
    · Share on TwitterShare on Facebook
  • edd_kedd_k Member Posts: 9 ✭
    miningpoolhub said:


    Server load is fine.

    Seems like your eth-proxy is trying all server failover.
    Can you share your eth-proxy.conf near WALLET and ENABLE_WORKER_ID?

    WALLET = "0x0000000000000000000000000000000000000000"
    ENABLE_WORKER_ID = True


    ENABLE_WORKER_ID should be True. Please check this.

    All as in guide (except FAILOVER3):

    ==============
    WALLET = "0x0000000000000000000000000000000000000000"
    ENABLE_WORKER_ID = True

    POOL_HOST = "us-east1.ethereum-classic.miningpoolhub.com"
    POOL_PORT = 20556
    POOL_FAILOVER_ENABLE = True
    POOL_HOST_FAILOVER1 = "europe1.ethereum-classic.miningpoolhub.com"
    POOL_PORT_FAILOVER1 = 20556
    POOL_HOST_FAILOVER2 = "asia1.ethereum-classic.miningpoolhub.com"
    POOL_PORT_FAILOVER2 = 20556
    POOL_HOST_FAILOVER3 = ""
    POOL_PORT_FAILOVER3 = 0
    ===============

    Maybe I also should try 20555?


    P.S.: Without specifying FAILOVER3 you will get next:

    # Trying to connect to Stratum pool at europe1.ethereum-classic.miningpoolhub.com:20556
    # Trying to connect to failover Stratum pool-1 at us-east1.ethereum-classic.miningpoolhub.com:20556
    # Trying to connect to failover Stratum pool-2 at asia1.ethereum-classic.miningpoolhub.com:20556
    # Trying to connect to failover Stratum pool-3 at eth-hk.dwarfpool.com:8008


    · Share on TwitterShare on Facebook
  • edd_kedd_k Member Posts: 9 ✭
    edited August 2016
    Sad picture :(

    Did the stale shares are treated as invalid?


    · Share on TwitterShare on Facebook
  • edd_kedd_k Member Posts: 9 ✭
    Changed to next list:
    main: EU
    fail1: US
    fail2: ASIA
    fail3: US

    I'm from Ukraine, but choosing EU server as main isn't good idea. First share - first disconnect:

    2016-08-03 18:38:40,726 WARNING proxy # Ethereum Stratum proxy version: 0.0.5
    2016-08-03 18:38:40,727 WARNING proxy # Trying to connect to Stratum pool at europe1.ethereum-classic.miningpoolhub.com:
    20556
    2016-08-03 18:38:40,727 WARNING proxy # Trying to connect to failover Stratum pool-1 at us-east1.ethereum-classic.mining
    poolhub.com:20556
    2016-08-03 18:38:40,729 WARNING proxy # Trying to connect to failover Stratum pool-2 at asia1.ethereum-classic.miningpoo
    lhub.com:20556
    2016-08-03 18:38:40,729 WARNING proxy # Trying to connect to failover Stratum pool-3 at us-east1.ethereum-classic.mining
    poolhub.com:20556
    2016-08-03 18:38:40,851 INFO stats # 1 peers connected, state changed 1 times
    2016-08-03 18:38:40,851 INFO proxy # Connected to Stratum pool at europe1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 18:38:40,900 WARNING proxy # -----------------------------------------------------------------------
    2016-08-03 18:38:40,901 WARNING proxy # PROXY IS LISTENING ON ALL IPs ON PORT 8081
    2016-08-03 18:38:40,901 WARNING proxy # -----------------------------------------------------------------------
    2016-08-03 18:38:40,901 WARNING proxy # Wallet: 0x0000000000000000000000000000000000000000
    2016-08-03 18:38:40,901 WARNING proxy # Worker ID enabled: True
    2016-08-03 18:38:40,903 WARNING proxy # Email monitoring disabled
    2016-08-03 18:38:40,903 WARNING proxy # Failover enabled: True
    2016-08-03 18:38:40,904 WARNING proxy # -----------------------------------------------------------------------
    2016-08-03 18:38:40,953 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:38:41,117 INFO stats # 2 peers connected, state changed 1 times
    2016-08-03 18:38:41,117 INFO proxy # Connected to Stratum pool at us-east1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 18:38:41,121 INFO stats # 3 peers connected, state changed 1 times
    2016-08-03 18:38:41,121 INFO proxy # Connected to Stratum pool at us-east1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 18:38:41,279 INFO stats # 4 peers connected, state changed 1 times
    2016-08-03 18:38:41,279 INFO proxy # Connected to Stratum pool at asia1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 18:38:42,713 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:38:43,707 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:38:48,997 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:38:51,187 INFO proxy # Hashrate for edd_k.main is 0.0 MHs
    2016-08-03 18:38:53,401 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:39:25,427 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:39:35,147 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:39:42,471 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:39:43,619 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:39:51,203 INFO proxy # Hashrate for edd_k.main is 19.284156 MHs
    2016-08-03 18:40:16,145 INFO proxy # MAIN eth_submitWork 0xbf4786291fbbdc6b by edd_k.main
    2016-08-03 18:40:16,196 INFO proxy # Disconnected from Stratum pool at europe1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 18:40:16,196 INFO stats # 3 peers connected, state changed 1 times
    2016-08-03 18:40:19,171 INFO stats # 4 peers connected, state changed 1 times
    2016-08-03 18:40:19,171 INFO proxy # Connected to Stratum pool at europe1.ethereum-classic.miningpoolhub.com:20556
    2016-08-03 18:40:28,157 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:40:34,841 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:40:43,914 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:40:51,243 INFO proxy # Hashrate for edd_k.main is 19.284156 MHs
    2016-08-03 18:40:51,678 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:41:00,198 INFO proxy # NEW_JOB MAIN_POOL
    · Share on TwitterShare on Facebook
  • edd_kedd_k Member Posts: 9 ✭
    edited August 2016
    But connected to EU without failovers I haven't disconnects and have ping ~60 ms...



    2016-08-03 18:48:09,630 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:48:13,507 INFO proxy # MAIN eth_submitWork 0x74dd692573d3dbb3 by edd_k.main
    2016-08-03 18:48:13,565 INFO protocol # [58ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 18:48:16,885 INFO proxy # NEW_JOB MAIN_POOL
    2016-08-03 18:48:17,015 INFO proxy # MAIN eth_submitWork 0x72f72337409ce5db by edd_k.main
    2016-08-03 18:48:17,072 INFO protocol # [56ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 18:48:17,914 INFO proxy # MAIN eth_submitWork 0x0fa46d9b5473be64 by edd_k.main
    2016-08-03 18:48:17,973 INFO protocol # [58ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 18:48:23,592 INFO proxy # MAIN eth_submitWork 0x955eea31ada84dd8 by edd_k.main
    2016-08-03 18:48:23,651 INFO protocol # [59ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 18:48:37,957 INFO proxy # MAIN eth_submitWork 0x7646ccd804a1f5d4 by edd_k.main
    2016-08-03 18:48:38,019 INFO protocol # [60ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 18:48:39,290 INFO proxy # MAIN eth_submitWork 0x6d8fe9626eb16e7b by edd_k.main
    2016-08-03 18:48:39,348 INFO protocol # [55ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 18:48:42,809 INFO proxy # MAIN eth_submitWork 0x0e55c8348161c35c by edd_k.main
    2016-08-03 18:48:42,865 INFO protocol # [55ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 18:48:54,144 INFO proxy # MAIN eth_submitWork 0xba47094bc3d9d65b by edd_k.main
    2016-08-03 18:48:54,418 INFO protocol # [271ms] eth_submitWork from 'edd_k.main' accepted
    2016-08-03 18:48:55,759 INFO proxy # NEW_JOB MAIN_POOL
    · Share on TwitterShare on Facebook
  • miningpoolhubminingpoolhub Member Posts: 308 ✭✭
    edited August 2016
    @edd_k

    I modified some suspicious points that causing disconnection in source code and restarted all region's pool software.
    I hope it's fixed now. Please monitor your log for a while.

    Stale shares are treated as valid stale shares and all counted. Seems like restarting pool just few minutes ago caused this kind of invalid share percent spike.

    Anyway, even if current settings work well, I would like to suggest you to use genoil-ethminer's Stratum mode mining. Don't use eth-proxy if you don't have some special reasons. Stratum protocol is much more efficient. Miners reported about 9% of profit increased when they changed to stratum from eth-proxy. Also miningpoolhub's stratum mode remembers last connection difficulty level, so miner and pool can start from optimized value when you reconnect.
    · Share on TwitterShare on Facebook
  • edd_kedd_k Member Posts: 9 ✭
    edited August 2016
    miningpoolhub said:

    @edd_k

    I modified some suspicious points that causing disconnection in source code and restarted all region's pool software.
    I hope it's fixed now. Please monitor your log for a while.

    Thanks!

    miningpoolhub said:

    @edd_k
    Anyway, even if current settings work well, I would like to suggest you to use genoil-ethminer's Stratum mode mining. Don't use eth-proxy if you don't have some special reasons. Stratum protocol is much more efficient. Miners reported about 9% of profit increased when they changed to stratum from eth-proxy. Also miningpoolhub's stratum mode remembers last connection difficulty level, so miner and pool can start from optimized value when you reconnect.

    I use proxy because it more informative.
    Thanks for explanation. I will try and compare working without it
    · Share on TwitterShare on Facebook
  • edd_kedd_k Member Posts: 9 ✭
    Also there is a problem with stats display:



    This not are "shares since last block" (as stated in the hint). Seems that this are "shares since couple of last blocks". "ETC balance" is also updates about once per 10 blocks. If this so by design, then it would be nice explain this in the hints/FAQ.
    · Share on TwitterShare on Facebook
  • miningpoolhubminingpoolhub Member Posts: 308 ✭✭
    edd_k said:

    Also there is a problem with stats display:



    This not are "shares since last block" (as stated in the hint). Seems that this are "shares since couple of last blocks". "ETC balance" is also updates about once per 10 blocks. If this so by design, then it would be nice explain this in the hints/FAQ.

    @edd_k

    "Last block" is updated within certain period. About 15~45 minutes.
    It is not updated in realtime, so it may introduce some confusion.

    I will make this information update interval shorter.
    Thank you for your suggestion.
    · Share on TwitterShare on Facebook
  • retherrether Member Posts: 258 ✭✭
    Any word on the Expanse pool?
    · Share on TwitterShare on Facebook
  • miningpoolhubminingpoolhub Member Posts: 308 ✭✭
    rether said:

    Any word on the Expanse pool?

    @rether

    I will add Expanse soon but I still have to deal with internal pool issues currently.
    Sorry for late opening.
    · Share on TwitterShare on Facebook
  • retherrether Member Posts: 258 ✭✭
    miningpoolhub said:

    rether said:

    Any word on the Expanse pool?

    @rether

    I will add Expanse soon but I still have to deal with internal pool issues currently.
    Sorry for late opening.
    No problem, thanks for the update.
    · Share on TwitterShare on Facebook
  • ImAMiner?ImAMiner? Member Posts: 208 ✭✭
    edited August 2016
    @miningpoolhub I just ran into a problem mining on 12020 port. I just had to restart a machine and it just so happened that at the same time I decided to mine etc on that one. On the hub workers I changed it to etc and restarted. The machine couldn't connect to the pool. Back on the hub workers page I changed it back to eth and it connected right away. So somehow I couldn't start mining etc.

    edit: Looks like switching on 12020 is not working anymore??? I tried moving a couple machines to etc and they are still on eth.

    edit2: somehow my miners are mining on 20535 now. I don't know what's going on. And it looks like you just restarted the pool because all my miners disconnected.

    edit3: so my miners are on 20535 because that's my first failover. Because I have ftime 5 they are trying to connect every 5 minutes to 12020. So 12020 is not working.
    · Share on TwitterShare on Facebook
  • retherrether Member Posts: 258 ✭✭
    ImAMiner? said:

    @miningpoolhub I just ran into a problem mining on 12020 port. I just had to restart a machine and it just so happened that at the same time I decided to mine etc on that one. On the hub workers I changed it to etc and restarted. The machine couldn't connect to the pool. Back on the hub workers page I changed it back to eth and it connected right away. So somehow I couldn't start mining etc.

    edit: Looks like switching on 12020 is not working anymore??? I tried moving a couple machines to etc and they are still on eth.

    edit2: somehow my miners are mining on 20535 now. I don't know what's going on. And it looks like you just restarted the pool because all my miners disconnected.

    edit3: so my miners are on 20535 because that's my first failover. Because I have ftime 5 they are trying to connect every 5 minutes to 12020. So 12020 is not working.

    I just had a similar thing happen. One of my miners on 12020 is getting its connection actively refused by the server when trying to mine ETH. I have another rig that is connecting fine at the moment.

    I still can't connect on that one rig on 12020.
    · Share on TwitterShare on Facebook
  • ImAMiner?ImAMiner? Member Posts: 208 ✭✭
    rether said:

    ImAMiner? said:

    @miningpoolhub I just ran into a problem mining on 12020 port. I just had to restart a machine and it just so happened that at the same time I decided to mine etc on that one. On the hub workers I changed it to etc and restarted. The machine couldn't connect to the pool. Back on the hub workers page I changed it back to eth and it connected right away. So somehow I couldn't start mining etc.

    edit: Looks like switching on 12020 is not working anymore??? I tried moving a couple machines to etc and they are still on eth.

    edit2: somehow my miners are mining on 20535 now. I don't know what's going on. And it looks like you just restarted the pool because all my miners disconnected.

    edit3: so my miners are on 20535 because that's my first failover. Because I have ftime 5 they are trying to connect every 5 minutes to 12020. So 12020 is not working.

    I just had a similar thing happen. One of my miners on 12020 is getting its connection actively refused by the server when trying to mine ETH. I have another rig that is connecting fine at the moment.

    I still can't connect on that one rig on 12020.
    Which server are you on?
    · Share on TwitterShare on Facebook
  • retherrether Member Posts: 258 ✭✭
    ImAMiner? said:

    rether said:

    ImAMiner? said:

    @miningpoolhub I just ran into a problem mining on 12020 port. I just had to restart a machine and it just so happened that at the same time I decided to mine etc on that one. On the hub workers I changed it to etc and restarted. The machine couldn't connect to the pool. Back on the hub workers page I changed it back to eth and it connected right away. So somehow I couldn't start mining etc.

    edit: Looks like switching on 12020 is not working anymore??? I tried moving a couple machines to etc and they are still on eth.

    edit2: somehow my miners are mining on 20535 now. I don't know what's going on. And it looks like you just restarted the pool because all my miners disconnected.

    edit3: so my miners are on 20535 because that's my first failover. Because I have ftime 5 they are trying to connect every 5 minutes to 12020. So 12020 is not working.

    I just had a similar thing happen. One of my miners on 12020 is getting its connection actively refused by the server when trying to mine ETH. I have another rig that is connecting fine at the moment.

    I still can't connect on that one rig on 12020.
    Which server are you on?
    us-east.ethash-hub.miningpoolhub.com:12020

    It was working fine all yesterday, not sure when this one started to have connection issues.
    · Share on TwitterShare on Facebook
  • shutfushutfu Member Posts: 320 ✭✭
    edited August 2016
    what is up with auto-switching port 17020? how much mining did i lose today, i just got home from work. My fault for not setting failover! That won't happen again

    I switched to port 20535 in the meantime, it works fine
    · Share on TwitterShare on Facebook
  • ImAMiner?ImAMiner? Member Posts: 208 ✭✭
    rether said:

    ImAMiner? said:

    rether said:

    ImAMiner? said:

    @miningpoolhub I just ran into a problem mining on 12020 port. I just had to restart a machine and it just so happened that at the same time I decided to mine etc on that one. On the hub workers I changed it to etc and restarted. The machine couldn't connect to the pool. Back on the hub workers page I changed it back to eth and it connected right away. So somehow I couldn't start mining etc.

    edit: Looks like switching on 12020 is not working anymore??? I tried moving a couple machines to etc and they are still on eth.

    edit2: somehow my miners are mining on 20535 now. I don't know what's going on. And it looks like you just restarted the pool because all my miners disconnected.

    edit3: so my miners are on 20535 because that's my first failover. Because I have ftime 5 they are trying to connect every 5 minutes to 12020. So 12020 is not working.

    I just had a similar thing happen. One of my miners on 12020 is getting its connection actively refused by the server when trying to mine ETH. I have another rig that is connecting fine at the moment.

    I still can't connect on that one rig on 12020.
    Which server are you on?
    us-east.ethash-hub.miningpoolhub.com:12020

    It was working fine all yesterday, not sure when this one started to have connection issues.
    For you and me, I think it was this morning.
    shutfu said:

    what is up with auto-switching port 17020? how much mining did i lose today, i just got home from work. My fault for not setting failover! That won't happen again

    I switched to port 20535 in the meantime, it works fine

    So 12020 and 17020 switching ports are down. shutfu, are you mining on the US servers as well? I'm assuming this is just affecting the US server because I would think there would be a lot more people complaining about disconnections.

    I fixed mine by editing config.txt through remote manager and extending ftime
    · Share on TwitterShare on Facebook
Sign In or Register to comment.