Question Panel-Port for management Node

[Martin.B]

As I read it, the management node for Plesk Multiserver can't contain any accounts or websites itself.
So is it possible to deactivate Apache & Nginx on the management node and reconfigure the Plesk-Panel (via /etc/sw-cp-server/conf.d/plesk.conf) to listen to Ports 80/443?

 

[craigueH]

This would be great as it would simplify logins for customers accessing their hosting CP.

 

[Anthony]

Hi @Martin.B,

So is it possible to deactivate Apache & Nginx on the management node and reconfigure the Plesk-Panel (via /etc/sw-cp-server/conf.d/plesk.conf) to listen to Ports 80/443?

No, it isn't. You can deactivate nginx but you can't deactivate Apache which serves Plesk panel itself. The panel is used for centralized customers login.
Another reason is that port 8443 is hard-coded for Multi Server redirections from service nodes to the management node.

 

[craigueH]

How about having the panel listen on both 443 and 8443?
Then customers could easily login via plain old HTTPS but the server nodes can all communicate as normal over :8443

It would be nice to to have this for security reasons too so we could firewall off :8443 to just internal servers and only open HTTPS port to end users for login to the CP.
Plus it would make the whole setup look more robust and not look just like a bunch of ordinary Plesk servers hobbled together.

 

[Anthony]

Hi @craigueH,

How about having the panel listen on both 443 and 8443?

Check this article https://kb.plesk.com/en/1694

 

[craigueH]

That'll do nicely

 

[craigueH]

Just tried this guide but it seems outdated for Plesk 17 Onyx. Have you a link to an updated version of this guide?

 

[Anthony]

Hi @craigueH,

You can this article https://support.plesk.com/hc/en-us/articles/213945625
But I have no time to make sure will it applicable to Multi Server or not.

In our case, a subscription will be created on a service node and all customers will be redirected from the service node to a management node using nginx proxy_pass.