如何解决Google App Engine中Laravel 5.5与同项目Cloud SQL的连接错误

Hey there! Let’s walk through troubleshooting this Laravel + Google Cloud SQL connection issue together—these are the most common checks and fixes to get things working:

First, make sure your database credentials and connection settings are spot-on, especially since App Engine handles environment variables a bit differently than local setups:

• If you’re using .env locally, remember that App Engine won’t use this file directly. Instead, define your database variables in app.yaml like this:

  env_variables:
      DB_CONNECTION: mysql
      DB_HOST: /cloudsql/your-project-id:your-region:your-sql-instance-name
      DB_DATABASE: your-db-name
      DB_USERNAME: your-db-username
      DB_PASSWORD: your-db-password
  

  Critical note: For App Engine Standard, use the Unix socket path for DB_HOST (format above) instead of an IP address—it’s the most reliable and secure way to connect.
• Verify that DB_DATABASE matches the actual database you created inside your Cloud SQL instance (not the instance name itself!) and that your username/password are correct.

Your App Engine service needs explicit permission to access the Cloud SQL instance:

1. Head to the Cloud SQL Console, select your instance, and go to the Connections tab.
2. If using the Unix socket (recommended), make sure your App Engine default service account (your-project-id@appspot.gserviceaccount.com) is added to the Cloud SQL Auth Proxy authorized list.
3. If you’re using a public IP connection (less secure), add App Engine’s outbound IP ranges to the Authorized networks section of your Cloud SQL instance.

Even if you think it’s enabled, it never hurts to confirm:

• Go to the Google Cloud Console’s APIs & Services > Dashboard, search for "Cloud SQL Admin API".
• Ensure its status shows Enabled. If you just turned it on, wait a few minutes for the change to propagate—sometimes permissions take a bit to kick in.

To rule out issues with the Cloud SQL instance itself, use the Cloud SQL Auth Proxy to test connectivity from your local machine:

1. Download the proxy tool, then run this command (replace placeholders):

   ./cloud_sql_proxy -instances=your-project-id:your-region:your-sql-instance=tcp:3306
   

2. Update your local Laravel .env to set DB_HOST=127.0.0.1, then try running php artisan migrate or a simple database query.
   • If this works, the problem is with your App Engine configuration, not the Cloud SQL instance.
   • If it fails, you likely have incorrect credentials, a missing database, or a misconfigured Cloud SQL instance.

Vague "database connection error" messages aren’t helpful—check the logs for exact details:

• Go to App Engine > Logs in the Google Cloud Console.
• Search for keywords like SQLSTATE, Access denied, or Unknown database. These messages will tell you exactly what’s wrong (e.g., wrong password, missing database, connection timeout).

Your App Engine default service account needs the Cloud SQL Client role to connect to the instance:

1. Navigate to IAM & Admin > IAM in the Cloud Console.
2. Find the account your-project-id@appspot.gserviceaccount.com in the list.
3. Check its assigned roles—make sure "Cloud SQL Client" is present. (Stick to this role instead of broader ones like Admin for security best practices.)

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