Heroku构建成功后出现应用错误（Node+React项目）

Hey there, sorry to hear you're stuck with this frustrating error—especially since you've deployed identical tech stacks without issues before! Let's walk through actionable steps to track down what's going wrong:

1. Check Your Deployment Logs First #

The error message explicitly tells you to check logs, and this is always the starting line for deployment issues. Every platform (Heroku, Vercel, Netlify, etc.) has a way to access real-time or historical logs:

• For Heroku, run heroku logs --tail in your terminal to stream live logs.
• For Vercel/Netlify, navigate to your project dashboard and look for "Logs" or "Function Logs" sections.
  Look for specific error messages like:
  • Port conflicts (e.g., "Port 5000 is already in use")
  • Missing environment variables (e.g., "Cannot read property 'DB_URL' of undefined")
  • Failed dependency installs (e.g., "Module not found: 'express'")

2. Verify Port Configuration #

• Backend Port: Make sure your Node.js server isn't hardcoding a port like 5000. Use process.env.PORT || 5000 instead—most deployment platforms assign a random port via the PORT environment variable.
• React Proxy: If you're using the CRA proxy field in package.json (e.g., "proxy": "http://localhost:5000"), note that this only works in development. For production, you'll need to either:
  • Serve the React build folder directly from your Node.js server (using express.static), or
  • Use an environment variable to point your React app to the correct backend URL (e.g., REACT_APP_API_URL=https://your-backend-url.com)

3. Audit Your Scripts #

• Development vs Production Scripts: Your concurrently setup is great for local dev, but production deployments shouldn't rely on it. Double-check your package.json scripts:
  • Local dev: "dev": "concurrently \"npm run server\" \"npm run client\""
  • Production: "start": "node server.js" (make sure your server is configured to serve the React build folder if needed)
• Dependency Installation: If you have tools like concurrently or nodemon in devDependencies, some platforms won't install them by default. Ensure your production start script doesn't depend on dev-only packages.

4. Confirm Environment Variables #

Local .env files don't get pushed to deployment platforms. Check if you've set all required environment variables (like database credentials, API keys) in your platform's dashboard:

• Heroku: Go to "Settings" > "Config Vars"
• Vercel: Go to "Settings" > "Environment Variables"
• Netlify: Go to "Site Settings" > "Environment Variables"

5. Reproduce the Issue Locally #

Simulate the production environment on your machine to rule out platform-specific issues:

1. Run npm run build in your React client folder to generate the production build.
2. Update your Node.js server to serve this build folder (add app.use(express.static(path.join(__dirname, '../client/build'))) if you haven't already).
3. Start your server with npm start (not npm run dev).
4. Try accessing the app locally—if you get the same error, you can debug it directly on your machine without deployment delays.

Since you've got experience with this stack, once you pull up those logs, you'll likely spot a small oversight (like a missing env var or misconfigured port) that slipped through this time. Happy debugging!

内容的提问来源于stack exchange，提问作者Thidasa Pankaja