Google authentication failed

Hi @marivsh

Thanks for contacting us!

Please enable the “Debug mode” on our General tab:

• https://nextendweb.com/nextend-social-login-docs/global-settings/

then try the login with Google again and that will probably write out an error message that prevents the login. That could help us in figuring out what is the problem exactly.

Best regards,
Laszlo.

Hi @laszloszalvak , thanks for quick replay.

So the error stands: Unable to validate CSRF state

I see in doc info about that, so will try to fix it, but if you have additional info for me, just let me know, what else I can do ??

Hi @marivsh

This error usually occurs if:

• we are not able to set the cookie that we use for the authentication. By default it is called “SESSnsl”
• or if we are not able to get the necessary information from the site transients, that is necessary to avoid CSRF attacks

I checked the login with Google on your site and I can see that we are able to set the cookie. So most likely you have a third party plugin that messes up the site transients. A typical example is when you have an Object Cache installed on your site, but it wasn’t configured properly, so plugins which are trying to get data from the site transients will fail, as no data will be returned.

If you have an Object Cache, you should try disabling it and see if it resolves the problem. If it does, then before you enable it, you need to make sure you have all the prerequisites to use Object cache.

E.g. from our experiences usually those people experience this problem who has the Object cache enabled, but:

• they didn’t have the PHP extension installed
• or the object cache server wasn’t started

Some plugins with Object cache feature usually have a status page, where they display these issues and those need to be fixed if you want to use object cache.

• This reply was modified 1 year, 11 months ago by Laszlo.

@laszloszalvak

I disable the Object cache in W3TC plugin settings, but error still occure. Any idea what can I do more?

@marivsh

The object cache can load over “Must use” and “Drop-Ins” plugins, too. So you should go to your plugins list, and check if you see those tabs. In this article you can find some screenshots that might help you in finding these tabs:

• https://www.narga.net/beginners-guide-wordpress-must-use-drop-ins-plugins/

If you see any cache being loaded this way, you should try disabling them. ( Note: Must use and Drop Ins plugins can only be disabled if you move the corresponding file out of the /wp-content folder.) Then check if that makes any difference.

In that case if you don’t have those tabs, but the problem still occurs, then you should try a complete plugin / theme conflict test. So basically you should:

• disable all plugins on your site except Nextend Social Login
• change your theme to a WordPress default one, like Twenty Twenty-One.
• then check the login again ( on the /wp-login.php page you will find the Google button )
• if the problem no longer occurs, you should start enabling the plugins one by one or in small groups then check the login again each time. Once the problem starts occurring again, you managed to find the plugin that causes the problem.

Hi @laszloszalvak ??

After deleting the cache plugin drop-ins, everything now work ok ?? Thanks for your help, great approach to the problem from your side ??

Best regards

Hi @marivsh

Then most likely the problem was that you didn’t have the prerequisites to run the object cache on your site.

As I mentioned above, most object cache usually have a status page. So if you would like to use Object Cache in the future, you should probably check their status page, as it might tell you what additional changes you have to make.

Anyways, I am glad you managed to fix it! ??