You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 02:51:43 UTC
Re: [D] public dashboard not working [superset]
GitHub user dosubot[bot] edited a comment on the discussion: public dashboard not working
<!-- Answer -->
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]](https://github.com/apache/superset/issues/33702).
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]](https://github.com/apache/superset/discussions/31949).
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]](https://github.com/apache/superset/issues/32836).
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]](https://github.com/apache/superset/issues/31434).
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.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=2b06ccbd-196d-40cc-a3db-ca31251cffba) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34050#discussioncomment-13650877
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org