Why my Superset 5.0.0 stuck in homepage after logout and login again? #34684
Replies: 1 comment
-
Superset 5.0.0 uses a single-page app (SPA) frontend that caches user and session data after login. When you log out and log in again, the frontend may not fully refresh its state, so you can get stuck on the homepage with stale data. Doing a full browser reload (Ctrl+F5) after login usually fixes this, because it forces the app to fetch fresh user info from the backend. Try clearing your browser cache/cookies and reloading the page after login. If the problem persists, check your browser console and Superset backend logs for errors during the login/logout cycle—session or CSRF token issues can also cause this behavior. If you see any errors, share them here and I can help interpret them. This caching issue is more common in Superset 5.x and later due to the SPA architecture and how bootstrap data is handled. If you want to dig deeper, you can review your session settings in To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why my Superset 5.0.0 stuck in homepage after logout and login again?
When i dokcer compose again and do login logout and login again get the same problem.
@dosu
Beta Was this translation helpful? Give feedback.
All reactions