A different port for ispCP

[macbishop]

Eminos Wrote:What it the benefit of running the CP at a different port ?

1.To independ the service of the panel that web pages
2.To separate the panel traffic that web content traffic*
3.Separate URL web content and URL panel for any domain hosted
http://domain
http://domain:xxx
4.Possibility that create Iptables rules that involve only the ispCP service panel

* If the port is ex.: 384 it would be good to add in add_rules() function in /etc/init.d/ispcp_network
the lines:

Code:

# ispcp
    
    ${IPTABLES} -I ISPCP_INPUT -p tcp --dport 384 2>> "${LOGDIR}/ispcp_network.err.log"
    ${IPTABLES} -I ISPCP_OUTPUT -p tcp --sport 384 2>> "${LOGDIR}/ispcp_network.err.log"

and create the code to see in the gui.

Raphael Wrote:without running it with an other httpd? playing with the config files (ouch, that ain't a benefit at all)

It's only a howto not obligation anyone !
I think that can be positive in future releases this isn't for this time
--
querer es poder