rtCamp / login-with-google

Minimal plugin which allows WordPress user to login with google.
https://wordpress.org/plugins/login-with-google/
GNU General Public License v2.0
64 stars 19 forks source link

403 error when login with google and normal log out #62

Closed rahul286 closed 3 years ago

rahul286 commented 3 years ago

@mrrobot47 when I try to login via the google login button I am getting nginx 403

  1. You can go to https://hw.rsites.in/wp-login.php
  2. Try google login. It gives 403
  3. Go to https://hw.rsites.in/wp-admin and you will be in
  4. Try log out from WP top-right side profile menu, and 403 again

If this is not related to server config, then you may assign this to somebody from @rtCamp/developers

kirtangajjar commented 3 years ago

@rahul286 Can you check now?

Looks like the issue was in the server config. We put 1 req/s rate limit on wp-login.php and while logging out, two requests were sent to wp-login.php simultaneously, and secod one was causing 403.

Screenshot from 2020-12-18 13-37-36

I was getting 403 on logout(but never got during login). After changing rate limit to 2 req/s, I'm not getting 403.

rahul286 commented 3 years ago

@mrrobot47 did we remove plugin

The plugin login-with-google/wp-google-login.php has been deactivated due to an error: Plugin file does not exist.

Please add it from directory and configure it sitewide

mrrobot47 commented 3 years ago

@rahul286 Did not remove the plugin. It was not active on network. Network activated now :white_check_mark:

rahul286 commented 3 years ago

Still 403 https://hw.rsites.in/wp-login.php?loggedout=true&wp_lang=en_US

403_Forbidden

mrrobot47 commented 3 years ago

~On which site did you get this error?~ Checking

mrrobot47 commented 3 years ago

@rahul286 please try now. The rate limitting was set at 1 request per 6 second (10r/m). Eased it down to 1r/s (EasyEngine's default setting). Please check now.

rahul286 commented 3 years ago

rsites_in

mrrobot47 commented 3 years ago

Did you get this just before my last message? Then probably Nginx restart caused it. Please let me know if you get this again.

rahul286 commented 3 years ago

Working now.