Laravel数据迁移遇SQLSTATE[HY000] [1044]权限拒绝，求排查解决

Hey there, let's break down why this migration error is happening and get it fixed right away!

What's Behind the Error? #

The error message clearly states:

Illuminate\Database\QueryException : SQLSTATE[HY000] [1044] Access denied for user ''@'localhost' to database 'forge'

This means Laravel is trying to connect to a database named forge with an empty username—but your .env file explicitly configures it to use TafutaM and the root user. The core issue here is that Laravel isn't reading your updated .env settings, almost always due to cached old configuration values.

Step-by-Step Solutions #

• Clear Laravel's Configuration Cache
  Laravel caches config files to boost performance, but this can make it ignore changes to .env. Run this command in your project root:

  php artisan config:clear
  

  This deletes the cached config files, forcing Laravel to pull fresh values directly from your .env.

• Verify Your .env Database Settings
  Double-check for typos or missing values in your database configuration block:

  DB_CONNECTION=mysql
  DB_HOST=127.0.0.1
  DB_PORT=3306
  DB_DATABASE=TafutaM
  DB_USERNAME=root
  DB_PASSWORD=
  

  • Confirm the TafutaM database actually exists in your local MySQL instance (you mentioned creating it, but a quick sanity check never hurts).
  • If your local MySQL root user requires a password, fill it in for DB_PASSWORD—leave it blank only if you've set up root to log in without a password.

• Check .env File Location & Permissions

  • Ensure .env is placed in your project's root directory (not nested in subfolders like app/ or config/).
  • For Linux/macOS users, run chmod 644 .env to make sure the file is readable by your server or CLI user (local development usually doesn't have permission issues, but this is a quick fix if it does).

• Restart Your Development Server
  If you're using php artisan serve to run your app, stop it and restart it. The server loads configuration when it starts up, so changes to .env won't take effect until you reboot it.

Bonus: Clear Extra Caches (If Needed) #

If the above steps don't resolve the issue, try clearing route and view caches as well—though config cache is the main culprit here:

php artisan route:clear
php artisan view:clear

内容的提问来源于stack exchange，提问作者user11071523