- Setup VPC peering between Qovery & Atlas with https://www.mongodb.com/docs/atlas/security-vpc-peering/
- Deployed application
- Verified it’s successfully running
- Cloned environment into the same cluster, not modifying anything
- Cloned env fails with
{"message":"connection timed out","name":"MongoNetworkTimeoutError"}
Hi @Andreas_Asprou,
One thing that you can do to check if the problem is coming from your app or AWS is:
- Connect to one of your instances from this environment with
qovery shell
command. - Install
telnet
ornetcat
client on this running instance (you may have a package manager like apt installed) - Try to open a TCP socket with
telnet
ornetcat
. E.gtelnet <your mongodb host> <your mongodb port>
Potential answers
- You successfully initiate a TCP connection with the MongoDB instance from your container: Then it means that the issue is coming from your application.
- If the
telnet
ornetcat
command returns anetwork time out
error: Then it means that the issue is coming from the network side (VPC Peering misconfiguration?) - If the
telnet
ornetcat
command returns aconnection reset
error: Then it is an issue on the MongoDB server side. You are better to contact MongoDB Atlas support to see what’s going on.
Can you show me the response from your telnet
or netcat
command?