• 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.

Issue Plesk 8443 and domain

Minato

New Pleskian
Hi guys,

My domain aws.rogerioit.com is pointing to Plesk control panel and it is working fine with Lets Encrypt.

My hostname is: aws.rogerioit.com
https://100001.onl/ https://1921681254.mx/


I can access plesk at
https://aws.rogerioit.com:8443

So I tried to create a domain with the same name like hostname aws.rogerioit.com

The domain above was created successfully but when I try to access it I got certificate error message in the browser

My question is: can I use aws.rogerioit.com:8443 to access plesk and aws.rogerioit.com to my website?

Help me please
 
normally you do it the other way around: first create your website & secure it with letsencrypt, then tell plesk to use that certificate for the plesk panel on 8443.
 
Back
Top