Node/Express应用中Heroku open无法运行，报R10启动超时错误

Hey Andrew, I’ve run into this exact Error R10 issue a handful of times with Heroku deployments—let’s break down how to fix it step by step.

What’s causing this? #

Error R10 happens because Heroku requires your web app to bind to the $PORT environment variable it provides within 60 seconds of launching. If your app is hardcoding a port (like 3000) instead of using this dynamic port, Heroku can’t connect to it, triggering the timeout.

Step 1: Check your app’s port configuration #

First, open your main server file (like server.js or app.js) and make sure you’re using process.env.PORT instead of a fixed number. For example, if you’re using Express:

const port = process.env.PORT || 3000; // Fallback to 3000 for local testing
app.listen(port, () => {
  console.log(`Server running on port ${port}`);
});

If you’re using npm jazz, double-check its documentation to ensure you can configure it to use the $PORT variable. Some frameworks need a specific flag or config setting to pick up environment variables.

Step 2: Verify your package.json start command #

You mentioned you added the start command, but let’s confirm it’s pointing to the right entry file. Your package.json should have something like:

"scripts": {
  "start": "node server.js" // Replace with your actual entry file
}

Test this locally first: run npm start and make sure your app boots up correctly, listening on port 3000 (or whatever fallback you set).

Step 3: Simulate Heroku’s environment locally #

To rule out environment issues, test with the $PORT variable set, just like Heroku does. On macOS, run:

PORT=5000 npm start

If your app starts and binds to port 5000, that’s a good sign it’ll work on Heroku. If it fails here, you’ve found the issue in your port handling.

Step 4: Refresh your Heroku deployment #

Sometimes old dependencies or cached build files cause problems. Try these steps:

1. Delete your local node_modules folder and package-lock.json file
2. Reinstall dependencies: npm install
3. Commit the changes: git add . && git commit -m "Fix port binding and refresh dependencies"
4. Push to Heroku: git push heroku main

Step 5: Add a Procfile (optional but recommended) #

Heroku uses a Procfile to explicitly define how to run your app. Create a file named Procfile (no extension) in your project root with this line:

web: npm start

This tells Heroku exactly which command to run for your web process, avoiding any ambiguity with default settings.

After trying these steps, run heroku open again—your app should boot up without the R10 error. If you’re still stuck, check the full Heroku logs with heroku logs --tail to look for any hidden startup errors that might be delaying the port binding.

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