how to run superset with subpath using traefik

[sino1641]

Hi Community,
I am new to superset and would like to test it in my k8s cluster but facing trouble on expose it on my domain with subpath.
Searching both issues and discussions, I have already added ENABLE_PROXY_FIX and SUPERSET_WEBSERVER_BASE_URL in config.py but no luck.

Here is my traefik config:

apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: superset
  namespace: superset
spec:
  entryPoints:
    - websecure
  routes:
    - kind: Rule
      match: Host(`my.domain`) && PathPrefix(`/superset`)
      middlewares:
        - name: superset-stripprefix
      services:
        - name: superset2024
          port: 8088
    - kind: Rule
      match: Host(`my.domain`) && PathPrefix(`/static`)
      services:
        - name: superset-2024
          port: 8088
---

apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: superset-stripprefix
  namespace: superset
spec:
  stripPrefix:
    prefixes:
      - /superset
    forceSlash: false

When I visit my.domain/superset, it will redirect to /superset/welcome but it is a 404 page.

The picture is from my.domain/static so I also added a middleware to get it shown but obviously it doesn't solve the problem.
Return home is <a href="/" class="button">Back to home</a> which also indicates BASE_URL is not set properly.

Do you guys have any idea or if you have tried setting up with traefik as well? Sincerely thanks for any suggestions!

[dosubot[bot]]

Hey there, @sino1641! 👋 I'm here to help you with your Superset and Traefik configuration. I'm a bot designed to assist with bugs, questions, and contributions. Let's tackle this challenge together!

To run Superset with a subpath using Traefik, you need to ensure that both Superset and Traefik are correctly configured to handle the subpath. Here are some steps and considerations:

1. Superset Configuration:

   • Ensure that ENABLE_PROXY_FIX is set to True in your superset_config.py to handle the X-Forwarded headers correctly.
   • Set SUPERSET_WEBSERVER_BASE_URL to include the subpath, e.g., SUPERSET_WEBSERVER_BASE_URL = "https://my.domain/superset".

2. Traefik Configuration:

   • Your Traefik configuration seems mostly correct, but ensure that the stripPrefix middleware is correctly applied to all routes that need it. This middleware removes the /superset prefix before forwarding the request to Superset.
   • Ensure that the PathPrefix rule in your IngressRoute matches the subpath you are using.

3. Static Files:

   • Ensure that static files are correctly served. You might need to adjust your Traefik configuration to handle static files if they are served from a different path.

4. Frontend Routing:

   • Superset's frontend routes need to be aware of the subpath. Ensure that all routes in Superset are prefixed with /superset.

5. Testing:

   • After making these changes, clear your browser cache or try accessing the site in an incognito window to ensure that cached redirects or resources are not causing issues.

By ensuring these configurations are correctly set, Superset should be able to run on a subpath with Traefik as a reverse proxy. If issues persist, double-check the logs for any errors that might provide more insight into the problem.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[sino1641]

Yes, I also consulted GPT but nothing works.
Hope clever guys watching the post like you could answer my question 🙏

[ziggekatten]

Not the answer you would like, but we spent weeks on trying to get this to work, but there is simply to many places in the code with non relative uri path's to deal with. Add an dns entry for yor traefik with an host rule instead. It's not worth the effort, as any update will break it again

[sino1641]

Not the answer you would like, but we spent weeks on trying to get this to work, but there is simply to many places in the code with non relative uri path's to deal with. Add an dns entry for yor traefik with an host rule instead. It's not worth the effort, as any update will break it again

Thanks bro. Yes it seems like a tough question to deal with it.