You can use bind your cPanel web server to a different port or
(better) you can put your services behind a reverse proxy/load
balancer. In this scenario, for web servers running on the standard
ports (ie TCP 80 and 443), you can use HTTP host headers/SNI to
redirect requests to the appropriate backend web server based on the
domain name used.
So yes, you can have a whole bunch of stuff running behind one public
IP address if you're willing to cope with the complexity. But
sometimes life is simpler if you can use more.
On Thu, Jul 19, 2018 at 4:45 PM Turritopsis Dohrnii Teo En Ming
<turritopsis.dohrnii@xxxxxxxxxxxxxxx> wrote:
>
> Good evening from Singapore,
>
>
> Is there any way I can deploy cPanel web hosting control panel with Microsoft Exchange 2016 groupware behind one static public IP? Or do I need 2 static public IP addresses at the minimum? With Exchange 2016 groupware taking up HTTP, HTTPS, IMAP, IMAPS, POP3, POP3S, SMTP, and SMTP/S ports, I personally don't think I can deploy cPanel behind the same public IP as Exchange.
>
>
> Please advise. Perhaps you have a brilliant idea. This is for experimental, testing and laboratory purposes.
>
>
> Thank you very much.
>
>
> ===BEGIN SIGNATURE===
>
> Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017
>
> [1] https://tdtemcerts.wordpress.com/
>
> <https://tdtemcerts.wordpress.com/>[2] http://tdtemcerts.blogspot.sg/
>
> <http://tdtemcerts.blogspot.sg/>[3] https://www.scribd.com/user/270125049/Teo-En-Ming
>
> <https://www.scribd.com/user/270125049/Teo-En-Ming>===END SIGNATURE===
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
