• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Vote Let's Encrypt support

WOuld you like to have free X509 certificate with Let's Encrypt initiative implemented with Plesk 12


  • Total voters
    56
It would be possible, I think, to accomplish this with an extension. I would be able to make a bash script to accomplish this, but, have not sat down to take the time looking into making an extension. I may initially create a bash script once letsencrypt.org releases their initial utilities. Perhaps someone that is more of a programmer and feels comfortable with the extension format and coding would want to collaborate to make this happen?
 
It would be possible, I think, to accomplish this with an extension. I would be able to make a bash script to accomplish this, but, have not sat down to take the time looking into making an extension. I may initially create a bash script once letsencrypt.org releases their initial utilities.

Their tools are already released: https://github.com/letsencrypt/letsencrypt
They are still in development, but they should be fine to use for developing a Plesk extension.

Additionally Let's Encrypt's root cert is now trusted by browsers and the beta test is running so it should be possible to start right now.
 
i would love to see that! Especially while their certificates are valid for only 90 days, and it would be a pain in the *** to renew them for 20 domains every two or so months.
 
i would love to see that! Especially while their certificates are valid for only 90 days, and it would be a pain in the *** to renew them for 20 domains every two or so months.
The software renews the certificates automatically, so where's the problem?
 
The software renews the certificates automatically, so where's the problem?

No problem. I think that's just an argument to support this integration - otherwise it might not work (depending on your server setup) to renew this all automatically.
 
IgorG - Feeling like a noob here, but how do we install it? The readme is a bit sparse.
When I try to add it through the Extensions panel, I get "Error: Unable to install the extension: Corrupted meta.xml file."
I cant see meta.xml anywhere in the project. Do we need to run the scripts manually?
 
Hi RicRuss,

please note, that this extension is not yet published for public usage. They are still working on it.

Hi Alban Staehli,

the Plesk Github is a place, where examples and developments are stored, so that contributors have a place where they are able to work together on a project. This plugin is in develeopment state and can't be used on a production server to be installed as an extension. As you can see at the github - release - page "https://github.com/plesk/letsencrypt-plesk/releases", there is no current release.

We are now testing a Plesk extension that allows users to create proper CA-signed SSL certificates issues by Let's Encrypt for their domains via one click:


As well, quoted from the dev - team - twitter - account ( https://twitter.com/Pleskdevelopers/status/667631874202845184 ) :
#Letsencrypt public beta on Dec 3, but our extension for 1-click SSL install already works on internal #Plesk builds


The extension will be published at https://ext.plesk.com/ and will be available on the extension catalogue from your Plesk Panel ( Home > Extensions ) , when it's published.
 
Thanks UFHH01 - With your quote above, the link to the releases actually has four releases listed. That is why I assumed it was good to go.
 
Hi RicRuss,

as mentioned, these are "developer" releases - you can see this with the file-names. Just be a bit patient... :)
 
FWIW, the answer to my question was to just upload the release and run "./letsencrypt-auto" from the shell.

With the public beta underway I have successfully configured some domains, and plan to slowly roll it out to a few more over the next week.
 
I have test it... simply brillant!!!!!!
The certificate is for 3 month, we will had to create it every 3 month? or automatically it will be renewed?
 
Last edited:
The following error occurred:
Let's Encrypt SSL certificate installation failed: Failed letsencrypt execution: 2015-12-04 19:55:13,186:WARNING:letsencrypt.cli:Root (sudo) is required to run most of letsencrypt functionality.
Failed authorization procedure. domain.tld (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://domain.tld/.well-known/acme-challenge/jdjtjdttdjdtjdtj-tdjjdt_jttjtjtdjtdjtjtjtjttj [IPv4]: 404
IMPORTANT NOTES:
- The following 'urn:acme:error:unauthorized' errors were reported by
the server:

Domains: domain.tld
Error: The client lacks sufficient authorization
 
Last edited:
Liwindo... the domain must be visible.. make sure .htaccess files are not interrupting access.. and make sure the domain is not going through cloud flare or similar.
 
Back
Top