GitHub user jc4250 added a comment to the discussion: Getting 404 error on 
welcome page

@dosu I have done the following changes after this I am able to see login page
at domain/superset/login/?next=%2Fsuperset%2Fwelcome%2F but once I do login 
request is routed to domain/superset/welcome 
and getting 404 error post login.

And if I update the url manually /superset/superset/welcome then I am able to 
see dashboard page

1) I have changed the superset_config.py
```
import os

APPLICATION_ROOT = "/superset"
STATIC_ASSETS_PREFIX = '/superset'

ENABLE_PROXY_FIX = True
LOG_LEVEL = "DEBUG"

PROXY_FIX_CONFIG = {"x_for": 1, "x_proto": 1, "x_host": 1, "x_port": 1, 
"x_prefix": 1}

# ------------------------------------------------------
# REQUIRED: force metadata DB for CLI + app init
# ------------------------------------------------------

SQLALCHEMY_DATABASE_URI = os.environ["SQLALCHEMY_DATABASE_URI"]
```
yes I have deployed using helm and updated the env value
```
env:
            - name: SUPERSET_APP_ROOT
              value: /superset
            - name: SUPERSET_CONFIG_PATH
              value: /app/superset_config.py
```
2) Istio VirtualService:

```
http:
    - match:
        - uri:
            prefix: /superset
      route:
        - destination:
            host: superset.superset.svc.cluster.local
            port:
              number: 80
          headers:
            request:
              set:
                X-Forwarded-Prefix: /superset
                X-Forwarded-Proto: https
```
3) Version check: 
I am using apache/superset:6.0.0
4) I have cross check all the config there is no trailing space, check in 
incognito still it is the same issue

GitHub link: 
https://github.com/apache/superset/discussions/37655#discussioncomment-15690747

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to