#Can you help to whitelist an ip to connect to old database?
1 messages · Page 1 of 1 (latest)
You will not need IP whitelisting for data migration.
Simply provide the data to the agent, and the agent will add it to the preview database. Once this is done, fork the session and use the Replace Deployment option with a fresh database.
This will ensure that all the updated preview data is reflected correctly in the deployed database.
If you need any further assistance during this process, feel free to connect to support : [email protected]
But apart from redeploy to same instance as we want to make sure the new environment is all working as expected after deployment like blue green deployment we should deploy parallely a new instance and have connected to same prod database to make sure its all working as expected. is there any way to migrate the database to new db instance? that will help us. or anyway to connect to mondo db to connect and backup? without having a view of mongo its difficult for any product we build.
Hey,
You can create a new instance in parallel and connect it to the same database, and it should work fine. Yes, you can also migrate the database—just provide all the required details to the agent and proceed with a replace deployment using a fresh database.
You can view the deployed app data as needed during this process. If you need any further assistance, feel free to reach out to our support team at [email protected].
MongoDB Atlas IP Whitelist: The main issue is that your MongoDB Atlas cluster is rejecting connections from Emergent's servers.
Go to MongoDB Atlas Console → Your Cluster → Network Access
Click "Add IP Address"
Either:
Add 0.0.0.0/0 (Allow from anywhere) - easiest but less secure
Or contact Emergent support to get their Kubernetes cluster IP ranges
To Deploy:
Update MongoDB Atlas IP whitelist (above)
Click Deploy button
Wait for deployment (~10-15 min)
see it asks for whitelist as the connection is unstable. without having access to mongo db datbase how to do it. neither emrgent agent nor the user can do these kind of things which is limiting the next steps for my app.
Without the IP whitelist fix, the deployment will keep failing with MongoDB timeouts.