[Bug]: Prevent Silent Database Connection Failures

[affanraza84]

Bug Description

Description

The database connection logic catches connection errors but does not propagate or handle them appropriately. As a result, the server can start successfully even when MongoDB is unavailable.

Acceptance Criteria

• Database connection failures prevent server startup.
• Detailed error information is logged.
• Application exits with a non-zero status code.
• Health checks accurately reflect service availability.

Steps to Reproduce

• Application starts in an unhealthy state.
• Database-dependent requests fail at runtime.
• Operational issues become harder to diagnose.
• Monitoring systems may incorrectly report the service as healthy.

Expected Behavior

The application should fail fast when a database connection cannot be established.

Suggested Solution

Terminate the process when the database connection fails.

catch (error) {
  console.error("Database connection failed:", error);
  process.exit(1);
}

Current Behavior

const connectdb = async () => {
  try {
    await mongoose.connect(process.env.MONGODB_URL);
    console.log("DB connected");
  } catch (_error) {
    console.log("DB error");
  }
};

If the database connection fails, the application continues running and accepts requests despite being unable to access required data.

Environment

MacOS, Safari, Windows, Linux

Logs/Screenshots

No response

[affanraza84]

Hey @Nsanjayboruds I would like to work on this issue under GSSoC'26

[Nsanjayboruds]

@affanraza84 it not applicable right now so is not valid issue

i want to give you some task in our site logout function not working so you can creat a new issue for that i will assign to you

[affanraza84]

@Nsanjayboruds One more issue is there in authentication system that the user can not sign in/up using google

Should I raise this issue too?

---

Also signing up using email is taking too much time to send OTP . I think I should work on whole authentication system.