Hi @liajds
Is the /wp-login.php available on your site? If it is, and you receive the 404 page at the Google provider only, then your problem can happen because of some server setting, maybe a firewall that does not allow passing http/https links in the URL:
https://nextendweb.com/nextend-social-login-docs/google-403-and-404-errors/
Google provider needs these for a successful authentication, so I suggest getting in touch with your host to get this solved.
From the reports we got, at most customers the problem was caused by ModSecurity, specifically rules 11085 and 11089 which were restricting access. Removing these by their server hosts solved the problem for them.
Thread Starter
liajds
(@liajds)
I asked my host and he checked an said that those rules are not present at my server.
What else can it be?
Plugin Support
Gabor
(@nextendweb_gabor)
Hi @liajds!
In this case you might have a plugin (or your theme), which overwrites the redirection of your pages. Please do a theme/plugin conflict test as you see here, at another plugin of ours:
https://smartslider.helpscoutdocs.com/article/2006-how-to-use-health-check-troubleshooting-plugin
Check out if only our plugin is activated, can you verify Google? If you still can’t, that will tell us it is a server setting caused issue. But if you can, then try to turn back on your plugins one-by-one (or a couple together, until you can narrow down the issue). If you would find out which plugin causes the problem, please tell us its name and we will take a look at it!
If it looks like a server issue, please send us a link to your website:
https://nextendweb.com/contact-us/nextend-social-login-support/?topic=Verfication-404&version=Free&send-screenshot=No
Thread Starter
liajds
(@liajds)
Hi, I opened a ticket as per your instructions but got no response yet.
Did you receive it or should I open a new ticket?
Thread Starter
liajds
(@liajds)
Sorry my bad,
I was checking the wrong email address.
yuo did respond in time!
thank you!
Plugin Support
Laszlo
(@laszloszalvak)
Hi @liajds
I am glad you managed to find our reply. Meanwhile I also replied to your most recent message. Could you check it please?
Just in case other users also see such problems, I share the cause of the problem, maybe it helps for others, too.
Some firewalls automatically black list some strings, e.g.: .profile
The problem is that, Google users this string in one of its scopes, too:
https://www.googleapis.com/auth/userinfo.profile
so the server won’t be able to serve the request.
To fix these kind of problems, users need to get in touch with their host and asking them about this limitation. They can usually whitelist the entire expression or whitelist it only for the context.
Best regards,
Laszlo.
