There was an issue signing in with Google. No info in logs or other disscus

After today all users(almost everyone) was not able to login trought Google. Only showing above message:
There was an issue signing in with Google. Please contact an administrator We aren`t able to change they passwords because Google Log in, Metabase logs show's nothing more than Unauthorized. This problem seems to already been treated by other users but are back today. Currently running latest version v0.44.5.

More infos above:

  "browser-info": {
    "language": "en-US",
    "platform": "Linux x86_64",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36",
    "vendor": "Google Inc."
  "system-info": {
    "file.encoding": "UTF-8",
    "": "OpenJDK Runtime Environment",
    "java.runtime.version": "",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "",
    "java.version": "",
    "": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "",
    "": "Linux",
    "os.version": "4.14.291-218.527.amzn2.x86_64",
    "user.language": "en",
    "user.timezone": "GMT"
  "metabase-info": {
    "databases": [
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "13.7"
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.5.0"
    "run-mode": "prod",
    "version": {
      "date": "2022-10-17",
      "tag": "v0.44.5",
      "branch": "release-x.44.x",
      "hash": "29fab4d"
    "settings": {
      "report-timezone": null
[1d6d4296-8927-4134-9bff-fe998a9cc727] 2022-10-31T21:32:58-03:00 WARN metabase.server.middleware.log GET /api/util/bug_report_details 403 1.1 ms (0 DB calls) 
"You don't have permissions to do that."

[9bf9c589-6fae-42a3-b766-da2b5c8acf5c] 2022-10-31T21:33:05-03:00 DEBUG metabase.server.middleware.log GET /api/task 401 149.7 µs (0 DB calls) 

There seems to be an issue where Google changed a parameter in their OAuth configuration without telling anyone. Also, this parameter has not been deployed to all regions, so some regions are affected while others aren't. Please check Google authentication failed · Issue #26184 · metabase/metabase · GitHub to follow the progress on the matter. We'll try to come up with a solution, but for now what we can see is that Google will need to revert their changes ASAP or officially communicate these changes so the libraries that handle Google OAuth can follow

1 Like

Thanks a lot for anserwing @Luiggi! Waiting for the official fix.

We just pushed the official JAR and container images, so if you run Metabase self hosted, you will be able to upgrade to the latest release where this is fixed