Closed thelinuxer closed 4 years ago
This issue looks like a support question. We try to answer these reasonably fast, but in case you are looking for faster resolution, please consider purchasing support subscription and make Weblate stronger.
It might be related to https://github.com/WeblateOrg/weblate/issues/4565. Can you please check the network requests in your browser if that includes correct callback URL while authenticating?
@nijel I checked the browser's network tab and found out there's a call that returns 401 status code.
{
"POST":{
"scheme":"https",
"host":"play.google.com",
"filename":"/log",
"query":{"format":"json","hasfast":"true"},
"remote":{"Address":"216.58.205.206:443"}
}
}
play.google.com doesn't sound like the relevant request, the authentication should go to accounts.google.com
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the issue
I installed weblate using docker on a kubernetes cluster a while back and configured it to be able to login with Google and it was working fine. Last night I upgraded to version 4.2.2, password authentication is working fine but Google login is not working and it keeps returning user message whenever I try to login saying " The server does not allow authentication." I configured the following environment variables:
To Reproduce
I am not sure I have a scenario since I am not sure if it's a bug or a misconfiguration.
Server configuration and status weblate list_versions
Weblate deploy checks weblate check --deploy ?: (weblate.I021) Error collection is not set up, it is highly recommended for production use HINT: https://docs.weblate.org/en/weblate-4.2.2/admin/install.html#collecting-errors ?: (weblate.I028) Backups are not configured, it is highly recommended for production use HINT: https://docs.weblate.org/en/weblate-4.2.2/admin/backup.html