• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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