GitHub user dosubot[bot] added a comment to the discussion: Need help setting up Superset chart in AWS EKS behind ALB
<!-- Greeting --> Hi @SB-MFJ! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> The “LocalProxy is not mapped” warning and the hanging/gateway timeout are usually caused by proxy/session misconfiguration or health check issues when running Superset behind AWS ALB in EKS—not by a bug in Superset itself, especially since you’re on 5.0.0+ where the main LocalProxy fix is present ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/CHANGELOG/5.0.0.md#L144-L144)). Here’s a focused checklist to resolve this setup: 1. **Superset config**: In your `superset_config.py` (or Helm `configOverrides`), set: ```python ENABLE_PROXY_FIX = True PROXY_FIX_CONFIG = {"x_proto": 1, "x_host": 1, "x_prefix": 1, "x_port": 0} SESSION_COOKIE_SECURE = True # if using HTTPS SESSION_COOKIE_SAMESITE = "None" # if cross-domain or HTTPS ``` Make sure your `SECRET_KEY` is a strong, random value (not the default), and your `SQLALCHEMY_DATABASE_URI` is correct ([source](https://github.com/apache/superset/issues/31862)). 2. **Ingress/ALB annotations**: In your Helm `values.yaml` under `ingress.annotations`, include: ``` alb.ingress.kubernetes.io/scheme: internet-facing alb.ingress.kubernetes.io/target-type: ip alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}]' alb.ingress.kubernetes.io/healthcheck-path: /health alb.ingress.kubernetes.io/healthcheck-port: traffic-port alb.ingress.kubernetes.io/healthcheck-protocol: HTTP ``` Set `ingressClassName: alb` and ensure the `hosts` field is a valid DNS name ([source](https://github.com/apache/superset/discussions/34882#discussioncomment-14410476)). 3. **Health checks**: Superset pods must respond with HTTP 200 on `/health` at port 8088. Check pod health with: ``` kubectl get pods kubectl exec <pod> -- curl localhost:8088/health ``` In AWS, confirm the ALB target group shows healthy targets. 4. **Timeouts**: Set ALB, Nginx, and Kubernetes timeouts higher than Superset’s `SUPERSET_WEBSERVER_TIMEOUT` (default 60s) to avoid premature disconnects. For long queries, add ingress annotations like: ``` nginx.ingress.kubernetes.io/proxy-read-timeout: "120" nginx.ingress.kubernetes.io/proxy-send-timeout: "120" nginx.ingress.kubernetes.io/proxy-connect-timeout: "120" ``` 5. **Proxy headers**: Ensure ALB forwards all `X-Forwarded-*` headers. Misconfigured headers or session cookies can cause redirect loops, login failures, or the LocalProxy error ([source](https://github.com/apache/superset/discussions/35241#discussioncomment-14483120)). 6. **Debugging**: If you still see timeouts or login loops, increase logging in Superset and your OAuth provider. Try switching to NGINX ingress as a test—some users have found ALB-specific issues with header forwarding and session stickiness. If you follow these steps and still see the issue, please share your relevant `values.yaml` and `superset_config.py` (with secrets redacted) for more targeted help. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/45d59322-81d8-4447-9f9e-675384f7b052?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/45d59322-81d8-4447-9f9e-675384f7b052?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/45d59322-81d8-4447-9f9e-675384f7b052?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/45d59322-81d8-4447-9f9e-675384f7b052?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/45d59322-81d8-4447-9f9e-675384f7b052?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/45d59322-81d8-4447-9f9e-675384f7b052?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/45d59322-81d8-4447-9f9e-675384f7b052?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=The%20%E2%80%9CLocalProxy%20is%20not%20mapped%E2%80%9D%20warning%20and%20the%20hanging/gateway%20timeout%20are%20usually%20caused%20by%20proxy/session%20misconfiguration%20or%20health%20check%20issues%20when%20running%20Superset%20behind%20AWS%20ALB%20in%20EKS%E2%80%94not%20by%20a%20bug%20in%20Superset%20itself%2C%20especially%20since%20you%E2%80%99re%20on%205.0.0%2B%20where%20the%20main%20LocalProxy%20fix%20is%20present%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/CHANGELOG/5.0.0.md%23L144-L144%29%29.%0A%0AHere%E2%80%99s%20a%20focused%20checklist%20to%20resolve%20this%20setup%3A%0A%0A1.%20%2A%2ASuperset%20config%2A%2A%3A%20%20%0A%20%20%20In%20your%20%60superset_config.py%60%20%28or%20Helm%2 0%60configOverrides%60%29%2C%20set%3A%0A%20%20%20%60%60%60python%0A%20%20%20ENABLE_PROXY_FIX%20%3D%20True%0A%20%20%20PROXY_FIX_CONFIG%20%3D%20%7B%22x_proto%22%3A%201%2C%20%22x_host%22%3A%201%2C%20%22x_prefix%22%3A%201%2C%20%22x_port%22%3A%200%7D%0A%20%20%20SESSION_COOKIE_SECURE%20%3D%20True%20%20%23%20if%20using%20HTTPS%0A%20%20%20SESSION_COOKIE_SAMESITE%20%3D%20%22None%22%20%20%23%20if%20cross-domain%20or%20HTTPS%0A%20%20%20%60%60%60%0A%20%20%20Make%20sure%20your%20%60SECRET_KEY%60%20is%20a%20strong%2C%20random%20value%20%28not%20the%20default%29%2C%20and%20your%20%60SQLALCHEMY_DATABASE_URI%60%20is%20correct%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/issues/31862%29%29.%0A%0A2.%20%2A%2AIngress/ALB%20annotations%2A%2A%3A%20%20%0A%20%20%20In%20your%20Helm%20%60values.yaml%60%20under%20%60ingress.annotations%60%2C%20include%3A%0A%20%20%20%60%60%60%0A%20%20%20alb.ingress.kubernetes.io/scheme%3A%20internet-facing%0A%20%20%20alb.ingress.kubernetes.io/target-type%3A%20ip% 0A%20%20%20alb.ingress.kubernetes.io/listen-ports%3A%20%27%5B%7B%22HTTP%22%3A%2080%7D%5D%27%0A%20%20%20alb.ingress.kubernetes.io/healthcheck-path%3A%20/health%0A%20%20%20alb.ingress.kubernetes.io/healthcheck-port%3A%20traffic-port%0A%20%20%20alb.ingress.kubernetes.io/healthcheck-protocol%3A%20HTTP%0A%20%20%20%60%60%60%0A%20%20%20Set%20%60ingressClassName%3A%20alb%60%20and%20ensure%20the%20%60hosts%60%20field%20is%20a%20valid%20DNS%20name%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/discussions/34882%23discussioncomment-14410476%29%29.%0A%0A3.%20%2A%2AHealth%20checks%2A%2A%3A%20%20%0A%20%20%20Superset%20pods%20must%20respond%20with%20HTTP%20200%20on%20%60/health%60%20at%20port%208088.%20Check%20pod%20health%20with%3A%0A%20%20%20%60%60%60%0A%20%20%20kubectl%20get%20pods%0A%20%20%20kubectl%20exec%20%3Cpod%3E%20--%20curl%20localhost%3A8088/health%0A%20%20%20%60%60%60%0A%20%20%20In%20AWS%2C%20confirm%20the%20ALB%20target%20group%20shows%20healthy%20targets.%0A%0A4.%20%2A%2 ATimeouts%2A%2A%3A%20%20%0A%20%20%20Set%20ALB%2C%20Nginx%2C%20and%20Kubernetes%20timeouts%20higher%20than%20Superset%E2%80%99s%20%60SUPERSET_WEBSERVER_TIMEOUT%60%20%28default%2060s%29%20to%20avoid%20premature%20disconnects.%20For%20long%20queries%2C%20add%20ingress%20annotations%20like%3A%0A%20%20%20%60%60%60%0A%20%20%20nginx.ingress.kubernetes.io/proxy-read-timeout%3A%20%22120%22%0A%20%20%20nginx.ingress.kubernetes.io/proxy-send-timeout%3A%20%22120%22%0A%20%20%20nginx.ingress.kubernetes.io/proxy-connect-timeout%3A%20%22120%22%0A%20%20%20%60%60%60%0A%0A5.%20%2A%2AProxy%20headers%2A%2A%3A%20%20%0A%20%20%20Ensure%20ALB%20forwards%20all%20%60X-Forwarded-%2A%60%20headers.%20Misconfigured%20headers%20or%20session%20cookies%20can%20cause%20redirect%20loops%2C%20login%20failures%2C%20or%20the%20LocalProxy%20error%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/discussions/35241%23discussioncomment-14483120%29%29.%0A%0A6.%20%2A%2ADebugging%2A%2A%3A%20%20%0A%20%20%20If%20you%20st ill%20see%20timeouts%20or%20login%20loops%2C%20increase%20logging%20in%20Superset%20and%20your%20OAuth%20provider.%20Try%20switching%20to%20NGINX%20ingress%20as%20a%20test%E2%80%94some%20users%20have%20found%20ALB-specific%20issues%20with%20header%20forwarding%20and%20session%20stickiness.%0A%0AIf%20you%20follow%20these%20steps%20and%20still%20see%20the%20issue%2C%20please%20share%20your%20relevant%20%60values.yaml%60%20and%20%60superset_config.py%60%20%28with%20secrets%20redacted%29%20for%20more%20targeted%20help.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/36296) GitHub link: https://github.com/apache/superset/discussions/36296#discussioncomment-15089323 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
