Binding an SSL certificate

Overview

After a SSL certificate has been installed in your account, it will need to be bound to the applicable domain (or domains) before your site will serve HTTPS. Adding a certificate to your account and binding it to a site are two separate steps.

Where the binding tool is

Log in to the Everleap Control Panel at cp.everleap.com.
From the top menu click Shared Sites.
On the Shared Cloud Sites Overview page, click Manage next to the applicable site.
On the Site Overview page, click the SSL tab.

The SSL tab for a site, showing the SSL Mode panel, the two steps to enabling HTTPS, the SSL SNI Bindings heading and the Add Binding section

The page reminds you of the two steps to enabling HTTPS on your site:

Add SSL certificates to your account in the Services then SSL Certificates section. Your options are to buy an SSL certificate, generate a CSR for an outside SSL vendor, or import an existing SSL certificate.
Bind the SSL certificate to the domain name for your site, using the tool on this page.

If no certificate is currently bound

Under Add Binding:

Select the applicable domain name from the Domain Name dropdown.
Select the SSL certificate from the Certificate dropdown.
Click Add Binding.

The Add Binding section with the Domain Name dropdown and the Certificate dropdown filled in, and the Add Binding button

The root domain, domain.com, and the www subdomain, www.domain.com, are two separate bindings. If you want both to serve HTTPS, add a binding for each.

If a certificate is already bound

If a SSL certificate has already been bound to the site, the existing binding (or bindings) will have to be deleted first before the new binding may be added.

The SSL SNI Bindings list showing existing bindings with the controls to delete them before a new binding can be added

This applies every time a new certificate is installed, including a renewal. A renewed certificate is a new certificate, so the old binding must be deleted and a new one added.

Verify It Worked

The new binding appears under SSL SNI Bindings. Browse to https:// followed by your domain name and confirm the browser shows the connection as secure, and that the certificate it reports is the one you just bound.

Notes

If your site uses IP-based SSL rather than SNI, adding the IP-based SSL add-on removes existing SNI bindings, and they must be added again afterwards. See The difference between SNI SSL and IP-based SSL.
Binding a certificate does not force visitors onto HTTPS. Traffic to http:// still works until you redirect it.

Article ID: 1621, Created: 2/27/2019 at 3:10 PM, Modified: 8/15/2026 at 9:26 PM