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:59:31 UTC
Re: [D] [6.0.0rc2] Custom prefix for URL on your site, not localhost. Closing port 8088 to external access. [superset]
GitHub user dosubot[bot] edited a comment on the discussion: [6.0.0rc2] Custom prefix for URL on your site, not localhost. Closing port 8088 to external access.
<!-- Answer -->
Yes, you can run Superset with a custom URL path prefix by setting the `SUPERSET_APP_ROOT` environment variable (for example, `SUPERSET_APP_ROOT=/analytic/monitor`). This allows Superset to be served under a custom path like `mysite.com/analytic/monitor`, and login redirects will work correctly with the prefix [source](https://github.com/apache/superset/pull/34395).
When closing port 8088 to external access, Superset should be exposed via a reverse proxy (such as Nginx or Traefik) that forwards requests to the container internally. Make sure to enable proxy header handling in Superset using `ENABLE_PROXY_FIX` and configure `PROXY_FIX_CONFIG` for proper path and header forwarding [source](https://github.com/apache/superset/blob/master/superset/config.py).
For Docker networking: if Superset cannot connect to the database after moving to a custom network, check that the database hostname in `SQLALCHEMY_DATABASE_URI` is resolvable from the Superset container within that network. Avoid using `localhost` for the database host; instead, use the service name defined in your Docker Compose file, `host.docker.internal` (Mac/Windows), or the Docker gateway IP (Linux) [source](https://github.com/apache/superset/blob/master/docs/docs/installation/docker-compose.mdx).
Superset's default Docker Compose setup is for single-host development and may require extra configuration for production, especially with custom networks and reverse proxies. If you need more advanced networking, ensure all services are on the same Docker network and that service names are used for connectivity [source](https://github.com/apache/superset/blob/master/docker-compose-non-dev.yml).
Let me know if you need more details on reverse proxy configuration or troubleshooting database connectivity!
<!-- 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=43902ef2-3523-488e-b24a-a899f7a42084) [](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/35637#discussioncomment-14674504
----
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