This guide explains how to allow certain incoming and/or outgoing ports in the firewall of a Web hosting or a Cloud Server.

Preamble

• On a shared Web hosting, it is only possible to open ports for outgoing traffic.
• On a Cloud Server, it is possible to open ports for inbound and outbound traffic.
• Opening ports ensures the proper functioning of certain applications but may decrease the security of your hosting.

Access the tool and add a rule

To manage port opening from the Manager:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the relevant product.
3. Click on Security in the left sidebar.
4. Click on Port Opening in the left sidebar.
5. Click on the Open a port button:
   

It is only possible to enter one IP address or host per line, and one port per rule.

By specifying an IP address or host, the connection will only be allowed in these cases:

• Incoming rule: if the connection comes from this IP or the indicated host
• Outgoing rule: if the connection is made to this IP or host

Same goes for the Typeof connection, if the protocol used for the connection is not the one indicated in the rule, the connection is not allowed.

Open outbound port 25 globally

You can open the outgoing port 25 from the manager if a destination host is specified.

With a Cloud Server, to open this port to the entire world, contact support Infomaniak and justify your request.

Default open ports

Once you have accessed the port opening tool, you will find the list of ports open by default on the page.

With a Cloud Server, to close some of the listed ports, contact support Infomaniak and justify your request.

The display may sometimes span multiple pages:

MySQL Ports

Regarding database ports, refer to these guides:

• Database access from another hosting
• Connect a Cloud Server to an external database
   

Check the activity of a port (Cloud Server)

On a Cloud Server, to check if an application is listening on a particular port (1234 in the example below) and to know the name of the application in question, run in SSH:

netstat -anpe | grep "1234" | grep "LISTEN"