You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "rusackas (via GitHub)" <gi...@apache.org> on 2026/03/11 19:22:39 UTC
Re: [I] werkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server [superset]
rusackas commented on issue #20319:
URL: https://github.com/apache/superset/issues/20319#issuecomment-4041607060
This issue has accumulated reports of many different configuration problems over three years, with most being resolved through environment-specific fixes (frontend build, nginx websocket proxy, session cookie settings, etc.) rather than a bug in Superset itself.
These are setup and configuration concerns best addressed through:
- The [Superset installation documentation](https://superset.apache.org/docs/installation/docker-compose)
- The [Apache Superset Slack community](https://communityinviter.com/apps/apache-superset/apache-superset)
- The [GitHub Discussions](https://github.com/apache/superset/discussions) section
If you have identified a specific, reproducible bug in Superset's code (not a configuration issue), please open a new focused issue with your Superset version, deployment method, and minimal reproduction steps.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org