How to setup an application (MERN) in a single Droplet

Hey Marcos,

Happy to hear that you’ve made such a good progress. Here are a few steps that you can follow to help you with further troubleshooting this:

1. Review Firewall Settings: Start by reviewing your firewall settings. Ensure that your firewall isn’t blocking MongoDB’s default port (27017). You can check the active firewall rules using:

   sudo ufw status
   

   If necessary, allow traffic on MongoDB’s port:

   sudo ufw allow 27017
   

2. Confirm MongoDB Configuration: If your MongoDB instance is running on your Droplet as well, verify MongoDB’s mongod.conf file to ensure it’s correctly set up to listen on the appropriate network interface. The configuration file is typically located at /etc/mongod.conf. You should see a line like bindIp: 127.0.0.1 (for localhost connections) or bindIp: 0.0.0.0 (to listen on all interfaces).

3. Testing MongoDB Connection: Test the MongoDB connection independently from your backend. Use the mongosh command:

   mongosh "mongodb://localhost:27017"
   

   This helps confirm that MongoDB is running and accessible.

4. Backend Service Debugging: Start your Node.js backend and watch for errors. If it crashes after trying to connect to MongoDB, the console should provide some insight. You can start your Node.js app with:

   node app.js
   

   Replace app.js with your main server file.

5. Review Node.js MongoDB Connection String: In your Node.js application, ensure the MongoDB connection string is correctly formatted. It generally looks like this:

   const mongoose = require('mongoose');
   mongoose.connect('mongodb://localhost:27017/yourdbname', { useNewUrlParser: true, useUnifiedTopology: true });
   

6. Inspect SSL/TLS Configuration: Since you mentioned a decryption error, double-check your SSL/TLS configuration for MongoDB. Ensure the .pem file path is correct and the file is accessible by your Node.js app.

7. Nginx Reverse Proxy Setup: For Nginx, you’ll want to set up reverse proxy settings for your Node.js app. Here’s an example configuration snippet for your /etc/nginx/sites-available/default file:

   server {
       listen 80;
       server_name your_domain_or_IP;
   
       location / {
           proxy_pass http://localhost:3333; # Replace with your Node.js port
           proxy_http_version 1.1;
           proxy_set_header Upgrade $http_upgrade;
           proxy_set_header Connection 'upgrade';
           proxy_set_header Host $host;
           proxy_cache_bypass $http_upgrade;
       }
   }
   

   After updating, restart Nginx:

   sudo systemctl restart nginx
   

8. Logging and Monitoring: Keep an eye on both Nginx and Node.js logs for any errors that might provide more clues:

   • Nginx: /var/log/nginx/error.log
   • Node.js: You can add custom logging within your application or use a process manager like PM2 that keeps logs.

If you are using a managed MongoDB cluster, you would need to make sure that your backend Droplet IP address is allowed in the trusted sources of the MongoDB cluster.

Keep us posted on your progress, and don’t hesitate to reach out for further assistance!

Best,

Bobby