Upgrade your Metabase instance NOW

Subscribe to the newsletter Metabase | Business Intelligence, Dashboards, and Data Visualization

Hello Luiggi.
I updated my metabase instance to version v46.6.1 right now.
But when I try to login, my screen flicks with login screen and stays like this:

3 Likes

Same issue here, downgrading doesn't seem to solve the issue.

1 Like

Are you in Latin America and using google sign on? We're seeing some issues with Google's identity service in the region. We just posted about it here if you want to subscribe to the issue for updates: https://status.metabase.com/

3 Likes

thanks cbalusek.
Bookmarking this status page :slight_smile:

1 Like

Happening to us as well, people from Argentina, Chile and Brasil are having issues. Thanks!

2 Likes

Yes, cbalusek, we're in Argentina.
Hoping it gets fixed soon, thank you.

Thanks for the link.

Same problem here, from Bolivia

new artifacts here

v1.46.6.2

JAR: https://downloads.metabase.com/enterprise/v1.46.6.2/metabase.jar
Docker image: metabase/metabase-enterprise:v1.46.6.2

v0.46.6.2

JAR: https://downloads.metabase.com/v0.46.6.2/metabase.jar
Docker image: metabase/metabase:v0.46.6.2

v1.45.4.2

JAR: https://downloads.metabase.com/enterprise/v1.45.4.2/metabase.jar
Docker image: metabase/metabase-enterprise:v1.45.4.2

v0.45.4.2

JAR: https://downloads.metabase.com/v0.45.4.2/metabase.jar
Docker image: metabase/metabase:v0.45.4.2

1 Like

... and what do they do compared to x.46.6.1? Are they as urgent as .1?
It's on the release page on GitHub:

Bug fixes

  • Google sign-in failing for some geolocations due to Google Identity Services (GSI) client issues (#32602)

Do you have any suggestions for how would we go about finding out if our install was affected?

after upgrade a get this error:

I just pull the latest docker image

please clean your cache, and also open a new thread with logs

please write to our support email, as we won't post information publicly about attack vectors, thanks

It seems to be a problem with the Cloudflare CDN, after cleaning the cache, cookies and purging the CDN, the problem persists...

On github they tell me to remove the CDN, but I can't... I have other services operating under cloudflare :frowning:

unfortunately we can't help here then. I suggest you try testing Metabase without the CDN (we tested and it works)

Upgrading to v0.46.6.2 fixed this issue for us using Google Auth and Cloudflare, working config at:

Huge thank you to the Metabase staff for the proactive follow ups on this issue :pray:

Using docker :latest, so automatically updated.
H2 database was wiped, only saw+read release notes afterwards about this and recommendation to switch to production DB before upgrade.

Tried to restore the H2 DB in fresh install (0.46.5 or 0.46.6.2):

java -jar metabase.jar load-from-h2 /metabase-data/backup/metabase.db

but get:

2023-07-26 11:47:12,807 INFO cmd.copy :: Set up h2 source database and run migrations...
2023-07-26 11:47:12,808 INFO db.setup :: Verifying h2 Database Connection ...
2023-07-26 11:47:13,159 INFO db.setup :: Successfully verified H2 2.1.212 (2022-04-09) application database connection. ?
...
2023-07-26 11:47:14,132 INFO cmd.copy :: Set up h2 target database and run migrations...
2023-07-26 11:47:14,132 INFO db.setup :: Verifying h2 Database Connection ...
2023-07-26 11:47:14,224 INFO db.setup :: Successfully verified H2 2.1.212 (2022-04-09) application database connection. ?
...
2023-07-26 11:47:14,489 ERROR cmd.copy :: JdbcSQLSyntaxErrorException:
 Message: Column "IS_AUDIT" not found; SQL statement:
INSERT INTO metabase_database ( "DESCRIPTION", "CACHE_FIELD_VALUES_SCHEDULE", "TIMEZONE", "AUTO_RUN_QUERIES", "METADATA_SYNC_SCHEDULE", "NAME", "SETTINGS", "CAVEATS", "CREATOR_ID", "IS_FULL_SYNC", "UPDATED_AT", "CACHE_TTL", "DETAILS", "IS_SAMPLE", "ID", "IS_ON_DEMAND", "OPTIONS", "ENGINE", "INITIAL_SYNC_STATUS", "IS_AUDIT", "DBMS_VERSION", "REFINGERPRINT", "CREATED_AT", "POINTS_OF_INTEREST" ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) [42122-212]
 SQLState: 42S22
 Error Code: 42122

How to restore H2 DB in latest or previous Docker version?

If your h2 db was inside the container, you lost it. Also, don’t use mutable docker tags (like “latest”), you’ll believe you’re in the latest version when you’re not

Understood the data is gone. But is there a way to get it back from the backup I have?