Google Login Blank Screen

I setup a new Google API Project, and oauth credential, entered the Client ID, when I click the Google login button, a blank screen opens up and nothing else happens.

What might I be missing?

Share logs and diagnostic info

Also any errors you get or screenshots can be helpful

Nothing in the log's that I can see:

[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:48:00-06:00 INFO metabase.sync.util FINISHED: Analyze data for h2 Database 1 'Sample Database' (27.5 ms)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:49:00-06:00 INFO metabase.task.sync-databases Starting sync task for Database 3.
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:49:04-06:00 DEBUG metabase.server.middleware.log GET /api/util/bug_report_details 200 1.9 ms (1 DB calls) App DB connections: 0/3 Jetty threads: 5/50 (2 idle, 0 queued) (139 total active threads) Queries in flight: 0 (0 queued)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:49:50-06:00 DEBUG metabase.server.middleware.log GET /api/user/current 200 6.6 ms (10 DB calls) App DB connections: 0/3 Jetty threads: 6/50 (1 idle, 0 queued) (141 total active threads) Queries in flight: 0 (0 queued)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:49:50-06:00 DEBUG metabase.server.middleware.log GET /api/session/properties 200 8.0 ms (6 DB calls) App DB connections: 0/3 Jetty threads: 5/50 (1 idle, 0 queued) (141 total active threads) Queries in flight: 0 (0 queued)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:49:50-06:00 DEBUG metabase.server.middleware.log GET /api/database 200 3.4 ms (3 DB calls) App DB connections: 0/3 Jetty threads: 5/50 (1 idle, 0 queued) (141 total active threads) Queries in flight: 0 (0 queued)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:02-06:00 INFO metabase.sync.util STARTING: Sync metadata for oracle Database 3 'Oracle DB3'
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:02-06:00 INFO metabase.sync.util FINISHED: step 'sync-dbms-version' for oracle Database 3 'Oracle DB3' (513.7 µs)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:02-06:00 INFO metabase.sync.util STARTING: step 'sync-dbms-version' for oracle Database 3 'Oracle DB3'
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:02-06:00 INFO metabase.sync.util STARTING: step 'sync-timezone' for oracle Database 3 'Oracle DB3'
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:02-06:00 INFO metabase.sync.util FINISHED: step 'sync-timezone' for oracle Database 3 'Oracle DB3' (2.7 ms)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:02-06:00 INFO metabase.sync.util STARTING: step 'sync-tables' for oracle Database 3 'Oracle DB3'
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:02-06:00 INFO metabase.sync.util FINISHED: step 'sync-tables' for oracle Database 3 'Oracle DB3' (8.2 ms)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:02-06:00 INFO metabase.sync.util STARTING: step 'sync-fields' for oracle Database 3 'Oracle DB3'
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:07-06:00 INFO metabase.sync.util FINISHED: step 'sync-fields' for oracle Database 3 'Oracle DB3' (5.5 s)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:07-06:00 INFO metabase.sync.util STARTING: step 'sync-fks' for oracle Database 3 'Oracle DB3'
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:08-06:00 INFO metabase.sync.util FINISHED: step 'sync-fks' for oracle Database 3 'Oracle DB3' (466.9 ms)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:08-06:00 INFO metabase.sync.util FINISHED: step 'sync-metabase-metadata' for oracle Database 3 'Oracle DB3' (559.8 µs)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:08-06:00 INFO metabase.sync.util STARTING: step 'sync-metabase-metadata' for oracle Database 3 'Oracle DB3'
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:08-06:00 INFO metabase.sync.util FINISHED: Sync metadata for oracle Database 3 'Oracle DB3' (6.0 s)
[e39eda58-b40e-4589-a8e6-72e3f14a682a] 2023-06-30T09:50:08-06:00 INFO metabase.task.sync-databases Starting sync task for Database 2.

please post diagnostic info

Oh sorry, didn't realize that was different than the logs, look right past it!

{
  "browser-info": {
    "language": "en-US",
    "platform": "MacIntel",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36",
    "vendor": "Google Inc."
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.19+7",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "https://adoptium.net/",
    "java.version": "11.0.19",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.19+7",
    "os.name": "Linux",
    "os.version": "5.15.0-76-generic",
    "user.language": "en",
    "user.timezone": "GMT"
  },
  "metabase-info": {
    "databases": [
      "oracle",
      "h2"
    ],
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "15.3 (Debian 15.3-1.pgdg120+1)"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.5.1"
      }
    },
    "run-mode": "prod",
    "version": {
      "date": "2023-06-29",
      "tag": "v0.46.6",
      "branch": "release-x.46.x",
      "hash": "1bb88f5"
    },
    "settings": {
      "report-timezone": null
    }
  }
}

Bump, anyone have any ideas?

Yes, upgrade Metabase to the latest version and wipe cookies and cache

1 Like