Can't see sidebar, just "An error occurred" v0.50

1

I'm self-hosting Metabase v0.50. I can create new questions and query the database etc, but not create new collections or models and the sidebar only shows "An error occurred".

Metabase is deployed via docker and connected to a Postgres 16.3 database.

Only issue I see in the logs is

2024-06-19 14:24:05,581 ERROR api.session :: Authentication endpoint error
clojure.lang.ExceptionInfo: Password did not match stored password. {:status-code 401, :errors {:password #metabase.util.i18n.UserLocalizedString{:format-string "did not match stored password", :args [], :pluralization-opts {}}}}
	at metabase.api.session$do_http_401_on_error.invokeStatic(session.clj:174)
	at metabase.api.session$do_http_401_on_error.invoke(session.clj:170)
	at metabase.api.session$fn__102455.invokeStatic(session.clj:195)
	at metabase.api.session$fn__102455.invoke(session.clj:182)
	at compojure.core$wrap_response$fn__52891.invoke(core.clj:160)
	at compojure.core$wrap_route_middleware$fn__52875.invoke(core.clj:132)
	at compojure.core$wrap_route_info$fn__52880.invoke(core.clj:139)
	at compojure.core$wrap_route_matches$fn__52884.invoke(core.clj:151)
	at clojure.lang.Var.invoke(Var.java:393)
	at compojure.core$routes$fn__52903$f__52904.invoke(core.clj:198)
	at compojure.core$routes$fn__52903.invoke(core.clj:200)
	at clojure.lang.AFn.applyToHelper(AFn.java:160)
	at clojure.lang.AFn.applyTo(AFn.java:144)

and later

2024-06-19 14:24:26,041 DEBUG middleware.log :: GET /api/user/current 401 269.2 µs (0 DB calls) {:metabase-user-id nil} 
"Unauthenticated"

which is strange, because the login still worked, and I see all the users I've invited so far. How can I debug this further? I did not see this error while testing the app locally with a jar.

2

this is weird, you say that you can log in fine but the sidebar does not load and this error is on the logs? are you sure this is the error and you're not sending other log lines?

3

I am facing the same issue. Were you able to fix it? Also, the sidebar is visible when accessing via Public IP as it's hosted on EC2 but doesn't show up when accessing via the domain name which we have setup using AWS

4

The main culprit was the uBlock origin extension