Bug description
in the doc url Configuring the application root Please be advised that this feature is in BETA.
Superset supports running the application under a non-root path. The root path prefix can be specified in one of two ways:
Setting the SUPERSET_APP_ROOT environment variable to the desired prefix. Customizing the Flask entrypoint by passing the superset_app_root variable. Note, the prefix should start with a /.
i set it in bitnami/superset ,but it is not work!!! like this i want root url is http://ip:port/superset ,i want it deploy on k8s.
Screenshots/recordings
No response
Superset version
5.0.0
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] 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]
Hi @worldofchu! I'm Dosu and I’m helping the superset team.
Running Superset 5.0.0 under a subpath like /superset in Kubernetes (with Bitnami) is not fully supported due to known bugs and hardcoded paths in that version. Even with the correct settings, you will likely encounter broken redirects, missing prefixes in API calls, and static asset issues. These problems are fixed only in versions released after mid-August 2025.
If you still want to try, set SUPERSET_APP_ROOT, APPLICATION_ROOT, and STATIC_ASSETS_PREFIX to /superset in both your environment variables and superset_config.py, and set ENABLE_PROXY_FIX = True. In your Kubernetes deployment, use the Bitnami Helm chart's extraEnv or extraEnvRaw to inject SUPERSET_APP_ROOT. Your Nginx (or ingress) config should proxy /superset/ to the backend and set proxy_set_header X-Forwarded-Prefix /superset/ (not X-Script-Name) for best compatibility. Example config and more details: issue comment.
However, even with all this, 5.0.0 will not fully work under a subpath due to frontend bugs. The only robust solution is to upgrade to a newer Superset version that includes the recent fixes (PR 34395, PR 34680) source.
If you must stay on 5.0.0, there is no complete workaround—expect broken links and features. For reference, see the Bitnami Helm chart docs for how to set extra environment variables.
More background and troubleshooting:
- Subpath deployment limitations
- Known bugs and upgrade advice
- Feature status and config tips
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: worldofchu
Thanks ！ I don't want to bind to version 5.0. I want to use the newly deployed one. When can we expect a new version to support pathbase？
Comment From: dosubot[bot]
Full pathbase (subpath) support is expected in the next major Superset release, version 6, which is planned for the second half of 2025. The key fixes for subpath deployment were merged in August 2025 (PR #34395, PR #34680), so any release after that date should include them. You can track the release schedule and check the changelog for confirmation of these fixes and other features here.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
Comment From: rusackas
While I haven't tested this feature personally, 6.0.0rc1 is available for testing now. We'll be releasing a new release candidate soon, so if you find any issues there, let us know!