ActiveRecord连接AWS MySQL实例遇NoDatabaseError，Heroku部署后连接中断求助

Hey Drew, sorry to hear your Rails-AWS MySQL connection broke after pushing to Heroku—let's troubleshoot this step by step, since the dotenv gem change is the likely culprit here.

First, let's clarify how dotenv interacts with Heroku's environment variables #

Dotenv is perfect for local development, but Heroku has its own native system for managing environment variables called config vars. The most common issue here is that your production environment either isn't loading dotenv (which is the default behavior) or you haven't mirrored your local .env variables to Heroku's config.

Here's what to check:

1. Verify your Gemfile's dotenv configuration

By default, dotenv-rails only loads in development and test environments. Take a look at your Gemfile:

gem 'dotenv-rails', groups: [:development, :test]

If this is how it's set up, your Heroku production environment won't load dotenv at all. That means any ENV['VAR_NAME'] references in your database.yml will return nil unless you've set those variables directly in Heroku's config.

2. Check Heroku's config vars for missing database credentials

Run this command in your terminal to list all environment variables set on your Heroku app:

heroku config

Make sure you see every database variable your database.yml expects—for example, AWS_DB_HOST, AWS_DB_USER, AWS_DB_PASSWORD, AWS_DB_NAME, or a full DATABASE_URL string.

If any are missing, add them using:

heroku config:set AWS_DB_HOST=your-rds-hostname AWS_DB_USER=your-db-user AWS_DB_PASSWORD=your-db-pass AWS_DB_NAME=your-db-name

Or if you prefer using DATABASE_URL (Heroku's recommended method), format it like this:

heroku config:set DATABASE_URL=mysql2://user:password@your-rds-hostname:3306/your-db-name

3. Test if your ENV variables are accessible in production

Spin up a Rails console on Heroku to confirm the variables are being picked up correctly:

heroku run rails console

Then type in the name of your database variable to check its value:

ENV['AWS_DB_HOST'] # Replace with your actual variable name

If this returns nil, that's your problem—Heroku doesn't have that variable set, or dotenv isn't loading it (but again, dotenv shouldn't be relied on for production on Heroku).

4. Double-check your database.yml production configuration

Make sure your production section is properly referencing the environment variables. For example:

production:
  adapter: mysql2
  encoding: utf8mb4
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  host: <%= ENV['AWS_DB_HOST'] %>
  username: <%= ENV['AWS_DB_USER'] %>
  password: <%= ENV['AWS_DB_PASSWORD'] %>
  database: <%= ENV['AWS_DB_NAME'] %>

Or if you use DATABASE_URL:

production:
  url: <%= ENV['DATABASE_URL'] %>
  adapter: mysql2
  encoding: utf8mb4
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>

5. Rule out RDS security group misconfig (just to be thorough)

Even though you mentioned opening all traffic, quickly confirm these details in the AWS RDS console:

• Your RDS instance has Publicly Accessible set to "Yes"
• The attached security group has an inbound rule allowing traffic from 0.0.0.0/0 (all IPs) on port 3306
• The RDS instance is in a VPC that allows internet access (since it worked before, this is less likely, but worth a quick check)

6. Check Heroku logs for specific error details

Run this command to view real-time logs and get the exact connection error message:

heroku logs --tail

Look for lines like Access denied for user (wrong credentials) or Can't connect to MySQL server on 'host' (network/host issue)—this will narrow down the problem instantly.

Final takeaway #

The most probable fix here is ensuring your Heroku config vars match the database credentials that were working before. Since you moved to dotenv locally, you might have forgotten to set those same variables on Heroku, where dotenv doesn't operate by default.

Give these steps a try, and let me know if you hit any specific errors I can help with!

内容的提问来源于stack exchange，提问作者Drew André