dosubot[bot] commented on issue #34248: URL: https://github.com/apache/superset/issues/34248#issuecomment-3096033778
<!-- Answer --> The most common cause of authorization errors in the Superset Docker Compose setup is a mismatch or stale state in the database credentials or Docker volumes. Here’s what you can do: 1. Make sure your docker/.env file is unchanged and matches the repo defaults—both POSTGRES_USER/POSTGRES_PASSWORD and DATABASE_USER/DATABASE_PASSWORD should be set to superset [cite](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/.env). 2. If you’ve run Superset before, persistent Docker volumes from an older Postgres version or previous runs can cause authentication errors. Run: ``` docker compose -f docker-compose-image-tag.yml down -v docker compose -f docker-compose-image-tag.yml up ``` This will clear old volumes and start fresh [cite](https://github.com/apache/superset/issues/33823). 3. If you still can’t log in with admin/admin, the database might not have been initialized or the admin user wasn’t created. Enter the running superset container and run: ``` superset fab create-admin superset db upgrade superset init ``` This ensures the admin user and DB schema are set up [cite](https://github.com/apache/superset/discussions/34044). 4. Always check the logs of both the db and superset containers for more detailed error messages—they often reveal the root cause. Recent changes to the repo have renamed and clarified docker-compose file usage, so make sure you’re using docker-compose-image-tag.yml as documented [cite](https://github.com/apache/superset/pull/33883). If you have any custom config overrides (like superset_config_docker.py or .env-local), double-check that they don’t introduce mismatches. If the problem persists, sharing the relevant error logs from the db and superset containers will help pinpoint the issue. <!-- 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/42ab0e7b-3a92-4ca4-bc7c-9e4c7cf0fed8?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/42ab0e7b-3a92-4ca4-bc7c-9e4c7cf0fed8?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/42ab0e7b-3a92-4ca4-bc7c-9e4c7cf0fed8?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/42ab0e7b-3a92-4ca4-bc7c-9e4c7cf0fed8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/42ab0e7b-3a92-4ca4-bc7c-9e4c7cf0fed8?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/42ab0e7b-3a92-4ca4-bc7c-9e4c7cf0fed8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/42ab0e7b-3a92-4ca4-bc7c-9e4c7cf0fed8?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [! [Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34248) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
