Skip to main content
    Installation Guide
    Linux
    Windows

    How to Install SSL Certificate on Plesk

    Complete step-by-step guide to install SSL certificates on Plesk for both Linux and Windows servers. From CSR generation to HTTPS configuration—everything you need for a secure website.

    My-SSL Security Team
    Updated December 2025
    22 min read

    Before You Begin

    This guide covers Plesk installation on both Linux (Apache/Nginx) and Windows (IIS) servers. Use our free CSR Generator for maximum security and control. Have your Plesk login credentials ready.

    Linux or Windows?

    This guide covers both platforms. Most steps are identical—the main differences are noted in Steps 4-5 (uploading certificates) and the troubleshooting section. Windows additionally supports PFX/PKCS#12 certificate import.

    Introduction to Plesk SSL Installation

    Plesk is one of the world's leading web hosting control panels, trusted by millions of server administrators on both Linux and Windows platforms. Its powerful SSL/TLS Certificates module makes securing websites straightforward, whether you're managing a single domain or hundreds of sites across multiple servers.

    In this comprehensive guide, you'll learn the complete process of installing SSL certificates on Plesk—from generating a Certificate Signing Request (CSR) using our free CSR Generator tool to verifying your installation with our SSL Checker. We'll cover both Linux (Apache/Nginx) and Windows (IIS) servers, troubleshoot common errors, configure HTTPS redirects, and share best practices for ongoing SSL management.

    Understanding how SSL works is fundamental to web security. SSL certificates encrypt connections between visitors' browsers and your server, protecting sensitive data like login credentials, payment information, and personal details. With Google using HTTPS as a ranking factor and browsers displaying "Not Secure" warnings, SSL is essential for every website.

    Plesk supports multiple SSL certificate types including DV SSL certificates for quick validation, OV SSL certificates for business verification, and EV SSL certificates for maximum trust. This guide works with all Plesk versions including Obsidian and Onyx.

    What You'll Need Before Starting

    Before beginning the SSL installation process on Plesk, ensure you have these prerequisites ready:

    Prerequisites Checklist

  1. Plesk Panel Access: Administrator or customer login credentials to your Plesk dashboard
  2. Domain Configured: Your domain must be added to Plesk and DNS pointing to your server
  3. SSL Certificate Files: Either a CSR for ordering a new certificate, or your issued certificate files
  4. Private Key: The private key generated alongside your CSR (keep this secure!)
  5. CA Bundle: The intermediate/chain certificate from your Certificate Authority
  6. If you haven't purchased an SSL certificate yet, browse our SSL certificates to find the right option for your needs. We offer certificates from trusted CAs with prices starting at just $2.99/year.

    Linux vs Windows: Key Differences

    AspectLinux (Apache/Nginx)Windows (IIS)
    Web ServerApache or NginxIIS
    Certificate FormatPEM (text-based)PEM or PFX/PKCS#12
    Config Location/etc/apache2 or /etc/nginxIIS Manager
    Service RestartApache/Nginx auto-restartIIS auto-restart
    Import OptionsPaste or uploadPaste, upload, or PFX import

    Step 1: Generate CSR Using My-SSL Tools

    The first step in obtaining an SSL certificate is generating a Certificate Signing Request (CSR). While Plesk has a built-in CSR generator, we recommend using our free CSR Generator tool for better control and the ability to save your private key securely.

    How to Generate a CSR

  7. Navigate to the CSR Generator: Visit our CSR Generator tool
  8. Enter Your Common Name (CN): This is your fully qualified domain name (FQDN)
  9. - For a standard certificate: example.com (automatically covers www.example.com)

    - For a wildcard certificate: *.example.com

    - For a subdomain: shop.example.com

  10. Fill in Organization Details:
  11. - Organization Name: Your legal business name

    - Organizational Unit: Department (e.g., "IT Department")

    - City/Locality: Your city

    - State/Province: Full state name (not abbreviated)

    - Country: Two-letter country code (e.g., US, GB, DE)

    - Email: Contact email for certificate management

  12. Add Subject Alternative Names (SANs): For multi-domain certificates, add additional domains
  13. Select Key Size: Choose 2048-bit (standard) or 4096-bit (maximum security)
  14. Generate and Save: Click "Generate CSR" and save both the CSR and Private Key
  15. Critical: Your private key is generated locally in your browser and never transmitted to any server. Store it securely—you'll need it during installation, and losing it means you'll need to regenerate the CSR and reissue your certificate.

    For a complete walkthrough of all our tools, see our Complete Guide to Free SSL Certificate Tools.

    Step 2: Order Your SSL Certificate

    With your CSR ready, you can now order your SSL certificate. The type of certificate you choose depends on your website's needs:

  16. **DV SSL Certificates**: Domain validation only, issued in minutes, ideal for blogs and personal sites
  17. **OV SSL Certificates**: Organization validation, displays company name, suitable for businesses
  18. **EV SSL Certificates**: Extended validation, highest trust level, recommended for e-commerce
  19. Ordering Process

  20. Choose Your Certificate: Select the appropriate SSL type and validity period
  21. Submit Your CSR: Paste the CSR generated in Step 1
  22. Complete Domain Validation: Verify domain ownership via:
  23. - Email validation (sent to admin@yourdomain.com)

    - DNS validation (add a CNAME or TXT record)

    - HTTP validation (upload a file to your server)

  24. Download Certificate Files: Once validated, download your certificate files
  25. Your certificate package typically includes:

  26. Main certificate file (.crt or .pem)
  27. CA Bundle / Intermediate certificate (.ca-bundle or chain.crt)
  28. Root certificate (often included in CA Bundle)
  29. For detailed information on validation types, read our guide on SSL Certificate Types.

    Step 3: Access Plesk SSL/TLS Settings

    Now that you have your certificate files, it's time to install them in Plesk. The steps are similar for both Linux and Windows, with slight interface variations.

  30. Log into Plesk: Access your Plesk panel (typically at yourdomain.com:8443 or server-ip:8443)
  31. Select Your Domain: From the left menu, click "Websites & Domains"
  32. Find SSL/TLS Option: Look for "SSL/TLS Certificates" under your domain
  33. - In Plesk Obsidian: Click directly on "SSL/TLS Certificates"

    - In older versions: May be under "Hosting Settings" or "Security"

  34. Overview of SSL/TLS Manager: You'll see options to:
  35. - Add SSL/TLS Certificate (upload new certificate)

    - View existing certificates

    - Manage Let's Encrypt certificates

    - Configure certificate settings

    For Windows IIS Servers

    The interface is nearly identical on Windows Plesk. The main difference is the backend handling—Plesk automatically manages IIS bindings when you assign certificates.

    Step 4: Add SSL Certificate in Plesk (Linux)

    For Linux servers running Apache or Nginx, follow these steps to upload your SSL certificate.

    Method 1: Upload Certificate Files

  36. Click "Add SSL/TLS Certificate" in the SSL/TLS Certificates section
  37. Enter a Certificate Name: Use a descriptive name like "mydomain-2025" for easy identification
  38. Upload or Paste Private Key:
  39. - Locate the "Private key" field

    - Paste your entire private key including headers:

    ```

    -----BEGIN RSA PRIVATE KEY-----

    [Your private key content]

    -----END RSA PRIVATE KEY-----

    ```

  40. Upload or Paste Certificate (CRT):
  41. - Locate the "Certificate" field

    - Paste your SSL certificate including headers:

    ```

    -----BEGIN CERTIFICATE-----

    [Your certificate content]

    -----END CERTIFICATE-----

    ```

  42. Upload or Paste CA Certificate (CA Bundle):
  43. - Locate the "CA certificate" field

    - Paste the complete intermediate/chain certificate

    - This may contain multiple certificates—include all of them

  44. Click "Upload Certificate": Plesk will validate and store the certificate
  45. Method 2: Upload Files Directly

    Instead of pasting text, you can use the file upload option:

  46. Click "Browse" next to each field
  47. Select the corresponding .key, .crt, and .ca-bundle files
  48. Click "Upload Certificate"
  49. Important: Use our Key Matcher tool to verify your private key matches your certificate before uploading.

    Step 5: Add SSL Certificate in Plesk (Windows/IIS)

    For Windows servers running IIS, you have additional options including PFX/PKCS#12 import.

    Method 1: Upload Certificate Files (Same as Linux)

    Follow the same steps as the Linux installation—paste or upload your private key, certificate, and CA bundle.

    Method 2: Import PFX/PKCS#12 File

    If you have a .pfx file (common for Windows certificates):

  50. Click "Add SSL/TLS Certificate"
  51. **Scroll to "Upload certificate as *.pfx file"**
  52. Browse and Select Your PFX File
  53. Enter the PFX Password: This is the password used when exporting the certificate
  54. Click "Upload Certificate": Plesk will extract the private key and certificates from the PFX
  55. Tip: If you need to convert between formats, use our Certificate Converter tool. It can convert PEM to PFX and vice versa for free.

    Verifying Your Certificate Details

    After uploading, use our Certificate Decoder tool to verify:

  56. Common Name matches your domain
  57. Validity period is correct
  58. Issuer is your expected Certificate Authority
  59. Subject Alternative Names include all domains
  60. Step 6: Assign Certificate to Domain

    After uploading, you need to assign the certificate to your domain's hosting.

    For Both Linux and Windows

  61. Return to Websites & Domains: Click on your domain name
  62. Click "Hosting Settings" (or "Hosting & DNS" > "Hosting Settings")
  63. Locate the Security Section:
  64. - Find "SSL/TLS support" or "Security" section

    - You'll see a "Certificate" dropdown

  65. Select Your Certificate: Choose the certificate you just uploaded from the dropdown
  66. Enable SSL/TLS Support: Ensure the checkbox is enabled
  67. Configure Additional Options:
  68. - Permanent SEO-safe 301 redirect from HTTP to HTTPS: Enable this for automatic redirects

    - HSTS (HTTP Strict Transport Security): Enable for enhanced security (optional)

  69. Click "Apply" or "OK": Plesk will configure the web server
  70. What Happens Behind the Scenes

    On Linux (Apache):

  71. Plesk updates the Apache virtual host configuration
  72. Adds SSLCertificateFile, SSLCertificateKeyFile, and SSLCertificateChainFile directives
  73. Restarts Apache automatically
  74. On Linux (Nginx):

  75. Plesk updates Nginx server block configuration
  76. Configures ssl_certificate and ssl_certificate_key directives
  77. Restarts Nginx automatically
  78. On Windows (IIS):

  79. Plesk imports certificate to Windows Certificate Store
  80. Creates HTTPS binding on port 443
  81. Associates certificate with the website in IIS
  82. Step 7: Verify Your SSL Installation

    After installation, verify everything is working correctly on both Linux and Windows.

    Verification Steps

  83. Visit Your Website: Navigate to https://yourdomain.com
  84. Check for Padlock: A padlock icon should appear in the browser address bar
  85. No Browser Warnings: The page should load without security warnings
  86. View Certificate Details: Click the padlock to view:
  87. - Issued to: Your domain name

    - Issued by: Your Certificate Authority

    - Valid dates: Current date within validity period

  88. Test with SSL Checker: Use our SSL Checker tool for comprehensive verification:
  89. - Certificate chain validation

    - Expiration date check

    - Protocol support

    - Common issues detection

    Linux-Specific Verification

    Check Apache/Nginx configuration:

    # For Apache
    apachectl -t
    systemctl status apache2
    
    # For Nginx
    nginx -t
    systemctl status nginx

    Windows-Specific Verification

  90. Open IIS Manager
  91. Select your site > Bindings
  92. Verify HTTPS binding on port 443 shows your certificate
  93. Configure HTTPS Redirect in Plesk

    After installing SSL, redirect all HTTP traffic to HTTPS for security and SEO benefits.

  94. Go to Websites & Domains > Your Domain
  95. Click "Hosting Settings"
  96. Enable "Permanent SEO-safe 301 redirect from HTTP to HTTPS"
  97. Click "Apply"
  98. This is the recommended method as Plesk handles it automatically for all web servers.

    Method 2: .htaccess Redirect (Linux Apache)

    For Apache servers, add to your .htaccess file:

    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

    Method 3: Nginx Directives (Linux Nginx)

    In Plesk, go to your domain > Apache & nginx Settings > Additional nginx directives:

    if ($scheme = http) {
        return 301 https://$host$request_uri;
    }

    Method 4: web.config (Windows IIS)

    For IIS with URL Rewrite module, add to web.config:

    <rule name="HTTP to HTTPS redirect" stopProcessing="true">
      <match url="(.*)" />
      <conditions>
        <add input="{HTTPS}" pattern="off" ignoreCase="true" />
      </conditions>
      <action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />
    </rule>

    Common Plesk SSL Errors & Troubleshooting

    Even with careful installation, you may encounter errors. Here's how to resolve the most common issues on both platforms:

    Error: "The certificate does not match the private key"

    Cause: The private key doesn't correspond to the CSR that generated the certificate.

    Solution:

  99. Use our Key Matcher to verify the key-certificate pair
  100. If they don't match:
  101. - Generate a new CSR using our CSR Generator

    - Request certificate reissuance from your CA

    Error: "SSL handshake failed" or "Certificate not trusted"

    Cause: Usually a missing or incorrect CA bundle.

    Solution:

  102. Verify you've included the complete CA bundle
  103. Download the correct intermediate certificates from your CA
  104. Re-upload with the proper chain
  105. Use our Certificate Decoder to check certificate details.

    Error: "Browser shows 'Not Secure' despite SSL"

    Cause: Mixed content—your HTTPS page loads resources over HTTP.

    Solution:

  106. Use browser Developer Tools (F12) > Console to identify HTTP resources
  107. Update all internal URLs to HTTPS
  108. Use relative URLs or protocol-relative URLs where possible
  109. Linux-Specific Issues

    IssueCauseSolution
    Apache won't restartSSL config syntax errorRun `apachectl -t` to check syntax
    Nginx proxy errorBackend certificate issueCheck upstream SSL settings
    Permission deniedWrong file permissionsSet 644 for certs, 600 for keys
    SELinux blockingSecurity policyRun `restorecon` on cert files

    Windows-Specific Issues

    IssueCauseSolution
    Port 443 in useAnother site using portCheck IIS bindings
    PFX import failedWrong password or formatUse Certificate Converter
    IIS binding errorCertificate store issueRe-import to store
    App Pool crashIdentity permissionsGrant read access to cert

    Certificate Not in Dropdown

    If your certificate doesn't appear in the hosting settings dropdown:

  110. Verify the private key matches the certificate
  111. Re-upload the certificate
  112. Check for any error messages during upload
  113. Use our CSR Decoder to verify CSR details
  114. Setting Up SSL Expiry Reminders

    SSL certificates expire after 1-2 years. Avoid unexpected expiration with our free reminder service.

    How to Set Up Reminders

  115. Visit our SSL Checker tool
  116. Enter your domain and run the check
  117. After viewing results, enter your email address
  118. Choose notification timing (1, 3, 7, 14, 30, 60, or 90 days before expiry)
  119. Click "Subscribe"
  120. You'll receive email notifications before your certificate expires, giving you time to renew and avoid security warnings.

    Plesk Let's Encrypt vs Purchased SSL Certificates

    Plesk includes a Let's Encrypt extension for free SSL certificates. Here's how it compares to purchased certificates:

    FeatureLet's Encrypt (Free)Purchased SSL
    **Cost**FreeFrom $2.99/year
    **Validity**90 days (auto-renews)1-2 years
    **Validation Level**DV onlyDV, OV, or EV
    **Warranty**NoneUp to $1.75 million
    **Wildcard Support**Requires DNS challengeFull support
    **Business Trust**BasicHigh
    **Auto-Renewal**Yes (via extension)Manual
    **Support**Community24/7 professional

    When to Choose Purchased SSL

  121. E-commerce websites: Warranty protection and higher trust
  122. Business websites: OV/EV validation displays company name
  123. Multiple subdomains: Wildcard certificates are more reliable
  124. High-traffic sites: Better support and uptime guarantees
  125. Compliance requirements: Some regulations require specific certificate types
  126. Learn more about choosing the right certificate in our SSL Certificate Types guide.

    Installing Wildcard SSL on Plesk

    Wildcard SSL certificates secure your main domain and all single-level subdomains (e.g., *.example.com covers shop.example.com, blog.example.com, etc.).

    Wildcard Installation Steps

  127. Generate Wildcard CSR: Use our CSR Generator with Common Name as *.example.com
  128. Order Wildcard Certificate: Purchase from our pricing page
  129. Upload to Plesk: Follow the standard upload process
  130. Assign to Multiple Domains: In Plesk, you can assign the same wildcard certificate to:
  131. - The main domain

    - All subdomains

    - New subdomains added later

    Wildcard on Linux vs Windows

    Both platforms handle wildcard certificates identically. The only consideration is ensuring all subdomains are configured in Plesk before assigning the certificate.

    Best Practices for Plesk SSL Management

    Follow these best practices to maintain optimal SSL security on your Plesk server:

    Regular Monitoring

  132. Check certificate status monthly using our SSL Checker
  133. Set up expiry reminders for all certificates
  134. Monitor for any browser security warnings
  135. Review server logs for SSL errors
  136. Security Measures

  137. Use 2048-bit or 4096-bit key sizes
  138. Never share or email private keys
  139. Store backup copies of certificates securely
  140. Use unique certificates per domain when possible
  141. Enable HSTS for enhanced security
  142. Plesk-Specific Tips

  143. Keep Plesk updated for SSL improvements and security patches
  144. Use the Let's Encrypt extension for auto-renewal on non-production sites
  145. Review hosting settings after Plesk updates
  146. Test SSL configuration after any server changes
  147. Use Plesk's built-in SSL/TLS checker for quick verification
  148. Documentation

  149. Document all certificate details (issuer, expiry, domains)
  150. Keep records of renewal dates
  151. Maintain a log of SSL-related changes
  152. Note private key storage locations
  153. For a deeper understanding of certificate infrastructure, read our guide on What is PKI?.

    Looking for other control panel installation guides? Check out our cPanel SSL Installation Guide for step-by-step instructions on cPanel servers.

    Frequently Asked Questions

    How long does it take to install SSL on Plesk?

    The technical installation takes just 5-10 minutes once you have all the necessary files. The entire process including CSR generation, certificate ordering, and domain validation typically takes 15-30 minutes for DV certificates, or 1-5 business days for OV/EV certificates.

    Can I install a free SSL certificate on Plesk?

    Yes, Plesk includes a Let's Encrypt extension that provides free DV certificates with automatic 90-day renewal. However, for business use, warranty protection, or extended validation, consider our affordable SSL certificates.

    What's the difference between Plesk SSL installation on Linux vs Windows?

    The Plesk interface is nearly identical on both platforms. The main differences are: Windows supports PFX/PKCS#12 import, Linux uses Apache/Nginx while Windows uses IIS, and Windows manages certificates through the Certificate Store.

    Why is my SSL certificate not showing in the dropdown?

    This usually means the private key doesn't match the certificate. Use our Key Matcher to verify, and re-upload if necessary. Also check for any error messages during the upload process.

    How do I renew an SSL certificate in Plesk?

    Renewal follows the same process as initial installation: generate new CSR, order renewal certificate, and install. Most CAs offer a renewal option that preserves remaining validity.

    What is a CA Bundle and do I need it for Plesk?

    A CA Bundle contains intermediate certificates that link your SSL to a trusted root CA. Without it, browsers may not trust your certificate. Always install the CA bundle provided by your Certificate Authority.

    Can I install multiple SSL certificates on one Plesk server?

    Yes, Plesk supports multiple certificates. Each domain can have its own certificate, or use multi-domain (SAN) or wildcard certificates to cover multiple domains.

    How do I install a Wildcard SSL on Plesk?

    Wildcard installation follows the same process. Ensure your CSR Common Name uses the wildcard format (*.example.com). Then assign the certificate to your main domain and all subdomains in Plesk.

    Why does my browser show "Not Secure" after installing SSL on Plesk?

    This usually indicates mixed content—your HTTPS page loads some resources over HTTP. Use browser Developer Tools to identify and fix HTTP resources.

    How do I convert a certificate for Windows Plesk (IIS)?

    Use our Certificate Converter to convert between PEM and PFX formats. For PFX, you'll need both the certificate and private key.

    What's the difference between Let's Encrypt and purchased SSL in Plesk?

    Let's Encrypt is free but limited to DV validation and 90-day validity. Purchased certificates offer longer validity, OV/EV options, warranties up to $1.75M, and professional support.

    How do I install SSL for subdomains in Plesk?

    Each subdomain can have its own certificate or share a wildcard certificate. Add the subdomain in Plesk, then install/assign the certificate following this guide.

    Recommended

    Ready to Secure Your Plesk Server?

    Get your SSL certificate and complete the installation

    DV SSL Certificate

    Starting at From $2.99/year/year

    • Quick Issuance
    • 99.9% Browser Trust
    • Free Reissues
    Browse SSL Certificates

    Plesk Let's Encrypt vs Purchased SSL Certificates

    FeatureLet's Encrypt (Free)Purchased SSL
    CostFreeFrom $2.99/year
    Validity90 days (auto-renews)1-2 years
    Validation LevelDV onlyDV, OV, or EV
    WarrantyNoneUp to $1.75 million
    Wildcard SupportRequires DNS challengeFull support
    Business TrustBasicHigh
    Auto-RenewalYes (via extension)Manual
    SupportCommunity24/7 professional
    Recommended

    Need Enterprise-Grade Security?

    Upgrade to organization or extended validation certificates

    OV & EV SSL Certificates

    Starting at From $29/year/year

    • Organization Validation
    • Company Name Display
    • $1.75M Warranty
    View Business Certificates

    Don't Let Your SSL Expire!

    Set up free email reminders before your certificate expires. Get notified 30, 14, or 7 days in advance to avoid any security warnings for your visitors.

    Set Up SSL Reminders