Hi @Ayberk_Cengiz,
Probably not related to your connectivity issue, but FYI you will need the same keyFile
configuration on your other replica set members.
Since you are on a private network, you may want to get basic networking working before enabling additional configuration.
The error message is about connectivity to the member you’re trying to add:
192.168.122.203:27017 failed with No route to host
As a start I would try to ping
and make sure your replica set members all have a known route to the other replica set member IPs.
Can you please provide some more details about your deployment:
-
Are you using the same config file for all replica set members?
-
Are the replica set members on different machines or are they VMs or containers on the same host?
-
Are there any firewalls that might be blocking communication between replica set members?
-
What O/S version are you using?
-
What specific version of MongoDB server are you using?
Thanks,
Stennie