Redirect to localhost:8088 in Superset running on GitHub Codespaces (Docker)

[volktier]

Hi everyone
I’m running Apache Superset via Docker Compose in GitHub Codespaces.
The UI is accessible at github dev.
The issue:
When I click the only “Create Dashboard” button, Superset redirects me to localhost:8088/ dashboard/new/ instead of staying on the Codespaces domain.
What I’ve already tried:
Setting variables in docker-compose
ENABLE_PROXY_FIX: “true”
CYPRESS_CONFIG_BASE_URL: https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev/
OVERRIDE_BASE_URL = “https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev/”

superset:
image: apache/superset:latest
container_name: superset
user: root
volumes:
- ./superset_config.py:/app/pythonpath/superset_config.py
environment:
ENABLE_PROXY_FIX: "true"
SUPERSET_SECRET_KEY: 'your-secret-key-change-this'
PYTHONPATH: "/usr/local/lib/python3.10/site-packages:/app/pythonpath"
ports:
- "8088:8088"
networks:
- greenplum-net
command: >
sh -c "
pip install --no-cache-dir psycopg2-binary &&
superset fab create-admin --username admin --firstname admin --lastname admin --email admin@example.com --password admin &&
superset db upgrade &&
superset init &&
gunicorn --bind 0.0.0.0:8088 --workers 4 --worker-class gthread --timeout 60 \"superset.app:create_app()\"
` "

superset_config.py:

must be https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev/dashboard/new/

endless loading if i try:
SUPERSET_WEBSERVER_DOMAINS = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'
OVERRIDE_BASE_URL = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'

endless loading if i try:
SUPERSET_WEBSERVER_DOMAINS = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'

redirect to http://localhost:8088/dashboard/new/ if i try:
SUPERSET_WEBSERVER_ADDRESS = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'
OVERRIDE_BASE_URL = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'

redirect to http://localhost:8088/dashboard/new/ if i try:
SUPERSET_WEBSERVER_ADDRESS = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'

redirect to http://localhost:8088/dashboard/new/ if i try:
SUPERSET_WEBSERVER_BASEURL = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'
OVERRIDE_BASE_URL = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'

redirect to http://localhost:8088/dashboard/new/ if i try:
SUPERSET_WEBSERVER_BASEURL = 'https://friendly-capybara-7jvxwxv77w7hpj44-8088.app.github.dev'

[dosubot[bot]]

Hi @volktier! I'm Dosu and I’m helping the superset team.

The redirect to localhost:8088 happens because Superset doesn't know its external domain — the "Create Dashboard" button uses a hardcoded /dashboard/new/ path in the frontend, and Flask resolves the full URL based on request context. Without proper proxy headers, it falls back to localhost.

The fix is ENABLE_PROXY_FIX in superset_config.py (not as a Docker env var), combined with the PROXY_FIX_CONFIG [1]:

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

This enables Werkzeug's ProxyFix middleware [2], which reads X-Forwarded-Host, X-Forwarded-Proto, etc. from the proxy. GitHub Codespaces acts as a reverse proxy and should be setting these headers when forwarding traffic to your container.

A few notes on what you tried:

• OVERRIDE_BASE_URL does not exist in Superset — there's no such config option.
• SUPERSET_WEBSERVER_DOMAINS is deprecated and was for domain sharding, not base URL configuration [3].
• SUPERSET_WEBSERVER_ADDRESS controls the bind address for the dev server, not the external-facing URL.

Also, since Codespaces handles HTTPS termination, make sure Talisman doesn't try to force HTTPS itself [4]:

TALISMAN_CONFIG = {
    "force_https": False,
    "content_security_policy": None,  # or configure as needed
}

If ENABLE_PROXY_FIX = True still results in localhost redirects, it likely means the Codespaces proxy isn't setting X-Forwarded-Host. You can verify by adding some debug logging to check incoming request headers. In that case, a workaround would be to put a small Nginx container in front of Superset within your Docker Compose that explicitly sets the forwarded headers:

proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-Host $http_host;
proxy_set_header X-Forwarded-Proto https;

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.