[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"doc-en-lets-encrypt-ssl-certificate-plesk":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":21,"docGroup":28,"docGroupIcon":28,"link_fr":29,"bodyHtml":30},"\u002Fdocs\u002Fen\u002Fcloud\u002Fhebergement-web\u002Flets-encrypt-ssl-certificate-plesk","lets-encrypt-ssl-certificate-plesk","How to Generate a Let's Encrypt SSL Certificate for Your Website","Generate a free Let's Encrypt SSL certificate for your website on Winheberg Plesk web hosting, www and mail options, HTTPS redirect, automatic renewal and wildcard certificate.","cloud","hebergement-web","tabler:file-text","2026-11-01","Winheberg",132,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Flets-encrypt-ssl-certificate-plesk.webp",[16,17,18,19,20],"SSL","Let's Encrypt","Plesk","HTTPS","Web Hosting",[22,23,24,25,26,27],"free ssl certificate","let's encrypt plesk","https website","plesk ssl certificate","wildcard ssl","browser padlock","","\u002Fdocs\u002Fhebergement-web\u002Fcertificat-ssl-lets-encrypt-plesk","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>An SSL certificate encrypts the traffic between your website and its visitors. Without one, browsers display &quot;Not secure&quot; in front of the address, and contact or login forms travel over the network in clear text.\u003C\u002Fp>\n\u003Cp>On your \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fcloud\u002Fweb-hosting\">Winheberg web hosting\u003C\u002Fa>, the Plesk panel issues free Let&#39;s Encrypt certificates, a certificate authority trusted by every browser. Plesk also takes care of their renewal, so you only do this once per domain.\u003C\u002Fp>\n\u003Cp>This guide covers the certificate request, what it protects, the HTTPS redirect check, subdomains and the most common errors.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The Winheberg Plesk panel is displayed in French. Menu, field and button names are quoted below exactly as they appear on screen, followed by their English meaning.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A Winheberg web hosting plan with access to the Plesk panel\u003C\u002Fli>\n\u003Cli>A domain added in Plesk and already pointing to your hosting, see our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fconnect-external-domain-plesk\">How to Connect an External Domain to Your Plesk Hosting\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>For a wildcard certificate, a domain that uses the Winheberg name servers\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M12 22c5.523 0 10-4.477 10-10S17.523 2 12 2 2 6.477 2 12s4.477 10 10 10z\"\u002F>\u003Cpath d=\"M12 8v4\"\u002F>\u003Cpath d=\"M12 16h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>Let&#39;s Encrypt checks that the domain points to your hosting before issuing the certificate. A request sent during DNS propagation fails, so wait until your domain leads to your hosting before starting.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>1. Open the domain certificates\u003C\u002Fh2>\n\u003Cp>In \u003Cstrong>Sites Web &amp; Domaines\u003C\u002Fstrong> (\u003Cem>Websites &amp; Domains\u003C\u002Fem>), open your domain. In the \u003Cstrong>Tableau de bord\u003C\u002Fstrong> (\u003Cem>Dashboard\u003C\u002Fem>), \u003Cstrong>Sécurité\u003C\u002Fstrong> (\u003Cem>Security\u003C\u002Fem>) section, the \u003Cstrong>Certificats SSL\u002FTLS\u003C\u002Fstrong> (\u003Cem>SSL\u002FTLS Certificates\u003C\u002Fem>) entry shows \u003Cstrong>Domaine non protégé\u003C\u002Fstrong> (\u003Cem>Domain not secured\u003C\u002Fem>) as long as no certificate is installed. Click it.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Flets-encrypt-ssl-certificate-plesk-1793567738430-27828c00861486a3721b9914.webp\" alt=\"SSL\u002FTLS Certificates entry in the domain Security section\" width=\"420\" \u002F>\n\n\u003Ch2>2. Start the Let&#39;s Encrypt request\u003C\u002Fh2>\n\u003Cp>Scroll down to \u003Cstrong>Plus d&#39;options\u003C\u002Fstrong> (\u003Cem>More options\u003C\u002Fem>), then click \u003Cstrong>Installer\u003C\u002Fstrong> (\u003Cem>Install\u003C\u002Fem>) under \u003Cstrong>Installer un certificat basique gratuit fourni par Let&#39;s Encrypt\u003C\u002Fstrong> (\u003Cem>Install a free basic certificate provided by Let&#39;s Encrypt\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Flets-encrypt-ssl-certificate-plesk-1793567834147-bb4b8d33f24945eb3227d145.webp\" alt=\"Install a free basic certificate provided by Let's Encrypt option in Plesk\" width=\"520\" \u002F>\n\n\u003Ch2>3. Choose what the certificate protects\u003C\u002Fh2>\n\u003Cp>Plesk opens the \u003Cstrong>Certificat SSL\u002FTLS Let&#39;s Encrypt\u003C\u002Fstrong> window of your domain. Tick at least \u003Cstrong>Sécuriser le nom de domaine\u003C\u002Fstrong> (\u003Cem>Secure the domain name\u003C\u002Fem>) and \u003Cstrong>Inclure un sous-domaine &quot;www&quot; pour le domaine et chaque alias sélectionné\u003C\u002Fstrong> (\u003Cem>Include a &quot;www&quot; subdomain for the domain and each selected alias\u003C\u002Fem>), so your website answers over HTTPS with and without \u003Ccode>www\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Flets-encrypt-ssl-certificate-plesk-1793572335535-1d3c5fdc266f733b6e639490.webp\" alt=\"Let's Encrypt certificate options and Get it free button in Plesk\" width=\"700\" \u002F>\n\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Options of the Let's Encrypt window\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Option\u003C\u002Fth>\n\u003Cth>What it protects\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Sécuriser le nom de domaine (\u003Cem>Secure the domain name\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The domain itself, \u003Ccode>example.com\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Protéger le domaine Wildcard (\u003Cem>Secure the wildcard domain, including www and webmail\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>Every direct subdomain, such as \u003Ccode>blog.example.com\u003C\u002Fcode>, see step 5\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Inclure un sous-domaine &quot;www&quot; (\u003Cem>Include a &quot;www&quot; subdomain\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The \u003Ccode>www.example.com\u003C\u002Fcode> address and the \u003Ccode>www\u003C\u002Fcode> of each ticked alias\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Protéger la messagerie Web sur ce domaine (\u003Cem>Secure webmail on this domain\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The webmail, \u003Ccode>webmail.example.com\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Sécuriser la messagerie sur ce domaine (\u003Cem>Secure mail on this domain\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The \u003Ccode>mail.example.com\u003C\u002Fcode> address\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Assigner le certificat au domaine de messagerie (\u003Cem>Assign the certificate to the mail domain\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>IMAP, POP and SMTP connections of your mail clients on this domain\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003Cdiv class=\"md-table__footer\">Example given for the domain example.com.\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>In \u003Cstrong>Méthode de validation du domaine\u003C\u002Fstrong> (\u003Cem>Domain validation method\u003C\u002Fem>), keep \u003Cstrong>HTTP\u003C\u002Fstrong>, a file on the website (http-01). Let&#39;s Encrypt then checks a temporary file that Plesk places on your website by itself. Then click \u003Cstrong>Obtenir gratuitement\u003C\u002Fstrong> (\u003Cem>Get it free\u003C\u002Fem>). Once the certificate is issued, Plesk installs it and assigns it to your domain.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>As the window states, the certificate is renewed automatically 30 days before its expiry date. There is nothing more to do as long as the domain points to your hosting.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>4. Check the HTTPS redirect\u003C\u002Fh2>\n\u003Cp>Open the \u003Cstrong>Hébergement et DNS\u003C\u002Fstrong> (\u003Cem>Hosting &amp; DNS\u003C\u002Fem>) tab of the domain, then the \u003Cstrong>Hébergement\u003C\u002Fstrong> (\u003Cem>Hosting\u003C\u002Fem>) entry, which shows the \u003Cstrong>Paramètres d&#39;hébergement\u003C\u002Fstrong> (\u003Cem>Hosting Settings\u003C\u002Fem>). In the \u003Cstrong>Prise en charge SSL\u002FTLS\u003C\u002Fstrong> (\u003Cem>SSL\u002FTLS support\u003C\u002Fem>) section, the \u003Cstrong>Certificat\u003C\u002Fstrong> (\u003Cem>Certificate\u003C\u002Fem>) field should now show your Let&#39;s Encrypt certificate instead of \u003Cstrong>Non sélectionné\u003C\u002Fstrong> (\u003Cem>Not selected\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Flets-encrypt-ssl-certificate-plesk-1793572335939-7200ab6fa1fc0b223c9c98c0.webp\" alt=\"HTTP to HTTPS redirect and certificate choice in the Plesk hosting settings\" width=\"700\" \u002F>\n\n\u003Cp>The \u003Cstrong>Rediriger les internautes de HTTP vers HTTPS via une redirection HTTP 301 respectueuse du SEO\u003C\u002Fstrong> (\u003Cem>Permanent SEO-safe 301 redirect from HTTP to HTTPS\u003C\u002Fem>) box is ticked and greyed out, it is enforced on our plans. All your visitors therefore switch to HTTPS without any setting on your side.\u003C\u002Fp>\n\u003Cp>Finally, open your website with \u003Ccode>https:\u002F\u002F\u003C\u002Fcode> in a browser, the padlock should appear in front of the address.\u003C\u002Fp>\n\u003Ch2>5. Protect your subdomains\u003C\u002Fh2>\n\u003Cp>Each subdomain added in Plesk has its own dashboard, with its own \u003Cstrong>Certificats SSL\u002FTLS\u003C\u002Fstrong> entry. For one or two subdomains, simply repeat steps 1 to 3 from each of them.\u003C\u002Fp>\n\u003Cp>To cover every subdomain at once, tick \u003Cstrong>Protéger le domaine Wildcard\u003C\u002Fstrong> in the Let&#39;s Encrypt window of the main domain. Let&#39;s Encrypt then only accepts \u003Cstrong>DNS\u003C\u002Fstrong> validation, a TXT record in the DNS zone (dns-01), which Plesk creates by itself when the zone is served by the Winheberg name servers.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-warning\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z\"\u002F>\u003Cline x1=\"12\" y1=\"9\" x2=\"12\" y2=\"13\"\u002F>\u003Cline x1=\"12\" y1=\"17\" x2=\"12.01\" y2=\"17\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>If your domain uses another provider&#39;s name servers, Plesk cannot publish the validation record and the wildcard certificate cannot be issued. Protect each subdomain separately with HTTP validation instead.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>Troubleshooting\u003C\u002Fh2>\n\u003Ch3>❌ The request fails with a validation error\u003C\u002Fh3>\n\u003Cp>Let&#39;s Encrypt could not reach your website at the requested address.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check that the domain leads to your hosting with \u003Ccode>dig +short A example.com @8.8.8.8\u003C\u002Fcode>, the address must be the \u003Cstrong>Adresse IP\u003C\u002Fstrong> (\u003Cem>IP address\u003C\u002Fem>) shown at the bottom of your domain page in Plesk\u003C\u002Fli>\n\u003Cli>Run the same check for \u003Ccode>www.example.com\u003C\u002Fcode> if you ticked the www option\u003C\u002Fli>\n\u003Cli>If an AAAA record exists for the domain, it must point to your hosting too, Let&#39;s Encrypt contacts the IPv6 address first\u003C\u002Fli>\n\u003Cli>If your domain goes through an external proxy, turn it off for the time of the request\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The browser still shows &quot;Not secure&quot;\u003C\u002Fh3>\n\u003Cp>The certificate is installed, but the page does not meet the browser conditions.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check that the certificate covers the visited address, a \u003Ccode>www\u003C\u002Fcode> address is only protected if the www option was ticked\u003C\u002Fli>\n\u003Cli>Look for resources loaded over \u003Ccode>http:\u002F\u002F\u003C\u002Fcode> in your pages, images, scripts or stylesheets, they are enough to lose the padlock\u003C\u002Fli>\n\u003Cli>Reload the page without cache with Ctrl+F5, or test from a private browsing window\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ Let&#39;s Encrypt rejects new requests\u003C\u002Fh3>\n\u003Cp>Let&#39;s Encrypt limits the number of requests accepted for the same domain over a given period, failures included.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Do not send the request over and over, first fix the cause of the failure with the first case above\u003C\u002Fli>\n\u003Cli>Wait a few hours before a new attempt if the rejection persists\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Always tick the www option, some of your visitors will type the address with it\u003C\u002Fli>\n\u003Cli>Protect the webmail too if you read your mail from the browser\u003C\u002Fli>\n\u003Cli>Keep the domain pointing to your hosting, each renewal goes through the same check\u003C\u002Fli>\n\u003Cli>Keep the wildcard for domains with many subdomains, one certificate per subdomain stays easier to follow\u003C\u002Fli>\n\u003Cli>Once the padlock shows, install your website with our guides \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fhost-wordpress-plesk\">How to Host a WordPress Website on Plesk\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fhost-laravel-plesk\">How to Host a Laravel Website on Plesk\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If the certificate will not issue although your domain points to your hosting, open a ticket with our support from your \u003Ca href=\"https:\u002F\u002Fbilling.winheberg.com\">client area\u003C\u002Fa>, \u003Cstrong>Technical\u003C\u002Fstrong> department, filling in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with the web hosting concerned. Mention the domain and the error message shown by Plesk.\u003C\u002Fp>\n\u003Cp>Your website shows its padlock, free of charge and with no renewal to watch 🔒\u003C\u002Fp>\n",1794526350980]