Deploying a Nodejs Application on Domain India cPanel Hosting with MongoDB Atlas Integration

Many Node.js tutorials pair an Express app with a free MongoDB Atlas cluster. On Domain India cPanel and DirectAdmin shared hosting, the Node.js part works, but the MongoDB Atlas part does not: the shared servers' outbound firewall does not allow MongoDB's port, so the app cannot reach the cluster. This guide explains what we measured, how to run your Node.js app on shared hosting with a MySQL or MariaDB database instead, and where to go if your app really needs MongoDB.

1. Why MongoDB Atlas does not connect from shared hosting

A MongoDB Atlas cluster listens on port 27017. Your app on shared hosting has to open an outgoing connection to that port. The shared servers run a firewall that allows outgoing connections only to a list of ports, and when we checked the cPanel and DirectAdmin servers on 23 September 2026, 27017 was not on it.

What you see:

• MongooseServerSelectionError or MongoNetworkError, usually after about 30 seconds;
• a timeout on the connection string's hosts, even though the same code works on your own computer;
• no change after you add the server's IP address to Atlas Network Access, because the block is on the outgoing side, not at Atlas.

The Atlas IP allow list and the hosting firewall are separate. Allowing an IP in Atlas does not open the port on the shared server.

2. Your options

3. Run the Node.js app on shared hosting

Our cPanel servers have Setup Node.js App, and our DirectAdmin servers have the same CloudLinux Node.js selector. When we checked on 23 September 2026, cPanel offered Node.js 20, 22 and 24; pick 22 or 24 if your app supports them. The short version:

The server runs your app behind Apache with Phusion Passenger, so you do not need, and cannot add, an Apache ProxyPass rule or a fixed port. The full guide, including DirectAdmin and troubleshooting, is Deploy a Node.js app on shared hosting.

4. Use MySQL or MariaDB instead of MongoDB

On shared hosting, the database that works is the one in your control panel.

1. Create a database and a database user in cPanel or DirectAdmin, and give the user all privileges on the database. The names start with your account username and an underscore.
2. Add the details as environment variables in the Node.js app form: DB_HOST=localhost, DB_USER, DB_PASSWORD and DB_NAME.
3. Add the mysql2 package to package.json and click Run NPM Install.

A connection pool with mysql2:

// db.js
const mysql = require('mysql2/promise');

const pool = mysql.createPool({
  host: process.env.DB_HOST || 'localhost',
  user: process.env.DB_USER,
  password: process.env.DB_PASSWORD,
  database: process.env.DB_NAME,
  waitForConnections: true,
  connectionLimit: 5,
});

module.exports = pool;

// app.js
const express = require('express');
const pool = require('./db');

const app = express();

app.get('/products', async (req, res) => {
  const [rows] = await pool.query('SELECT id, name, price FROM products LIMIT 50');
  res.json(rows);
});

app.listen(process.env.PORT || 3000);

If you prefer an ORM, Prisma, Sequelize and Drizzle all support MySQL. Keep the pool small: your app shares the account's resource limits. More on connecting in How to connect to the MySQL database.

5. If your app needs MongoDB

App Platform

The App Platform detects and builds Node.js apps automatically, runs each app in its own container and includes a PostgreSQL database, given to your app as DATABASE_URL. To use Atlas from it, add your connection string as an environment variable and test the connection from the running app before you rely on it, for example with a health route:

const mongoose = require('mongoose');

mongoose
  .connect(process.env.MONGODB_URI, { serverSelectionTimeoutMS: 10000 })
  .then(() => console.log('MongoDB connected'))
  .catch((err) => console.error('MongoDB connection failed:', err.message));

app.get('/health/db', (req, res) => {
  res.json({ mongo: mongoose.connection.readyState === 1 ? 'connected' : 'not connected' });
});

Current Mongoose versions need no extra options: useNewUrlParser and useUnifiedTopology are deprecated and do nothing. If the connection fails, ask support before you plan around Atlas, or use the included PostgreSQL. See Getting started with the App Platform.

VPS

On a VPS you manage the firewall yourself, so you can connect to Atlas (add the VPS IP address in Atlas Network Access) or install MongoDB on the server. A Domain India VPS is self-managed and has no cPanel. See Installing MongoDB on a Domain India VPS.

6. Keep your connection string safe

• Store it in environment variables (the Node.js app form, the App Platform dashboard or your VPS service file), never in code or a file inside public_html.
• Create an Atlas database user with access only to the database your app uses.
• Do not open Atlas Network Access to 0.0.0.0/0 to "fix" a connection problem. It does not help on shared hosting, and it exposes your cluster to the whole internet.

7. Troubleshooting

• Timeout connecting to Atlas from shared hosting: expected; port 27017 is not open outbound. Move the database to MySQL/MariaDB or the app to the App Platform or a VPS.
• The app page shows an error or 503: check the startup file and read the log named on the app's page, then restart the app.
• "Cannot find module": check that package.json is in the application root and click Run NPM Install again.
• Changes do not show: restart the app. On cPanel, add ?t=1 to the URL to skip the page cache.

8. Where Domain India fits

For a small Node.js app with a MySQL or MariaDB database, cPanel shared hosting is enough. For a production app, or one that needs MongoDB, use the App Platform or a VPS. The cards show live prices, excluding 18% GST.

Ready to deploy? Put a small app on cPanel hosting with a MySQL database, move a production app to the App Platform, choose a VPS for MongoDB, or open a support ticket to ask which fits your app.