bamajr

Oh, and FYI…

I use Google’s Authenticator for a lot of other services like App.net, Dropbox, Evernote, Facebook, GitHub and Google – all of which are still working correctly.

I’m also use Authy for CloudFlare and it is working, as well.

I’m not sure how to verify my phone against that time. I’m in CST and it is 7:36 PM here (or 19:36 in 24 hour) we are -6 UTC

The website says it is 1:36 AM.

Nope, but I am was a little skeptical about whether or not I saved the user profiles correctly, with it either. I think i did, but not sure.

Is there a plugin, you know of, which will check the server time?

I went through the complete install, activate, regenerate, save, delete (ftp) twice and still it doesn’t work.

I’m trying to look into the time issue, but I’m not sure how to get the time from my web host, just yet. I’ve already verified my phone has the correct time.

Right! So while I can’t explain why it quit working, right now, I’m verifying that I went through the whole process, to regenerate the new secret, including saving the user profile settings, when I did, try and change it.

That is what I’m testing, right now, using both your plugin and the other one.

Each time, I tried resetting the plugin, I scanned the QR Code. However, each time I deactivated the plugin, the same secret is automatically populated into the settings.

…and I am looking into the time issue. I just don’t know how to check it, exactly, on the server. I’m not aware of any way to do that, with WebSynthesis – so I have to find out.

How is the QR Code Generated? Google Charts API, right?

I did install the other google authenticator plugin, on one website, but not on any of the others. I’m testing your theory of the issue, with a different plugin, as the Google API, used by both plugins, would be the same.

Hah… I was just getting ready to ask you the same thing ??

Look, when something works, for as long as it did, then it quits working, after an update, I’m prone to believe the issue is in the update. I haven’t changed hosts, nor server configs since this plugin was working, till now, when they are not.

All of these have been on their same server for at least 6 months. They all worked until your most recent update.

Yes, I’ve tried checking the option for relaxing the time, within your plugin’s config (User Profiles).

Yes… Disabled, but not uninstalled. Also, before wasting your time with a random issue, I’ve verified that at least 3 of my websites are having the same problem.

All three started having the problem, at the same time – after updating to the latest version, after updating to WordPress 3.8

All three have the same issue – the Google Authenticator code was working, prior to the update, and now, no longer works, even after deleting the plugin, via FTP, re-installing it, via WordPress Admin, regenerating the key and re-adding it to Google’s Authenticator app.

All three issue the same error:

ERROR: The Google Authenticator code is incorrect or has expired.

Thanks Ron…

Guess I should have been more clear on how I was using these plugins together ?? but you did fully answer my question.

Fontello (https://fontello.com) isn’t one font, that I’m aware of. I’m pretty sure it’s a service, with multiple fonts. So, depending on which font is bing used, there are representations for App.net, Behance & Path, within Fontello, but under different font titles.

I would also guess that it is only a matter of time, before 500px and About.me have an option as well.

I found the underlying issue, though I’m not sure what is causing it. The WordPress Editor is removing part of the code, when the initial draft is saved. If I correct it, before I post (or after) this word count issue goes away!

Thanks anyway!