Need help setting up Superset chart in AWS EKS behind ALB #36296
-
|
Hi all. i've tried adding some logging into logging.py to figure out what's going wrong to no avail. It just hangs. This is behind AWS alb running in k8, if that helps narrow it down. I've tried 5.0.0 and now on 6.0.0r3 with same results superset 10.17.0.219 - - [26/Nov/2025:17:27:37 +0000] "GET / HTTP/1.1" 302 223 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36"
superset 2025-11-26 17:27:37,642:DEBUG:root:<flask_login.mixins.AnonymousUserMixin object at 0x7fef2c2757b0>
superset 2025-11-26 17:27:37,642:WARNING:root:Failed to add user to db session: Class 'werkzeug.local.LocalProxy' is not mapped
superset 2025-11-26 17:27:37,645:DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
# added debug prints to the classes for the sqlalchemy session and flask global context
superset debug_print of: <flask.g of 'superset.app'>
superset user: <flask_login.mixins.AnonymousUserMixin object at 0x7fef2c2757b0>
superset _login_user: <flask_login.mixins.AnonymousUserMixin object at 0x7fef2c2757b0>
# this at least confirms that I have a db session
superset debug_print of: <sqlalchemy.orm.scoping.scoped_session object at 0x7fef2ede8580>
superset session_factory: sessionmaker(class_='CustomSignallingSession', db=<SQLA engine=postgresql+psycopg2://db-sa:***@db.myorg.local:5432/uns>, query_cls=<class 'flask_sqlalchemy.BaseQuery'>, bind=None, autoflush=True, autocommit=False, expire_on_commit=True)
superset registry: <sqlalchemy.util._collections.ScopedRegistry object at 0x7fef2ede8d00>
superset 10.17.0.219 - - [26/Nov/2025:17:27:37 +0000] "GET /superset/welcome/ HTTP/1.1" 302 261 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36" |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 10 replies
-
|
Hi @SB-MFJ! I'm Dosu and I’m helping the superset team. 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). Here’s a focused checklist to resolve this setup:
If you follow these steps and still see the issue, please share your relevant To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
The persistent If you’re sure your environment is correct, check for any custom authentication, user management, or security manager code in To isolate the issue, try deploying a minimal, official Superset image (no custom overrides) in your EKS/ALB setup. If the error disappears, incrementally reintroduce your overrides to find the culprit. If it persists, double-check your Python/Node.js versions and clean up any old Docker volumes before redeploying (source). Let me know if you want a step-by-step on how to check your runtime versions or isolate custom code! To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
Noticed this error: this user is created by the app with the helm values: The database is blank, so I'm not sure where this error is coming from |
Beta Was this translation helpful? Give feedback.
-
|
The "User already exists" error during Superset initialization is expected and benign in Helm/Kubernetes setups—it just means the admin user already exists in the metadata database, and the init job script is designed to ignore this and continue without failing (source). This does not cause or relate to the "werkzeug.local.LocalProxy is not mapped" error. The LocalProxy error is almost always due to session/context issues, version mismatches (Superset requires Python 3.10/3.11 and Node.js 20.x), or custom authentication/security manager code returning a LocalProxy instead of a real user object (source). It can also happen if requests hit endpoints outside a valid Flask context, such as misrouted ALB/Ingress traffic or health checks (source). To further diagnose:
Best practices: use supported Python/Node versions, ensure proper proxy header and session cookie config, and avoid requests outside Flask context (source). To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
After wiping the DB i get a new error: |
Beta Was this translation helpful? Give feedback.
-
|
This error happens because PostgreSQL ENUM types like To fix this, manually drop the lingering ENUM type before rerunning migrations: DROP TYPE IF EXISTS emaildeliverytype;You can run this in For future resets, consider scripting the cleanup of persistent types. Superset migrations don't currently check for or drop existing ENUMs before creating them, so manual cleanup is required (source). To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
|
Beta Was this translation helpful? Give feedback.
-
|
Alright, the actual error ended up being cache server config. if you have been upgrading from a legacy Elasticache before they had user auth, you might also need to set the username to not blank and to set the RECAPCHA_PUBLIC/PRIVATE_KEY per Flask App Builder as with using LDAP you also need to set Part user error, part weird doc structure between FAB and Superset, part needs more debug errors. |
Beta Was this translation helpful? Give feedback.
Alright, the actual error ended up being cache server config.
If you, dear viewer, also go down this rabbit hole, double check:
AWS Elasticache needs TLS to be set on, despite using 6379
if you have been upgrading from a legacy Elasticache before they had user auth, you might also need to set the username to not blank
and to set the RECAPCHA_PUBLIC/PRIVATE_KEY per Flask App Builder as with using LDAP you also need to set
AUTH_USER_REGISTRATION = True