public dashboard not working

[mlzxdzl]

I install version 5 by docker compose. My superset_config file like following:
PUBLIC_ROLE_LIKE = "Gamma"
SQLALCHEMY_DATABASE_URI = "postgresql+psycopg2://superset:superset@superset_db:5432/superset"
FEATURE_FLAGS = {
"DASHBOARD_RBAC": True,
"ALERT_REPORTS": True
}
then i give dashboard Public role in Dashboard properties
But I still can not see the dashboard when i not login in.

[dosubot[bot]]

A few things to check for public dashboards in Superset v5 with Docker Compose:

1. Make sure your config is in ./docker/pythonpath_dev/superset_config_docker.py on your host, not just superset_config.py. Superset in Docker Compose only loads overrides from this location by default. After placing it there, run docker compose down -v and docker compose up to fully reload the config. If the config isn’t loaded, PUBLIC_ROLE_LIKE and feature flags won’t take effect [source].

2. The dashboard must be published (not in draft) and have the Public role assigned in its properties. If it’s not published, it won’t be accessible even with the right role [source].

3. Some users found that adding the "can write on dashboard" permission to the Public role fixed unexpected login prompts, due to frontend PUT requests failing with 403 errors. You can check and add this permission in Security > List Roles > Public [source].

4. If you’re embedding dashboards or using iframes, check for CSP or X-Frame-Options headers that might block access, especially if you use a reverse proxy [source].

If you’ve done all this and it’s still not working, check the logs for permission or config loading errors when accessing the dashboard without login.

To reply, just mention @dosu.

---

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

[mlzxdzl]

@dosu

1. In ./docker/pythonpath_dev/ only have superset_config.py and superset_config_local.example,there is no superset_config_docker.py. Should I create it and put the config in it ? I create a superset_config.py, mount the superset_config.py (- ./docker/superset_config.py:/app/superset_config.py) and set the environment SUPERSET_CONFIG_PATH: "/app/superset_config.py"
2. My dashboard has been published
3. I did not embedding dashboards or using iframes. I only watch the dashboard on web

[dosubot[bot]]

Your current approach—mounting your superset_config.py and setting SUPERSET_CONFIG_PATH—is fully supported and will override the default Docker Compose configs, including superset_config_docker.py, as long as the path is correct and the file is readable in the container. You do not need to create superset_config_docker.py unless you want to use the default Docker override workflow instead. If SUPERSET_CONFIG_PATH is set, only that file is loaded for config overrides, and the others are ignored (source).

To confirm your config is being loaded, check the Superset logs for a message like Loaded your LOCAL configuration at [/app/superset_config.py] when the container starts. If you don’t see this, double-check your mount path, environment variable, and file permissions (source).

If you ever want to switch to the default Docker Compose workflow, copy superset_config_local.example to superset_config_docker.py in ./docker/pythonpath_dev/ and put your overrides there (source). But your current method is valid and should work.

To reply, just mention @dosu.

---

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

[sfirke]

Did you get this working? I see it's closed.