Hello. I'm having a problem with the Google Login Plugin and I still can't determine the reason. Everything was working perfectly, and from one day to the next this problem started. I've been searching all over Google and I can't fix it.



Error message:
"There was problem getting access token from google, login has failed. Following errors were returned: Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."

I tried regenerating the token from the Google Cloud Console and the problem persists.

Can anyone know the reason for this? I appreciate any suggestion in advance.

@Emidelro
This looks like issue with your app setup or incorrect credentials are put into plugin configuration.

Hello, thanks for the answer.
That was the first thing I thought. But I checked the credentials and they are correct. I also tried generating new credentials, but the problem continues.
Everything was working perfectly, and from one moment to another the failure began. But I have not changed anything regarding the plugin code or credentials.

@Emidelro
That would need to be checked by google support as well.
I did test right now and everything is working OK.

Yes, I will do that. Thank you very much for the answers.

Greetings.

Was it solved? 

Not yet, I've exhausted all possibilities. I'll see if I can get support from Google, as the problem is quite strange (credentials are correct).

Query: if I uninstall the plugin (and then reinstall it), will this procedure also delete the data from the DB?

uninstallation should drop also parameters (settings) of plugin from database.

Hi Emidelro, i have the same problem, did you find a solution?

Thank you

Check this. Problem is same, you have not configured Keys properly.
https://www.codexworld.com/login-with-google-api-using-php/

Thanks for the reply.
I followed the step by step guide, but it didn't solve the problem.
Token is correct. Could this be a friendly url problem?

Thanks

How you followed?
Here are some details