5 months ago
On attempting to connect to my atlas cluster I receive the error below. I upgraded to the pro plan and added IP address to mongodb's network access. Are there any other settings I need to adjust to connect to my atlas cluster.
Connection: MongooseServerSelectionError: Could not connect to any servers in your MongoDB Atlas cluster. One common reason is that you're trying to access the database from an IP that isn't whitelisted. Make sure your current IP address is on your Atlas cluster's IP whitelist.
20 Replies
5 months ago
Hi there, did you redeploy after setting the static IP?
The Static IP will only be used by your service after the next deploy
Status changed to Awaiting User Response railway[bot] • 5 months ago
unicodeveloper
Hi there, did you redeploy after setting the static IP?The Static IP will only be used by your service after the next deploy
5 months ago
Hi! Yes I redeployed many times hoping to find the cause.
Status changed to Awaiting Railway Response railway[bot] • 5 months ago
5 months ago
Interesting. Can you whitelist 0.0.0.0/0 on MongoDB Atlas and then try again?
Status changed to Awaiting User Response railway[bot] • 5 months ago
5 months ago
Hi, Yes sorry. I should have said that on whitelisting 0.0.0.0/0 the connection is allowed. I have applied the settings as you suggest and it does again connect but obviously this is not a solution.
Status changed to Awaiting Railway Response railway[bot] • 5 months ago
5 months ago
Okay, let's try something else. Can you disable and re-enable the static IP?
Status changed to Awaiting User Response railway[bot] • 5 months ago
5 months ago
Disabling and re-enabling has no effect.
Status changed to Awaiting Railway Response railway[bot] • 5 months ago
5 months ago
Hi there, I am escalating to the team internally to understand why this is not working as expected. I'll get back to you on details soon.
Status changed to Awaiting User Response railway[bot] • 5 months ago
5 months ago
Thank you, much appreciated.
Status changed to Awaiting Railway Response railway[bot] • 5 months ago
5 months ago
Quick one, I can see that the static IP is in us-west while your service is in eu-west. When did you make the switch of your service region to eu-west?
Status changed to Awaiting User Response railway[bot] • 5 months ago
5 months ago
Hi, How odd. Yes I did.
Status changed to Awaiting Railway Response railway[bot] • 5 months ago
5 months ago
When please? We have a developing theory but it will be nice to know when you made the switch.
Status changed to Awaiting User Response railway[bot] • 5 months ago
5 months ago
As soon as I upgraded. It was the 1st thing I did.
Status changed to Awaiting Railway Response railway[bot] • 5 months ago
5 months ago
Thanks, will pass on to the team
Status changed to Awaiting User Response railway[bot] • 5 months ago
5 months ago
We just pushed a fix. Please can you toggle static IPs off and on again?
5 months ago
It still will not connect via the eu region but if I change it to us Oregon it will. Ideally it would work across all regions but this will do. Thank you for your help.
Status changed to Awaiting Railway Response railway[bot] • 5 months ago
5 months ago
Okay, we will investigate it further. Happy you are able to get it to work now.
Status changed to Awaiting User Response railway[bot] • 5 months ago
4 months ago
Can someone get the outbound ip if they are not using the pro plan?
Status changed to Awaiting Railway Response railway[bot] • 4 months ago
Status changed to Awaiting User Response railway[bot] • 4 months ago
unicodeveloper
We just pushed a fix. Please can you toggle static IPs off and on again?
4 months ago
I am experiencing same issue and it is frustating
Status changed to Awaiting Railway Response railway[bot] • 4 months ago
datacoupon
I am experiencing same issue and it is frustating
4 months ago
Hobby users do not have static IPs, you would need to instead whitelist 0.0.0.0/0 in Atlas.