This article is a WikiHow and the links lead directly to the source https://fr.wikihow.com/installer-un-certificat-SSL.
There are 4 methods to install an SSL certificate on a server:
1. Using Apache
2. Using Microsoft Internet Information Services (IIS)
4. Using cPanel
SSL certificates are used by websites to ensure encrypted and secure information exchanges between them and their clients. They also serve to verify that you are indeed connected to the desired service (for example, that you are connecting to your email service and not a fraudulent clone). If you own a website that requires a secure connection, you might want to install an SSL certificate to ensure its trustworthiness.
Read on to learn how to do this and follow detailed steps:
Read the WikiHow article - How to install an SSL certificate
Help with installing an SSL certificate on cPanel
You can learn more about the procedure by reading the cPanel documentation page.
Known issues you might encounter:
These common issues are extracted from this troubleshooting cPanel documentation page
1. Certificate and Key Mismatch
Occurs when the private key doesn’t match the SSL certificate.
Effect: Apache won’t start with SSL.
Fix: Check that the certificate and private key pair correctly (they must have the same modulus). If they don’t, use the correct private key for that certificate.
2. Dedicated IP Address Issues
Without SNI enabled, only one SSL certificate can be used per IP address.
Effect: A subdomain or secondary domain may fail to serve its SSL properly.
Fix: Assign a dedicated IP or enable SNI on the server.
3. Certificate Mismatch Warnings
The certificate shown by the browser does not match the site’s domain.
Effect: Browser warnings even if the certificate is technically installed.
Cause: Likely wrong certificate for the domain or a self-signed certificate being used.
Fix: Ensure the SSL certificate matches the domain name.
4. Domain Mismatch Warnings
The certificate’s domain name and the actual domain do not match.
Effect: Browser error indicating the certificate is not valid for that domain.
Fix: Use a certificate that exactly matches the requested domain.
5. Self-Signed Certificates
Self-signed certificates are not trusted by browsers because they are not signed by a trusted Certificate Authority (CA).
Effect: Visitors see browser security warnings.
Fix: Install a CA-signed SSL certificate instead of using the self-signed one.
6. Shared Certificate Conflicts
When multiple sites share one IP address and only one has SSL installed, non-SSL sites might not work via HTTPS.
Effect: Other sites on the same IP may show errors when accessed with HTTPS.
Fix: Install proper SSL on each domain or configure the server to use the hostname certificate.
7. System Failures
Severe system problems (e.g., drive failures) can corrupt or remove SSL data.
Effect: SSL certificates might stop working or be lost.
Fix: Restore SSL information from backups if available.
Checking your certificate / website:
You can verify your website’s security, as well as SSL data and your certificate installation here:
Digicert: SSL Tools DigiCert / Website Security Tools
TBS Test SSL: Check your certificate installation with CO-PIBOT
Sectigo (formerly Comodo CA) SSL Checker: Check your SSL certificate installation with SSL Checker
Qualys SSL Labs: SSL Server Test