Tweet
As you know a shared hosting environment can be insecure if you leave open ports and most of the servers already have a CSF or Imunify360 installed with non used ports closed. Sometimes clients ask to run nodejs or ruby on specific ports, other than 80/443 but leaving other ports open and have control over them (for example the client tested a nodejs on port 11300 and then dorpped it and you have that port open now...you cant track every open port by users request every day). So will be great auotomate this with the nodejs or ruby server start/stop action, so when the user start the server and select a non default port, open the port, and then if they stop the server, automaticaly close that port. Also will be great in the admin side a field to specify the port range that they can use, so you can control a port range for this.