[1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration!

[Inaba]

Bitcoind was freaking out about the clock... it should be fixed now and all payments should have processed properly as of a few minutes ago.

[patica]

I have 7 workers with last activity 16h ago.
And ~ 400 emails for last 8 hours.
Try another fix

[SysRun]

Even with notification turned off the emails keep coming.

[MykelSilver]

Complete site including mining is offline atm
EDIT: I see in my terminal that shares are accepted. Only the API that reports these shares is offline.
It is not as serious as it looks.
all the best

[Inaba]

Website server was offline... not sure what was up there.  It's back up now, but stats will be wonky for a bit until it catches up with the mining servers.  All mining remained online though...

[Nemesis]

Its down on my end with CloudFlare Error

[Inaba]

Seems to be up here, no problems connecting.

[BitMinerN8]

Seems to be up here, no problems connecting.

Working here in SoCal on COX.

[Nemesis]

This is the error message

DNS Resolution Error
You've requested a page on a website (eclipsemc.com) that is on the CloudFlare network. Unfortunately, CloudFlare is currently unable to resolve your requested domain (eclipsemc.com). There are two potential causes of this:

Most likely: if the owner just signed up for CloudFlare it can take a few minutes for the website's information to be distributed to our global network. Check back in about 5 minutes and the site should be up and running and enjoying all the benefits of CloudFlare.

Less likely: something is wrong with this site's configuration. Usually this happens when accounts have been signed up with a partner organization (e.g., a hosting provider) and the provider's DNS fails.

Timestamp: Thu, 23 May 2013 08:55:36 -0700

Your IP address: *************

Requested URL: eclipsemc.com/

Error reference number: 1001

Server ID: FL_29F4

Process ID: PID_732ee712169053a

User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.64 Safari/537.31

[MykelSilver]

@Nemesis
http://forums.eukhost.com/f15/how-clear-flush-dns-cache-windows-linux-mac-machines-6337/#.UZ5A9-cybN0

 ipconfig /flushdns

[Inaba]

That's really weird.  I wonder if the local Cloudflare node you are connected to is having problems?

Is anyone else having an issue?

[Nemesis]

That's really weird.  I wonder if the local Cloudflare node you are connected to is having problems?

Is anyone else having an issue?

Its autosolved itself. I just checked again and it works now.

Weird.

[MacT]

That's really weird.  I wonder if the local Cloudflare node you are connected to is having problems?

Is anyone else having an issue?

 I am getting this:

This website is offline
No cached version is available
What's wrong?
The most likely causes:
The server is down for maintenance
There may be a network problem
The site may be experiencing excessive load
Retry for a live version of the site
What's CloudFlare?
This website uses CloudFlare in order to help keep it online when the server is down by serving cached copies of pages when they are unavailable. Unfortunately, a cached copy of the page you requested is not available, but you may be able to reach other cached pages on the site.

[mwm4bcf]

Question on 2-factor authentication.

Just purchased a Yubikey.  Tried (several times) to add to my account - but setting is ignored and no 2FA authentication is needed on login. Feature seems to be disabled?

Also tried the Google Authenticator setup.  This implementation uses a counter rather than a time-based OTP.  I run 2 versions of Google Auth on my PC desktop and neither has this option.  The time-based feature seems to be the standard and works fine for me on several other BTC sites.  Why this counter-based version that I can't use?

Thanks.

[Inaba]

Question on 2-factor authentication.

Just purchased a Yubikey.  Tried (several times) to add to my account - but setting is ignored and no 2FA authentication is needed on login. Feature seems to be disabled?

Also tried the Google Authenticator setup.  This implementation uses a counter rather than a time-based OTP.  I run 2 versions of Google Auth on my PC desktop and neither has this option.  The time-based feature seems to be the standard and works fine for me on several other BTC sites.  Why this counter-based version that I can't use?

Thanks.

Yubikey is working for me... is anyone else having troubles?  Are you sure you're clicking save?

As for counter based, I dislike the time based.  With a counter based one, you can copy down several numbers and keep them with you, so you don't need a phone or what have you available.  You can easily invalidate them by just advancing the counter 1 spot then as well.

The time based has only become a standard people people don't seem to understand the limitations of TOTP and how annoying it really is.  Especially if there's network lag, clock skew or improper implementation.

[mwm4bcf]

Yubikey is working for me... is anyone else having troubles?  Are you sure you're clicking save?

As for counter based, I dislike the time based.  With a counter based one, you can copy down several numbers and keep them with you, so you don't need a phone or what have you available.  You can easily invalidate them by just advancing the counter 1 spot then as well.

The time based has only become a standard people people don't seem to understand the limitations of TOTP and how annoying it really is.  Especially if there's network lag, clock skew or improper implementation.

Thanks for the quick response.  My mistake - I had been on blockchain.info for a while and on their account security settings page, there isn't any "save changes" (which I think there should always be).  So when I went to the EMC account security page, I failed to use the "save changes" button.  So I've corrected that, and have a few questions.

1) I've logged off and on quite a few times using the Yubikey.  A few of those times I get an error message: "OTP REPLAY ERROR", and need to try again.  Normally the next try it works fine.  Is this a timing issue?

