dosubot[bot] commented on issue #34773:
URL: https://github.com/apache/superset/issues/34773#issuecomment-3206615392

   <!-- Answer -->
   There are known issues with Superset 5.0.0 and earlier versions when 
deploying under a subpath (using `SUPERSET_APP_ROOT` or `APPLICATION_ROOT`), 
especially with Docker and nginx. The symptoms you describe—redirects to 
incorrect paths, missing subpath in API calls, and broken links—match these 
issues. Recent fixes were merged after 5.0.0 that address frontend and API 
routing bugs related to the application root, including proper handling of 
login redirects and API endpoints when a subpath is configured. These fixes are 
not present in 5.0.0, so you are likely hitting these known bugs [[PR 
34395](https://github.com/apache/superset/pull/34395)] [[PR 
34680](https://github.com/apache/superset/pull/34680)].
   
   To reliably run Superset under a subpath, you will need to upgrade to a 
version that includes these fixes (anything after mid-August 2025). If you must 
stay on 5.0.0, there is no robust workaround—subpath support is incomplete and 
buggy in that release.
   
   For reference, the recommended config is to set both `APPLICATION_ROOT` and 
`STATIC_ASSETS_PREFIX` to your subpath (e.g., `/analytics`), and use 
`ENABLE_PROXY_FIX = True`. In nginx, use `proxy_set_header X-Forwarded-Prefix 
/analytics/` instead of `X-Script-Name` 
[[example](https://github.com/apache/superset/issues/33226)]. But even with 
these settings, 5.0.0 will not fully work under a subpath due to the frontend 
bugs described above.
   
   Upgrading to a newer Superset version is the only reliable solution for 
subpath deployments.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/f7694d4d-5622-4c37-84a7-36ff201cce67?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/f7694d4d-5622-4c37-84a7-36ff201cce67?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/f7694d4d-5622-4c37-84a7-36ff201cce67?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/f7694d4d-5622-4c37-84a7-36ff201cce67?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/f7694d4d-5622-4c37-84a7-36ff201cce67?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/f7694d4d-5622-4c37-84a7-36ff201cce67?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/f7694d4d-5622-4c37-84a7-36ff201cce67?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
 b)&nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34773)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to