Doesn’t work with Duo plug-in since today’s update

Hi @kkelley0213,

You mentioned Duo plugin means “Duo Two-Factor Authentication” ? or any other please let us know.

https://www.ads-software.com/plugins/duo-wordpress/

Here it can not run together means what exact issue can you please brief the issue so we can cross check internally and if possible solve the issue if possible

Regards

Hey @hjogiupdraftplus,

I found that we are also having issues with these two plugins. The “Duo Two-Factor Authentication” plugin that you linked in your reply is the correct one. When logging into the admin dashboard with both plugins active, you will receive a “There has been a critical error on this website” error. Disabling the Duo plugin or the All In One WP Security plugin fixes the issue. It seems that there is some kind of conflict.

I believe this is the issue that @kkelley0213 is referring to.

Here are some details from the automated email I recieved:

WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, All In One WP Security.

…

Error Details
=============
An error of type E_ERROR was caused in line 678 of the file /home/user/site_url/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php. Error message: Uncaught Error: Call to undefined function get_active_blog_for_user() in /home/user/site_url/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php:678
Stack trace:
#0 /home/user/site_url/wp-includes/class-wp-hook.php(324): AIOWPSecurity_User_Login->wp_logout_action_handler(0)
#1 /home/user/site_url/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(false, Array)
#2 /home/user/site_url/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#3 /home/user/site_url/wp-includes/pluggable.php(671): do_action(‘wp_logout’, 0)
#4 /home/user/site_url/wp-content/plugins/duo-wordpress/duo_wordpress.php(212): wp_logout()
#5 /home/user/site_url/wp-content/plugins/duo-wordpress/duo_wordpress.php(274): duo_start_second_factor(Object(WP_User))
#6 /home/user/site_url/wp-includes/class-wp-hook.php(324): duo_authenticate_user(Object(WP_User), ‘username’, ‘password’)
#7 /home/user/site_url/wp-includes/plugin.php(205): WP_Hook->apply_filters(NULL, Array)
#8 /home/user/site_url/wp-includes/pluggable.php(618): apply_filters(‘authenticate’, NULL, ‘username’, ‘password.’)
#9 /home/user/site_url/wp-includes/user.php(106): wp_authenticate(‘username’, ‘passsword.’)
#10 /home/user/site_url/wp-login.php(1311): wp_signon(Array, true)
#11 {main}
? thrown

Thanks!

Yes, it was the Duo Two-Factor Authentication plugin and I got the error that Luke described above.

I am able to login when I disable one or the other plugin, but I need to use both.

Same exact issue with the Google Authenticator plug-in: https://www.ads-software.com/plugins/google-authenticator/

After yesterday’s update, I am getting a 502 bad gateway error when attempting to login after entering user name, password, and token. Disabling either plugin works, but I’d ideally like to keep both active.

I think I figured out a fix (at least for the Google Authenticator plugin). I have multiple sites and noticed a difference in configuration from one that is working fine with the latest version from the one that is not. When the Google Authenticator prompt appears on the second login page (user name and password first, then login, then GA on the next page), I get the Bad Gateway error. If I have the Google Authenticator field on the same page with the user name and password, it works.

For me, this setting is configurable in Settings > Google Authenticator.

Can confirm this recent update (version 5.2.7) prevents login when Duo Authenticator plugin is in use. Since I use Duo Authenticator and AIOS on all of my sites, this is not good. Can we roll AIOS back to the previous version, or will an emergency update fix this critical issue promptly?

Hi All,

Can you confirm if the sites you had a problem on were multisites or not?

I’m looking into this issue now.

Best Wishes,

Ashley

Hi @aporter,

As for me I am only dealing with a singular site that uses Duo.

Thanks!

Ditto @aporter, single site setup here.

Mine are not multisites.

Hi All,

Thanks for all the information.

We have tracked down the conflict and fixed it, we should have a release out soon that includes this fix.

Attached is a copy of AIOS that fixes the conflict if you didn’t want to wait:

https://gofile.io/d/jCZt8I

Best Wishes,

Ashley

Can anyone on this thread confirm if the error went away?

This error message is happening on logouts too. I’ve had two distinct bug reports from WP hosting customers today who both had the same error. They are both running 5.2.7 already it looks like (the same one in your link).

Here are stacktraces from the two sites (totally different codebases and servers and hosting plans):

PHP Fatal error: Uncaught Error: Call to undefined function get_active_blog_for_user() in /wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php:678\nStack trace:\n#0 /web/wp-includes/class-wp-hook.php(324): AIOWPSecurity_User_Login->wp_logout_action_handler(0)\n#1 web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(false, Array)\n#2 web/wp-includes/plugin.php(517): WP_Hook->do_action(Array)\n#3web/wp-includes/pluggable.php(671): do_action(‘wp_logout’, 0)\n#4 /web/wp-login.php(793): wp_logout()\n#5 {main}\n thrown in /web/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php on line 678′, referer: https://…/wp-login.php?action=logout&_wpnonce=4681bd1f0e

here is the second one , again it’s logout triggering it, slightly different URL though, this one has the slug in it too.

PHP Fatal error: Uncaught Error: Call to undefined function get_active_blog_for_user() in web/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/wp-security-user-login.php:678\nStack trace:\n#0 web/wp-includes/class-wp-hook.php(324): AIOWPSecurity_User_Login->wp_logout_action_handler(0)\n#1 web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(false, Array)\n#2 web/wp-includes/plugin.php(517): WP_Hook->do_action(Array)\n#3 web/wp-includes/pluggable.php(671): do_action(‘wp_logout’, 0)\n#4web/wp-content/plugins/all-in-one-wp-security-and-firewall/other-includes/wp-security-rename-login-feature.php(712): wp_logout()\n#5 ‘, referer: https://…/loginslug/?action=logout&_wpnonce=a8357da108

both sites are running version AIO5.2.7. Neither site is a multi-site.

Examining the code i see that the problem must be that $logging_out_of_correct_site is false, even though it’s not a multi-site.

• This reply was modified 9 months, 1 week ago by damien_vancouver.

Hi @damien_vancouver,

We have tracked down the conflict in AIOS 5.2.7 and fixed it, we should have a release out soon that includes this fix.

Attached is a copy of AIOS that fixes the conflict if you didn’t want to wait:

https://gofile.io/d/jCZt8I

Let us know if you have already uploaded from the above link zip the AIOS and still the issue is there.

Regards

• This reply was modified 9 months, 1 week ago by hjogiupdraftplus.

It’s been a week and I am still not seeing an update that fixes this problem. Am I missing it somehow?

The ‘fix file’ does not exist, and we still have no update. Can you let us know what is going on?