Bug description
Hi Team ,
I have installed version 5.0.0 and When I access URL it is redirecting me to login page and after that I am seeing blank page
.
Here are the logs collected from the debug:
[Intervention] Images loaded lazily and replaced with placeholders. Load events are deferred. See https://go.microsoft.com/fwlink/?linkid=2048113 login/:251 GET https://superset-blue.qacore.vite/static/assets/images/superset-logo-horiz.png 503 (Service Unavailable) favicon.png:1 GET https://superset-blue.qacore.vite/static/assets/images/favicon.png 503 (Service Unavailable)
Screenshots/recordings
Superset version
5.0.0
Python version
3.11
Node version
18 or greater
Browser
Chrome
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
The blank page after login and the 503 errors for static assets (like the logo and favicon) indicate that Superset's frontend assets are not being served correctly. In production, Superset relies on a web server (typically Nginx) or a dedicated static file service to serve these assets—Flask does not handle this by default. If these assets are missing or the web server is misconfigured, the UI will fail to load, resulting in a blank page and 503 errors for static files (reference, reference).
Common causes include: the frontend assets were not built or copied into the final deployment, the Nginx (or reverse proxy) configuration is not correctly forwarding or serving the /static/assets path, or the static asset build process is still running in the background (especially in Docker setups).
To resolve this:
- If using Docker, make sure the frontend asset build process is complete before accessing the UI. Check container logs to confirm asset build completion.
- If using a custom image or non-standard deployment, ensure that the frontend assets are built (using npm ci and npm run build in the superset-frontend directory) and copied into the correct location before runtime.
- Verify your Nginx or reverse proxy configuration is correctly serving /static/assets from the right directory or proxying to the correct service (reference).
- Double-check that the files like superset-logo-horiz.png and favicon.png exist in the expected static assets directory.
If these steps don't resolve the issue, check your browser console and Nginx/backend logs for additional errors that might point to a misconfiguration or missing files.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: devikaaaa33
Thank you dosu,