Port 27017 closed for security reasons

[Stennie_X (Stennie)]

@Tayyab_Ferozi

When I open the terminal in my hosted server’s cPanel and type:
curl portquiz.net:27017
I am getting this:

[webnappc@s312 ~]$ curl portquiz.net:27017
curl: (7) Failed connect to portquiz.net:27017; Connection refused
[webnappc@s312 ~]$

Hi @Tayyab_Ferozi,

Your original error suggests outbound access to port 27017 is blocked by your hosting provider or instance firewall. Since that is a more straightforward issue to troubleshoot via portquiz.net, I would use it as a test case to resolve with your provider before trying to get your database connection working.

Once you have confirmed that outbound connections are not blocked, I would then test with the mongo shell and make sure you are able to login before trying to debug connectivity from your application code.

If you have temporarily opened up your Atlas IP Access List to allow any host to connect (that isn’t recommended for long term configuration), any remaining connection issues should be local to your environment (network/firewall configuration, or perhaps the driver/application version you are trying to connect with).

@Tayyab_Ferozi

Unfortunately, we cannot open ports. However, we can whitelist your specific IP address for either inbound or outbound.

A possible interpretation is that they are asking for the IP of the ventralIP instance you want to whitelist for outbound connections. I would ask them how to get your curl example working.

I think it would be unusual for hosts to aggressively block outbound connections without providing an interface for you to self-manage common firewall rules. Does your hosting include cPanel or a similar management interface?

@Tayyab_Ferozi

Thanks, but I found out that the node’s IP address may change when something changes on the server, this way I have to ask my hosting providers to outbound IP again and again.

That is correct (and expected behaviour). For the most robust access, you should rely on cluster names rather than IPs.

@Tayyab_Ferozi

And one more thing, do I need to whitelist IPs for outbound only? or inbound whitelisting is also required.

As noted by @chris, connections to Atlas are only outbound from your deployment.

Regards,
Stennie