Facebook
Twitter
Sysop
Basic Pleskian
I've been trying to figure out the proper way to secure the Plesk Panel (https://mypleskpanel.com:8443) while allowing my other domains such as (https://myotherdomain.com:8443) or (https://anotherdomain.com:8443) to be properly secured as well while using the Plesk Panel.
The issue that arises is that if https://mypleskpanel.com:8443 is secured using a letsencrypt certificate then for example https://myotherdomain.com:8443 shows an invalid certificate because there's apparently some redirect to https://mypleskpanel.com:8443. If I do the opposite and tell the Plesk Panel to use https://myotherdomain:8443 certificate then it's valid, but everything else will show as invalid, including https://mypleskpanel.com:8443 ... so as you can see I'm a bit confused on what the proper way to actually do this is...
* I did notice some type of plug-in available in the Plesk Extensions catalog that appears to direct all domains to the main Plesk Panel url, although it's in Russian so I'm not sure whether I should use that or not seeing as how I'm not fluent in Russian.
The issue that arises is that if https://mypleskpanel.com:8443 is secured using a letsencrypt certificate then for example https://myotherdomain.com:8443 shows an invalid certificate because there's apparently some redirect to https://mypleskpanel.com:8443. If I do the opposite and tell the Plesk Panel to use https://myotherdomain:8443 certificate then it's valid, but everything else will show as invalid, including https://mypleskpanel.com:8443 ... so as you can see I'm a bit confused on what the proper way to actually do this is...
* I did notice some type of plug-in available in the Plesk Extensions catalog that appears to direct all domains to the main Plesk Panel url, although it's in Russian so I'm not sure whether I should use that or not seeing as how I'm not fluent in Russian.
