• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Question Various 8443 let's encrypt domain on one server

S

sebgonzes

Silver Pleskian
I know how to protect panel access with let's encrypt, but also want to know if it's possible to protect more domain with this port in plesk? We have a few user that use they own domain to access to panel ( https://www.mydomain.com:8443 ) and they don't understand the unsecure message sometime...

It's possible to do it?
 
You must log in or register to reply here.

Similar threads

learning_curve
Forwarded to devs SSL It! / Let's Encrypt installs incomplete Generation Y RSA certificate chain (YR1/YR2 → Root YR) without Root YR cross-sign to ISRG Root X1
Replies
4
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
D
Forwarded to devs SSL It! / Let's Encrypt DNS-01 challenge remains permanently "Pending" – TXT records created successfully but challenge is never confirmed
Replies
3
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
kristobal1969
Resolved Error messages with let's Encrypt when 1 serveur for main domain and another serveur for subdomain or mails
Replies
12
Views
7K
NataliaA
N
K
Resolved Plesk Obsidian – Let’s Encrypt certificate does not include domain aliases in SAN
Replies
7
Views
6K
kicoes
K
T
Question Let's Encrypt SSL certificate issuance on new subdomain take too long
Replies
2
Views
7K
tertek
T
Back
Top