I am building a NextJS web app hosted on Vercel. One of my api routes contains the following code to connect to my cluster:
const {MongoClient} = require('mongodb');
// connect to client
const uri = process.env.URI
const client = await MongoClient.connect(uri, {useNewUrlParser: true, useUnifiedTopology: true}) // this line hangs on Vercel
const companies = client.db("myDatabase").collection("companies");
// update document
const updateDoc = {$set: set};
const result = await companies.updateOne(filter, updateDoc)
console.log(`${result.matchedCount} document(s) matched the filter, updated ${result.modifiedCount} document(s): `, updateDoc);
// close connection to client
await client.close();
This runs fine on localhost. However, when running on Vercel, the code hangs on the MongoClient.connect() line. There are no errors but the connection doesn’t resolve.
I have whitelisted all IP addresses in Network Access in Atlas (“Allow Access from anywhere”) as I’ve seen that Vercel does not have a particular IP address but still getting the same issue.
The code in general is correct - if you are using the 4.x driver you can remove the useNewUrlParser and userUnifiedTopology options from the connect call. I would double check the URI env variable is correct and that the function can actually reach the cluster. Also it’s usually best to cache the connected client in the initialization phase as we describe here: https://www.mongodb.com/docs/atlas/best-practices-connecting-from-vercel/. I’d also check the default timeout of the function and maybe it needs more time for the connection phase. Another thing to potentially help debug is to listen to the monitor heartbeats and see if there is a potential issue there.
Since my last message, I’ve implemented the new Vercel integration but I’m experiencing the same issue. The MONGODB_URI produced automatically through the integration looks fine, but the connection hangs on await client.connect().
I’ve been stuck on this for months now and would really appreciate some help in identifying where the issue may come from!
Hey, I’m experiencing the same exact problem on the same exact place.
The weird thing in my case is that when I’m doing actions on my Front End that trigger a DB update, the connection is working perfect, I only have a DB connection problem when receiving Stripe’s events to my webhooks endpoint, and trying to connect to Mongo and update my DB.
I have tried Vercel’s Mongo integration, and all the tutorials above, same problem every time.
If anyone knows a solution for this problem, please help.
Vercel is serverless. Meaning that for each user that connects, they spin up a vm and kill it when the request is done (or 30 seconds). This means that your connect is not persisting to your pages.
Here’s my solution: <<see code below>>
Then you can make mongo calls with await mongoDb.collection(‘birds’, c=>c.findAll({}).toArray());
It works for form actions, but not for server actions. Will post a solution for server actions when I can find it.
It works for server actions. I just had a different database for localhost and vercel so my values weren’t being saved. Made the same edits in vercel hosted app and now they show up
class MongoDBClass {
uri: string;
constructor(uri: string | undefined) {
if (!uri) throw new Error("MONGODB_URI is not set in env.");
this.uri = uri;
}
connect() {
const client = new MongoClient(this.uri);
return client.connect().then(() => {
return client;
});
}
command<ReturnType>(callback: (client: MongoClient) => Promise<ReturnType>) {
let cmdClient: MongoClient;
return this.connect()
.then((client) => {
cmdClient = client;
return callback(client);
})
.finally(() => {
cmdClient.close();
});
}
collection<ReturnType, T extends Document = Document>(
collectionName: string,
callback: (collection: Collection<T>) => Promise<ReturnType>
) {
return this.command<ReturnType>((client) => {
const collection = client.db().collection<T>(collectionName);
return callback(collection);
});
}
}
export const mongoDb = new MongoDBClass(process.env.MONGODB_URI);
