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

Let's Encrypt permission via Service Plan not working

Boindil

New Pleskian
TITLE:
Let's Encrypt permission via Service Plan not working​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk 17.5.3 Update #43
‪CentOS Linux 7.4.1708 (Core)
Let's Encrypt Addon 2.5.3-354
​
PROBLEM DESCRIPTION:
When adding a subdomain, a Checkbox is shown that allows the customer to add a Let's Encrypt certificate.

Since one can set the behaviour of Let's encrypt being available per Service Plan to None, the customer should not be able to do this.​
STEPS TO REPRODUCE:
Add subdomain as customer of a subscription that is assigned to a Service plan, that has set the additional Service Let's encrypt to None.​
ACTUAL RESULT:
User is able to select Let's Encrypt for new subdomains.​
EXPECTED RESULT:
The customer should not get the Option to add Let's encrypt.​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out​
 
Back
Top