• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question SSL error https://52.***.***.***:8443/

Anirudh

New Pleskian
Can someone please give me a step by step guide to remove ssl error for plesk web server backend?

I am using Plesk on Azure VM.
 
Well you can still access Plesk with non secured port with the port 8880 instead of 8443 . However that is not recommended.

Regarding the SSL error you get its because the SSL certificate is self signed so no need to worry about it.
 
Bad idea. It would be much better if you protect your Plesk Admin interface with the certificate from built-in LetsEncrypt extension instead of default self signed certificate.
 
Bad idea. It would be much better if you protect your Plesk Admin interface with the certificate from built-in LetsEncrypt extension instead of default self signed certificate.
How? I don't need see Full hostname in LetsEncrpt
 
Back
Top