2) I'd assume based on the above message that EMC DOES validate the OTP and not just look for the correct public key portion of the OPT field (I've read that Blockchain.info only validates the public key portion - BAD).  Is this correct?

3) I haven't tried, but EMC documentation says I can't ever remove this Yubikey setting? Is that correct?

4) On the GoogleAuth counter based setting, I want to know how this works.  If the account is set for that, does the EMC page give the user a "starting counter" which then is continuously incremented by 1 on each login attempt?  Sounds like no software is needed then.  If an error occurs (bad # for example) how would the user reset the counter?

Thanks much - hopefully these answers will also be helpful to other newbies.

[Inaba]

1) I've logged off and on quite a few times using the Yubikey.  A few of those times I get an error message: "OTP REPLAY ERROR", and need to try again.  Normally the next try it works fine.  Is this a timing issue?

I means you're trying to send the same code you've already sent or one in the chain that is before the latest one you've used. Any time a code is used all previous codes are invalidated, regardless of whether or not they've been used.

2) I'd assume based on the above message that EMC DOES validate the OTP and not just look for the correct public key portion of the OPT field (I've read that Blockchain.info only validates the public key portion - BAD).  Is this correct?

Yes, it validates the entire OTP, not just the first few bytes.

3) I haven't tried, but EMC documentation says I can't ever remove this Yubikey setting? Is that correct?

You should be able to remove it by switching your 2FA to GA or None.

4) On the GoogleAuth counter based setting, I want to know how this works.  If the account is set for that, does the EMC page give the user a "starting counter" which then is continuously incremented by 1 on each login attempt?  Sounds like no software is needed then.  If an error occurs (bad # for example) how would the user reset the counter?

As above, the OTP is deterministic.  As long as you have the starting seed, you can compute all keys to infinity.  However, once a key is used along that line to infinity, all previous codes that come before it are invalid.  All future codes are still valid until one is used, then all codes before it are rendered invalid. 

[cooler-persistence]

Ouch, I believe that is twice in the past week EMC round durations have gone over 1 day. 
Although they did have a run with higher than average earnings right before.

Is this an inherent challenge with smaller pools?  How should I look at this objectively? 

Active Miners    Round Duration    Round Shares    Your Shares    Current Speed    US1    US2    US3                                                    Est. Reward    BTC Earned
2036                    1d 01:30:23    22839171             xxxx                     2.84 TH/s            1205.52 GH/s    1154.73 GH/s    490.66 GH/s    xxx                    0 / 24 hours

[Inaba]

It's normal variance.  You want to look at it over the long term.  If you look at the last 50 blocks, we are doing better than the average, at 54.7%. 

[ocminer]

Somebody has to bring back the luck !