MySQL Access Denied Fix

MySQL access denied errors usually come from the wrong user, host, password, database grants or Docker environment mismatch.

Symptoms

  • Application cannot connect to MySQL.
  • mysql client returns Access denied for user.
  • Docker app works after rebuild but fails after changing .env.

Likely causes

  • Credentials do not match the MySQL user.
  • User grants are for a different host.
  • Docker volume preserved old database users.
  • Application reads a different .env than expected.

Fix steps

  1. Confirm host, port, database, user and password.
  2. Check grants for user@host.
  3. Inspect Docker Compose env variables and persistent volumes.
  4. Avoid changing root credentials without reinitializing intentionally.

Verify the fix

  • Connect with mysql CLI using the same host and credentials.
  • Log the configured host without printing passwords.
  • Restart the app after config changes.

FAQ

Why did changing .env not fix MySQL?

Existing database volumes may keep the old initialized users and passwords.

Is localhost the same as 127.0.0.1?

Not always. MySQL may treat socket and TCP connections differently.

Related tools and guides

ENV .env Generator

Generate clean .env starter files for local development, app configuration, databases, Redis, mail and API placeholders.

 Docker Docker Compose Generator

Generate starter docker-compose.yml snippets for common local development stacks.

 PHP PHP Error Explainer

Paste common PHP errors and get likely causes, fixes and verification steps for runtime, syntax and dependency problems.

 Docker Docker Compose and .env Workflow for Local Development

Local stacks are easier to maintain when docker-compose.yml describes services and .env.example documents configuration without real secrets.

Last updated: May 18, 2026