Apache Superset Application root configuration doesn't work

Bug description

I tried to configure superset to work under a specific path url like the documentation : https://superset.apache.org/docs/configuration/configuring-superset/#configuring-the-application-root//

But it no works. I specify that my superset app works without application root configuration. I'm using docker with docker-compose-image-tag to start superset and I have nginx server to redirect url to superset app.

I set environment variables in .env-local like this :

SUPERSET_APP_ROOT = /analytics
ENABLE_PROXY_FIX = True

My nginx config for superset :

server {
    listen [::]:443 ssl;
    listen 443 ssl;

    server_name mydomain.fr

    include conf.d/ssl.conf;

    location /analytics/ {
        include conf.d/location.conf;
        proxy_set_header X-Script-Name /analytics;
        proxy_pass http://localhost:8088/;
    }

    access_log /var/log/nginx/superset/access.log;
    error_log /var/log/nginx/superset/error.log;
}

My location.conf :

proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header Connection keep-alive;
proxy_set_header Upgrade $http_upgrade;
proxy_cache_bypass $http_upgrade;

If I open "https://mydomain.fr/analytics" I'm redirected to https://mydomain.fr/superset/welcome with a 404 error. If I open "https://mydomain.fr/analytics/superset/welcome/" I have the menu bar, but nothing else, and inside the console, I see an error about a query on "https://mydomain.fr/api" without "analytics" path, and all the links in the menu don't have the path either.

I saw there is trouble with application root feature, is that supposed to work ? and on which version ?

Thanks

Screenshots/recordings

No response

Superset version

5.0.0

Python version

3.9

Node version

16

Browser

Firefox

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]

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] [PR 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]. 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.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

Comment From: sadpandajoe

@dosu does this work currently in master?

Comment From: dosubot[bot]

Yes, subpath (application root) support works in master, with recent fixes merged to address frontend and API routing issues. The backend and frontend now consistently respect the SUPERSET_APP_ROOT/APPLICATION_ROOT setting for URLs, static assets, and most internal links, and tests confirm correct handling of the app root in both layers PR #34680 code.

However, there are still some known gaps: for example, OAuth login links and a few API endpoints may not yet prepend the app root, so full coverage is still considered BETA and may require further fixes issue discussion. For most use cases, deploying under a subpath now works as expected in master, but thorough testing in your environment is recommended.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}