Unable to log in with Google SSO after updating to v0.47.8

I'm using self-hosted metabase and updated from version v0.46.6.4 to v0.47.8.

As far as I can see from the logs, the update and metabase startup were successful, but when I tried to access the metabase, an error like the one shown below occurred and I was no longer able to log in using Google SSO.

Even after reverting to v0.46.6.4, the same error occurs and I am having trouble logging in.

I would appreciate it if you could let me know if you know the solution.

An excerpt of the log during installation are as follows.

$ wget https://downloads.metabase.com/v0.47.8/metabase.jar -O metabase.jar
$ sudo -E nohup java -jar metabase.jar &
$ sudo tail -f nohup.out
2023-11-29 12:57:55,579 INFO metabase.core ::
Metabase v0.47.8 (639fa5e ?)

Copyright © 2023 Metabase, Inc.

Metabase Enterprise Edition extensions are NOT PRESENT.
2023-11-29 12:57:55,595 INFO metabase.core :: Starting Metabase in STANDALONE mode
2023-11-29 12:57:55,698 INFO metabase.server :: Launching Embedded Jetty Webserver with config:
 {:port 80}

2023-11-29 12:57:55,821 INFO metabase.core :: Starting Metabase version v0.47.8 (639fa5e ?) ...
2023-11-29 12:57:55,886 INFO metabase.core :: System info:
 {"file.encoding" "UTF-8",
 "java.runtime.name" "OpenJDK Runtime Environment",
 "java.runtime.version" "11.0.2+9",
 "java.vendor" "Oracle Corporation",
 "java.vendor.url" "http://java.oracle.com/",
 "java.version" "11.0.2",
 "java.vm.name" "OpenJDK 64-Bit Server VM",
 "java.vm.version" "11.0.2+9",
 "os.name" "Linux",
 "os.version" "4.9.77-31.58.amzn1.x86_64",
 "user.language" "ja",
 "user.timezone" "Asia/Tokyo"}
2023-11-29 12:57:58,466 INFO metabase.core :: Setting up and migrating Metabase DB. Please sit tight, this may take a minute...
2023-11-29 12:57:58,470 INFO db.setup :: Verifying mysql Database Connection ...
2023-11-29 12:58:02,372 INFO db.setup :: Successfully verified MySQL 5.7.12 application database connection. ✅
2023-11-29 12:58:02,375 INFO db.setup :: Running Database Migrations...
2023-11-29 12:58:02,378 INFO db.setup :: Setting up Liquibase...
2023-11-29 12:58:02,694 INFO db.setup :: Liquibase is ready.
2023-11-29 12:58:02,701 INFO db.liquibase :: Checking if Database has unrun migrations...
2023-11-29 12:58:06,837 INFO db.liquibase :: Database has unrun migrations. Waiting for migration lock to be cleared...
2023-11-29 12:58:07,241 INFO db.liquibase :: Migration lock is cleared. Running migrations...
2023-11-29 12:58:14,204 INFO db.custom-migrations :: No forward migration for DowngradeDashboardTab
2023-11-29 12:58:18,096 INFO db.setup :: Database Migrations Current ...  ✅
2023-11-29 12:58:18,110 INFO db.data-migrations :: Running all necessary data migrations, this may take a minute.
2023-11-29 12:58:18,138 INFO db.data-migrations :: Finished running data migrations.
2023-11-29 12:58:18,141 INFO metabase.util :: Database setup took 19.7 s
2023-11-29 12:58:19,987 INFO metabase.task :: タスクスケジューラが開始されました
2023-11-29 12:58:19,991 INFO metabase.core :: メタベース初期化 COMPLETE in 54.8 s.
2023-11-29 12:58:20,094 INFO task.refresh-slack-channel-user-cache :: Starting Slack user/channel startup cache refresh...
2023-11-29 12:58:20,096 INFO integrations.slack :: Refreshing slack channels and usernames.
2023-11-29 12:58:21,263 INFO task.refresh-slack-channel-user-cache :: Slackユーザー/チャンネル起動キャッシュが605項目で更新され、1,163msかかりました。

I was able to resolve the issue by starting up a new hosting EC2 instance, connecting it to the database restored from the snapshot, and restarting the v0.46.6.4 metabase.

Not aware of any SSO issues in 47.8 or 47.9 ... Do you have a CDN on top of metabase could be something got cached