HelioHost Wiki
  • Home
  • Hosting
    • What is HelioHost?
    • What HelioHost Offers
    • What HelioHost is Not
    • What is HelioNet?
    • Signing up
    • Why Was My Account Suspended?
    • Repair Times
    • Terms of Service
  • Accounts
    • International Countries
    • Moving Your Account
    • Suspension Policy
    • Donations for Increased Storage
  • Plesk and Management
    • How to Access Plesk
    • Uploading Files
    • Creating MySQL Databases via Plesk
    • Changing Your Main Domain
    • Addon Domains
    • Subdomains
    • Parked (Alias) Domains
    • Using SSL
  • Tutorials
    • VPS
      • Installing NGINX
      • Installing WordPress on Hestia
      • Setting up Email on Hestia
    • Discord Bot
    • Django
      • Django on HelioHost
      • Converting an Existing Django App
    • Flask
    • Golang as CGI
    • Node.js
      • Next.js
      • Express.js
    • Perl
    • Plesk
      • Account Backups
      • Viewing Error Logs
      • Cron Jobs / Scheduled Tasks
      • Password Protect a Directory
      • Create a Website
    • Python
    • Ruby on Rails
    • DNS Record Management
      • External DNS Hosting
        • Cloudflare
      • HelioHost DNS Records
        • Google Site Verification
        • Manage HelioHost DNS
  • Common Errors
    • open_basedir restriction
    • SSL Certificate Problems
    • 504 Gateway Timeout
    • Mail Delivery Problems
    • PostgreSQL Database Creation Error
    • PostgreSQL Database Remote Connection Error
    • phpMyAdmin / MariaDB Access Denied Error
    • Linux Case Sensitivity
    • Could Not Spawn Process for Application
    • Supported Browsers
  • FAQ
  • Servers
    • Physical
      • Annie
      • Charlie
      • Eddie
      • Sparkie
      • Stevie
    • Virtual
      • Johnny
      • Tommy
      • Morty
      • Brody
      • Cody
      • Lily
  • Features
    • .NET / .NET Core / Classic ASP
    • Plesk
    • Java / JSP
    • PHP
    • PostgreSQL
    • Python
    • Node.js
    • Softaculous
    • SQLite
    • Storage
    • Unlimited Bandwidth
    • Unlimited Email Accounts
  • Miscellaneous
    • Clear Your Cache
    • WordPress
    • Contributing to the Wiki
      • Code Style
    • Server Load and Uptime
    • How You Can Help
    • Staff
      • Ashoat
      • Krydos
      • Wolstech
Powered by GitBook
On this page
  • Installing a Let's Encrypt SSL Certificate
  • Navigate to the Let's Encrypt Settings
  • Install the Certificate
  • Select Certificate Options
  • Troubleshooting
  • Check if the Certificate is Expired or Invalid
  • If the Certificate is NOT Expired
  • Further Support

Was this helpful?

  1. Common Errors

SSL Certificate Problems

Previousopen_basedir restrictionNext504 Gateway Timeout

Last updated 2 months ago

Was this helpful?

Installing a Let's Encrypt SSL Certificate

Navigate to the Let's Encrypt Settings

  1. Navigate to the Let's Encrypt settings using the steps below:

Login > Plesk > Websites & Domains > [ domain ] > Dashboard tab > Security section> SSL/TLS Certificates button > Let's Encrypt settings

Install the Certificate

  1. Click on the Install button.

Select Certificate Options

  1. In addition to selecting the Secure the domain name option, we also recommend selecting the following options:

  • Include a "www" subdomain for the domain and each selected alias

  • Secure webmail on this domain

  • Assign the certificate to the mail domain

Note: Securing webmail cannot be done during the 2 hours following domain creation, because it requires an Apache restart. Apache restarts every 2 hours, so if you're setting up SSL on a brand new account or a new domain that's just been added, you will need to return to these settings later to activate the webmail security feature.

  1. Click on the Get it free button to install the certificate.

  1. You should see that Keep websites secured is now Enabled

We also recommend activating the Redirect from http to https option

Troubleshooting

If you have issues with the Let's Encrypt SSL certificate on your domain or subdomain, here are some things to check:

Check if the Certificate is Expired or Invalid

If the certificate is expired or invalid:

  • Reissue the certificate

  • Wait a full 2 hours

  • Clear your cache to ensure the changes are applied correctly

If the Certificate is NOT Expired

If the certificate is not expired:

  • Unassign the certificate from the domain

  • Reassign the certificate to the domain

  • Wait a full 2 hours

  • Clear your cache to ensure the changes are applied correctly

Further Support

If after following the above steps, waiting a full 2 hours, and clearing your cache, the problem is not fixed, please post a topic in the Customer Support forum. Make sure you provide your username, domain name, and any applicable error message(s) received.