Rails: ActiveRecord::NoDatabaseError: We could not find your database
Rails reached the database server and logged in, but the database it asked for does not exist there. That rules out the host and the password. On a fresh clone, a new CI runner or a new Docker volume nobody has run db:create yet, or DATABASE_URL points at a server where the database has a different name from config/database.yml. When both are set, DATABASE_URL wins, which is how a stale environment variable quietly overrides the file you are reading.
Quick fix
Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.
# Which database is Rails trying to use?
echo "$DATABASE_URL"
grep -A 6 "^development:" config/database.yml
# Create it, then migrate or load the schema
bin/rails db:create
bin/rails db:prepare # creates when missing, otherwise migrates
# PostgreSQL: list the databases that do exist on that server
psql -h localhost -U postgres -l
# Docker: POSTGRES_DB only takes effect on an empty data volume.
# Changing it later does nothing until the volume is recreated
docker compose exec db psql -U postgres -lHow to diagnose Ruby errors
Ruby errors are dominated by Bundler and gem resolution, native extension compilation (which needs system headers Ruby cannot install for you), and in Rails by the pending-migration and asset-precompilation guards. Those guards are deliberate safety checks, so the fix is to satisfy them rather than to disable them.
If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.
- Run
bundle installwith verbose output and read which gem fails and why. Native extension failures name the missing header in the mkmf log. - Check the mkmf log path the error prints. It contains the actual compiler error, which the Bundler summary truncates.
- For Rails migration errors, run
rails db:migrate:statusto see exactly which migrations the database has recorded. - For asset errors in production, confirm
rails assets:precompileran during deployment and that the manifest is present inpublic/assets. - Verify the Ruby version matches
.ruby-versionand the Gemfile. Version managers silently switch, producing gem-not-found errors for gems that are installed elsewhere.
Tools worth reaching for
bundle install --verboserails db:migrate:statusgem envrbenv/rvm version checkbundle exec
Authoritative references
Primary documentation for this error, worth reading before applying any fix in production.
Related Ruby errors
- Bundler: Could not find gemBundler cannot locate the specified gem in any of the configured sources (e.g., RubyGems).
- Bundler: Your bundle only supports platforms ["arm64-darwin-23"]Gemfile.lock records the platforms it was resolved for, and it was generated on a Mac, so the…
- Encoding::InvalidByteSequenceErrorA string contains bytes that are invalid for the expected encoding (e.g., invalid UTF-8 bytes).
- LoadError: cannot load such fileRuby cannot find the required file or gem. The gem may not be installed, or the require path…
- Rails: ActionController::InvalidAuthenticityTokenThe CSRF token in the request did not match the one in the session. Rails keeps the session…
- Rails: Asset not precompiledA referenced asset (CSS, JS, image) was not included in the precompiled asset list for…
- Rails: Blocked hosts: myapp.example.comThis is Rails' own HostAuthorization middleware, added in Rails 6 to stop DNS rebinding…
- Rails: could not obtain a connection from the pool within 5.000 secondsEach thread that touches the database needs its own connection, and every connection in the…
Browse other categories
- HTTP 494xx client errors, 5xx server errors, redirects, headers and protocol problems.
- JavaScript 42npm resolution, async pitfalls, hydration, memory limits and runtime type…
- Database 41Connections, deadlocks, constraints, replication and memory limits.
- AI 35Rate limits, context windows, GPU memory and model-serving failures.
- Network 35Refused connections, timeouts, resets, MTU problems and port exhaustion.
- Python 35Imports, virtual environments, encoding, concurrency and dependency conflicts.
- Kubernetes 34CrashLoopBackOff, ImagePullBackOff, OOMKilled, RBAC, scheduling and storage.
- Docker 27Daemon connectivity, disk space, image pulls, ports and architecture mismatches.
- System 26Disk space, systemd units, file descriptors, OOM killer and scheduled jobs.
- Cloud 25IAM permissions, quotas, service limits and credential failures.
- Security 25JWT validation, CSRF, OAuth grants, SELinux, SSH host keys and CSP.
- TLS 24Untrusted authorities, expiry, hostname mismatch, chains and cipher negotiation.
Something missing or wrong?
This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.