cPanel & WHM Version 94 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!
This object is in archive! 

Allow binding of cPanel & WHM to a specific IP address so we can use port 80 and 443 directly with cPanel & WHM

rainboy shared this idea 7 years ago
Open Discussion

Due to more and more changes in corporate firewalls as well as changes of limiting ports at ISPs it becomes more and more important to be able to access the 'cPanel' features over the normal ports (80 or preferable port 443). We understand cPanel & WHM is running on its own daemon I would like to see a option to bind that daemon to a specific IP address on the server which can only be used for this specifically (cPanel, WHM, Webmail) so that users do not have ports open in the >2000 range.


A secondary IP would give the ability to run a secondary webserver as is done by cPanel & WHM and allow it to use to otherwise occupied ports like 443 for SSL.


[Modified for clarity]

Comments (7)

photo
1

To be clear, cPanel & WHM do not rely upon Apache for providing any of its functionality. The cpsrvd daemon functions as the main cPanel & WHM, and bears little in common with Apache.

photo
2

Kenneth, my mistake, still it would be great if its possible as the reason why does not change :)

photo
1

Have voted because this is an interesting idea but I do have a question, what would this achieve that apache proxy would not do ?

photo
1

monarobase wrote:

Have voted because this is an interesting idea but I do have a question, what would this achieve that apache proxy would not do ?
This would allow the server admin to lock down access to cPanel & WHM at the firewall, without impacting access to Apache. Granted you can already do that, however I believe locking cpsrvd to a specific IP address could simplify firewall rules, and make them more understandable.

photo
3

We need 443 instead of a proxy to offer real SSL access with a valid certificate.

Currently the Proxy only allows port 80 which is not sufficient

photo
3

I agree - we need to be able to proxy over 443.

photo
1

Has there been any action on getting 443 working with proxy subdomains? Any workarounds? The non-standard ports being the only option for SSL access to cPanel continues to cause us regular headaches and we'd very much like to push everything towards SSL-only connections but this always holds us back. Does the SNI Support feature solve any of that?

Leave a Comment
 
Attach a file