基于Express和Node.js的注册登录功能异常求助

Hey there! I totally get how frustrating it is when you copy code exactly from a course and it still doesn't work—been there, done that with MEAN stack when I was starting out. Let's break down the most common culprits that could be causing this "invalid user" error and redirect to /auth/failure:

1. Double-Check Your Database Connection #

• Chances are, your local setup doesn't match the course's database configuration. Maybe:
  • Your local MongoDB service isn't running (try firing up mongod in your terminal to start it).
  • Your MONGODB_URI in .env is pointing to the wrong database name, or you're using a MongoDB Atlas cluster that you haven't whitelisted your IP for.
  • The course might have used a pre-seeded database, while yours is empty—though that shouldn't block registration, it's worth verifying the connection logs in your terminal.

2. Ensure Request Body Parsing is Enabled #

MEAN stack backends rely on parsing incoming POST data to read username/password fields. If you're missing this middleware, your backend won't see the data you're sending, so it'll flag the user as invalid:

• Verify your Express app has these lines early in your code (before your routes):

  app.use(express.json());
  app.use(express.urlencoded({ extended: true }));
  

3. Check Password Hashing Logic #

If the course used bcrypt (super common for auth), a mismatch in hashing parameters or versions can break validation:

• Confirm you're using the same salt rounds as the course (most courses use 10, but double-check):

  const hashedPassword = await bcrypt.hash(req.body.password, 10);
  

• Make sure your registration code is actually saving the hashed password to the database, not the plaintext one.
• For login, ensure you're using bcrypt.compare() in the correct order: bcrypt.compare(plaintextPassword, hashedPasswordFromDB)—mixing these up will always return false.

4. Verify Route & Frontend Form Alignment #

Sometimes a tiny typo can throw everything off:

• Check that your frontend form's action attribute matches the backend registration route (e.g., if your backend uses /api/auth/register, make sure the form isn't pointing to /auth/register).
• Open your browser's DevTools (F12), go to the Network tab, and watch the registration request. Look at:
  • The request URL—does it match your backend route?
  • The request body—are username/password being sent correctly?
  • The response status code (404 means missing route, 400 means bad request data).

5. Confirm Environment Variables Are Loaded #

If the course used dotenv to manage secrets (like JWT keys or DB URIs):

• Make sure you have a .env file in your project root with the exact variable names the code expects (e.g., if the code uses process.env.JWT_SECRET, don't name it JWT_KEY in your .env).
• Ensure you're loading dotenv at the very top of your server file:

  require('dotenv').config();
  

6. Rule Out CORS Issues #

While CORS usually causes blocked requests, misconfiguration can sometimes lead to truncated or missing data:

• If your frontend is on localhost:3000 and backend on localhost:5000, make sure you've set up the cors middleware correctly:

  const cors = require('cors');
  app.use(cors({ origin: 'http://localhost:3000' })); // Or use app.use(cors()) for development
  

If none of these fix the issue, share snippets of your registration route code, database connection setup, and frontend form code—those details will help narrow down the problem even more!

内容的提问来源于stack exchange，提问作者rini saha