inthylight

Hi queenbeeqt,

Sorry to hear about the trouble! First things first, if you are being locked out by the Clef plugin (rather than another issue on your server), see the unlock guide for how to remove the plugin and regain access immediately.

If you re-try the plugin and are still seeing a CURL error, then you check the following:

(a) that you are running the latest stable version of WP core,

(b) that your web server and/or WP application is not running a firewall that is blocking incoming or outgoing requests to the Clef API server (i.e., https://clef.io) (see the firewall guide),

(c) that you are not experiencing a theme and/or plugin conflict (see the conflict resolution guide),

and (d) that your web server is running a stable and updated version of CURL.

If you re-try the plugin and continue to see the state parameter error, then check to make sure that all of the layers on your caching stack (i.e., reverse proxy, server-side cache, web application cache) are excluding the login script from the cache. See the state param guide.

Hi aykutyunus,

Even though the plugin page has not yet been updated to show support for WP 4.7, the plugin does in fact support 4.7.

The error you are experiencing is more than likely a theme and/or plugin compatibility issue. See this guide on testing with the baseline method to determine the cause.

Hi bgwalker,

Can you try the steps in this guide? I think these should get you rolling. . . .

@avinash76 Please see this guide.

@gferry

Yes, a while back as in version 2.5.1 in May 2016…but it sounds like outdated versions of core or the plugin is not the issue.

If you’re still seeing this error, and if a fresh re-install (from the WP.com repository via your WP Dashboard -> Plugins menu, not from your GoDaddy control Panel) doesn’t resolve it, then there’s one more thing to check: test whether you are facing a theme/plugin compatibility issue.

If you’re able to rule out a compatibility issue, then likely the best path for a resolution is to follow up with GoDaddy’s support.

@gferry

This issue was fixed a while back. Can you try the following:
– double-check that your WP core is up to date
– then perform a fresh install of the Clef 2FA plugin (i.e., delete any pre-existing versions)

@jkmwp it looks like you’ve got an automatic redirect for https. The Clef logout hook URL is protocol specific . . . I updated it to https:// for you. Can you log out and log back in; then perform a log out? Unless there is a plugin conflict also at issue, it should be working now.

Hi Jamie,

Send us a note at [email protected]. We’d love to learn more about your project needs and see whether a business-tier plan makes good sense for your use case or whether you’ll be just fine on the free-tier plan.

Hi Jamie,

Send us a note at [email protected]. We’d love to learn more about your project needs and see whether a business-tier plan makes good sense for your use case or whether you’ll be just fine on the free-tier plan.

• This reply was modified 8 years, 2 months ago by inthylight.

@ldowdell

Hi there,

Based on this message it is not clear to me that this is a Clef 2FA-related issue (i.e., it’s possible that a file was corrupted during a core or plugin update).

If you’ve already tried the troubleshooting steps in this guide and determined that the issue is related to Clef 2FA, can you send an email to support [at] getclef.com, and we’ll begin the discovery process.

Hi Rahul,

You’re covered. Please see this guide.

Hi Steve,

You are correct: the disable passwords for Clef-enabled users setting is automatically turned on after the first successful Clef log in by the admin user who installs the plugin. You can turn the setting off any time thereafter, if you prefer.

If you are asking is there a way not to have that happen on the current plugin’s settings, no.

If you are asking can you do it yourself with a code modification, yes; to see where the mods need to be made, look at this old PR.

@tomhodgson

Hi Tom,

The fix in the beta mentioned above was pushed live in version 2.5.5 back in June. Can you double-check that you are running the latest version of the plugin?

Hi mallard66,

No, that is not the way it is supposed to work. Based on your description, it sounds like there is a plugin and/or theme conflict that is causing the issue. To find the cause, please see this troubleshooting guide.

Hi xarain,

Thanks for the encouragement, we appreciate it.

On your question, there are two things here:

a) I’m not sure what you mean by #3 above. If you’d like to follow up on this, can you email [email protected] with the URL of the site in question, and we’ll take a look.

b) There are many ways to handle the brute-force vector. Clef 2FA stops brute-force cold at the application layer (i.e., you don’t need Clef 2FA + captcha). Depending on your server setup, traffic volume, and security goals, it may make better sense to consider pre-application layers of defense rather than sorting out a plugin conflict between Clef 2FA and a captcha plugin; see the second half of this guide.