Hey there, let's walk through the most common issues that cause an Application Error when deploying a Node.js/MongoDB Atlas app to Heroku, along with fixes for each:

Your code relies on process.env.MONGODB_URI for the production database connection—if this variable isn't set correctly in Heroku, your app will fail to connect to Atlas.

• Verify the variable exists and has the right value by running this in your terminal:

  heroku config:get MONGODB_URI
  

• If it returns nothing or an invalid string, set it using your MongoDB Atlas connection string (replace <username>, <password>, and <cluster-name> with your actual details):

  heroku config:set MONGODB_URI="mongodb+srv://<username>:<password>@<cluster-name>.mongodb.net/blogdb?retryWrites=true&w=majority"
  

  Pro tip: Make sure the connection string ends with blogdb to target your specific database.

Local MongoDB uses the mongodb:// protocol, but Atlas requires the mongodb+srv:// format to handle cloud cluster DNS resolution. If your MONGODB_URI uses the old protocol, the connection will fail.

• Head to your Atlas dashboard, go to "Connect" > "Connect your application", and copy the provided srv string directly—this avoids typos in credentials or cluster paths.

The Application Error is a generic message—Heroku logs will tell you why the app crashed. Since you have a screenshot, look for these red flags:

• MongoNetworkError: Means the app can't reach your Atlas cluster (though your 0.0.0.0/0 whitelist should fix this, double-check the cluster is online in Atlas)
• Authentication failed: Your Atlas username/password in the connection string is wrong
• Error: listen EACCES: permission denied 3000: You're hardcoding port 3000 instead of using Heroku's dynamic port
• If you need to pull fresh logs, run:

  heroku logs --tail
  

  This shows real-time logs as your app starts, so you can catch the exact failure.

Your current code logs connection errors but doesn't prevent the app from starting before the database is ready. Heroku marks apps as crashed if the main process exits unexpectedly. Update your code to:

1. Only start your Express server after a successful MongoDB connection
2. Exit the process with an error code if the connection fails
   Here's the revised code:

const mongoose = require('mongoose');
const config = require('./path-to-your-config-file');
const app = require('./path-to-your-express-app');

mongoose.connect(config.database, { useNewUrlParser: true, useUnifiedTopology: true })
  .then(() => {
    console.log('Connected to mongodb');
    // Use Heroku's dynamic port
    const PORT = process.env.PORT || 3000;
    app.listen(PORT, () => {
      console.log(`Server running on port ${PORT}`);
    });
  })
  .catch(err => {
    console.error('Failed to connect to MongoDB:', err);
    // Tell Heroku this is a critical failure
    process.exit(1);
  });

Heroku assigns a dynamic port to your app via the PORT environment variable. If your code hardcodes port 3000, Heroku can't route traffic to it, leading to an Application Error. Always use process.env.PORT as shown in the code above.

Even if your connection string is correct, your Atlas user might not have access to the blogdb database:

• Go to your Atlas dashboard > "Database Access"
• Select your database user, click "Edit"
• Ensure they have the readWrite role assigned to the blogdb database (or dbOwner if you need full access)

• MONGODB_URI is set correctly in Heroku config
• Atlas connection string uses mongodb+srv:// and has valid credentials
• Heroku logs don't show authentication/network errors
• Express server starts only after MongoDB connects
• App uses process.env.PORT instead of a fixed port
• Atlas user has readWrite access to blogdb

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