Google login suddenly stopped working

  • Resolved itsabhist

    (@itsabhist)


    1 year, 10 months ago

    Hi
    Suddenly Google login stopped working
    And when trying to login it redirecting to 404 page .

    In debug mode showing

    

Debug: Google
Network connection successful: https://accounts.google.com/o/oauth2/token

*   Trying 2404:6800:4003:c02::54:443...
* Connected to accounts.google.com (2404:6800:4003:c02::54) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /localhost/public_html/wp-includes/certificates/ca-bundle.crt
  CApath: none
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=accounts.google.com
*  start date: Jun  6 09:40:55 2022 GMT
*  expire date: Aug 29 09:40:54 2022 GMT
*  subjectAltName: host "accounts.google.com" matched cert's "accounts.google.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x12033c0)
> POST /o/oauth2/token HTTP/2
Host: accounts.google.com
accept: */*
content-length: 0
content-type: application/x-www-form-urlencoded

* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 400 
< content-type: application/json; charset=utf-8
< vary: X-Origin
< vary: Referer
< vary: Origin,Accept-Encoding
< date: Sun, 26 Jun 2022 04:20:31 GMT
< server: scaffolding on HTTPServer2
< cache-control: private
< x-xss-protection: 0
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
< accept-ranges: none
< 
* Connection #0 to host accounts.google.com left intact
{
  "error": "unsupported_grant_type",
  "error_description": "Invalid grant_type: "
}
Viewing 3 replies - 1 through 3 (of 3 total)
  • Ramona

    (@nextend_ramona)

    1 year, 10 months ago

    Hi @itsabhist

    The debug information for the specific providers was only made to check if your site is able to connect to the given provider’s. Based on this log, the connection is successful.

    If you visit your /wp-login.php by adding Google’s .profile scope, are you able to load the page? So, basically, you should go to:
    https://yoursite.com/wp-login.php?test=.profile
    then remove the ˙e´from profile, like so:
    https://yoursite.com/wp-login.php?test=.profil

    If the first one doesn’t load, but the second does, then the problem will be that there’s some kind of firewall ( probably ModSecurity ) that blocks requests when they contain certain strings, more specifically “.profile”:
    https://nextendweb.com/nextend-social-login-docs/google-403-and-404-errors/

    With ModSecurity this is actually a very common problem, as they have this string on their black list, however one of the scopes that Google use:
    https://www.googleapis.com/auth/userinfo.profile
    also contains that “.profile” string, which means the OAuth requests of Google will be blocked.

    So to fix the problem, you should get in touch with your host and ask them to disable the rule that causes the problem. They have an error log that contains all kinds of error messages, including the ones triggered by the firewall. And that should contain the rule ID that causes this 403/404 error.

    If the ´.profile´ scoped page loads, can you share the link of the page where we could check the problem? If you don’t want to put your site URL to a public forum, you can share it privately here:
    https://nextendweb.com/contact-us/nextend-social-login-support/?ref=https://wordpress.org/support/topic/google-login-suddenly-stopped-working/

    Thread Starter itsabhist

    (@itsabhist)

    1 year, 10 months ago

    During troubleshooting it observed that
    My login is working fine for existing user
    But when new user register
    It redirecting to localhost/register/?loginSocial=googlel

    Instead of
    localhost/wp-login.php?loginSocial=googlel

    And new registration not working

    Please help

    Plugin Support Laszlo

    (@laszloszalvak)

    1 year, 10 months ago

    Hi @itsabhist

    In this case you probably ask some extra information before the registration ( e.g. you display the Terms and conditions ) so the user gets into our register flow. By default we handle this over the WordPress default registration page which should be /wp-login.php page, as well. In your case, that seems to be handled over the mentioned /register page by a third party and that could break our register flow.

    So what I would suggest you is to use the following:

    If you still see problems even after that, just let us know!

    Best regards,
    Laszlo.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Google login suddenly stopped working’ is closed to new replies.