FB Login Not working
-
Hi There,
My Facebook login is not working anymore. Previously it is working just fine. Google button working perfectly could you please help me. Thank you
Regards
AfizanLink to video showing the problem https://1drv.ms/u/s!AlDEB9smb3Mkj_9VsWD8DGNo6yAZXw?e=OaYIRx
-
Hi @afizan75
I checked both the Facebook and the Google login on your site, and actually I can see the same problem occur with Google too, just you need to select an account in the account selector screen.
Anyways I can see that, the login/registration fails because of an “Authentication failed” error. This doesn’t tell you what is the problem exactly, but if you would enable the “Debug mode” at our Global Settings > General tab:
Then we could probably write out the error message in the popup.
Once it is done, please let me know and I will take another look.
Best regards,
Laszlo.Hi Laszlo,
Thank you so much for your quick response. Below are the values return when I run debug
**Facebook**
* Trying 2a03:2880:f00c:13:face:b00c:0:2:443…
* Connected to graph.facebook.com (2a03:2880:f00c:13:face:b00c:0:2) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /home/u672545931/domains/zanilla.com.my/public_html/wp-includes/certificates/ca-bundle.crt
CApath: none
* SSL connection using TLSv1.3 / TLS_CHACHA20_POLY1305_SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=California; L=Menlo Park; O=Facebook, Inc.; CN=*.facebook.com
* start date: Dec 22 00:00:00 2020 GMT
* expire date: Mar 21 23:59:59 2021 GMT
* subjectAltName: host “graph.facebook.com” matched cert’s “*.facebook.com”
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* 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 0x260d2a0)
> POST /v7.0/oauth/access_token HTTP/2
Host: graph.facebook.com
accept: */*
content-length: 0
content-type: application/x-www-form-urlencoded* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 400
< content-type: application/json; charset=UTF-8
< facebook-api-version: v7.0
< x-fb-request-id: AmKudHEoIMAHrqgeTGxubfE
< strict-transport-security: max-age=15552000; preload
< x-fb-trace-id: Cm04JivIn/O
< x-fb-rev: 1003284553
< cache-control: no-store
< pragma: no-cache
< access-control-allow-origin: *
< expires: Sat, 01 Jan 2000 00:00:00 GMT
< www-authenticate: OAuth “Facebook Platform” “invalid_request” “Missing redirect_uri parameter.”
< x-fb-debug: Dmi3bQoNR4cyY+Am6R8p5HKE4nsd38fHrLw+LaCutm5tpIBfrnd0J+gvHdoXJ/o5r5HaZ6uniS7teKwY0nfsVg==
< content-length: 129
< date: Tue, 09 Feb 2021 17:25:51 GMT
< alt-svc: h3-29=”:443″; ma=3600,h3-27=”:443″; ma=3600
<
* Connection #0 to host graph.facebook.com left intact
{“error”:{“message”:”Missing redirect_uri parameter.”,”type”:”OAuthException”,”code”:191,”fbtrace_id”:”AmKudHEoIMAHrqgeTGxubfE”}}**Google**
* Trying 2404:6800:4003:c04::54:443…
* Connected to accounts.google.com (2404:6800:4003:c04::54) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /home/u672545931/domains/zanilla.com.my/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: C=US; ST=California; L=Mountain View; O=Google LLC; CN=accounts.google.com
* start date: Jan 19 08:04:14 2021 GMT
* expire date: Apr 13 08:04:13 2021 GMT
* subjectAltName: host “accounts.google.com” matched cert’s “accounts.google.com”
* issuer: C=US; O=Google Trust Services; CN=GTS CA 1O1
* 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 0x2727cf0)
> 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: Tue, 09 Feb 2021 17:28:39 GMT
< server: scaffolding on HTTPServer2
< cache-control: private
< x-xss-protection: 0
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< alt-svc: h3-29=”:443″; ma=2592000,h3-T051=”: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: ”
}Once again thank you
Regards
AfizanHi @afizan75
Sorry, I didn’t mean debug information of the providers that you receive when you press the “Test X connection” buttons in the Debug section.
But what I actually meant is the “Debug” setting, what you can find at our Global Settings > General tab. See here:
You should enable this setting, and then when you connect with a provider it will most likely write out an error message in the popup, instead of closing it automatically.
Hi @laszloszalvak,
I turn on the debug mode and here is the error for both Google and Facebook “Error: Unable to validate CSRF state”. Thank you
Regards
AfizanHi @afizan75
The “Error: Unable to validate CSRF state” usually pops up because of some server related cookie caching. You can learn more about the problem and the possible solutions in this documentation:
https://nextendweb.com/nextend-social-login-docs/common-error-messages/#csrfIt is not the server. It is my caching plugin. When I turn off the caching plugin everything work just fine. Thank you for your help. I will ask the caching plugin developer on how to solve this issue. Once again thank you very much for your help.
Regards
Afizan
The topic ‘FB Login Not working’ is closed to new replies.