GitHub user dosubot[bot] added a comment to the discussion: How to install and configure superset step by step??
<!-- Answer --> The error "NoneType object has no attribute is_active" means Superset is trying to access the is_active property on a user object that is actually None. This usually happens when the user/session context isn't set up correctly—often because of a config import failure, database issue, or a problem with authentication setup. In Superset 5, this is a common symptom if your custom config file fails to load or if the database migrations didn't complete cleanly, leaving user/session management in a broken state ([details](https://github.com/apache/superset/issues/34441)). Here's what to check and try: 1. Make sure your custom config file is named superset_config_docker.py and placed in ./docker/pythonpath_dev/ on your host machine (not superset_config.py or in another location). Remove any SUPERSET_CONFIG_PATH overrides. 2. To confirm your config is being loaded, add raise Exception("test") at the top of superset_config_docker.py and restart your containers. If you see this error in the logs, the config is loading; if not, Superset is ignoring your config ([reference](https://github.com/apache/superset/issues/34441)). 3. Carefully review the Superset and database container logs for any import, syntax, or runtime errors during startup. Any error in your config file will prevent it from loading and can break user/session handling. 4. Make sure the initial database migration completed successfully and that the Superset web UI is accessible. If migrations failed or the metadata DB is missing tables, user/session objects may not be created correctly. 5. If the error persists, check if you have any custom authentication or user/session code in your config that could interfere with user initialization. Superset expects g.user to always be a valid user or AnonymousUser; if it's None, you'll see this error ([code reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/views/utils.py)). If you still see the error after these steps, please provide the full stack trace and specify what action triggers the error (e.g., login, dashboard access, etc.) so we can help further. <!-- 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/529ef41d-d84b-442a-ace0-5c2df5aa28cb?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/529ef41d-d84b-442a-ace0-5c2df5aa28cb?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/529ef41d-d84b-442a-ace0-5c2df5aa28cb?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/529ef41d-d84b-442a-ace0-5c2df5aa28cb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/529ef41d-d84b-442a-ace0-5c2df5aa28cb?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/529ef41d-d84b-442a-ace0-5c2df5aa28cb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/529ef41d-d84b-442a-ace0-5c2df5aa28cb?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](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/34439) GitHub link: https://github.com/apache/superset/discussions/34439#discussioncomment-13955025 ---- 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]
