HTTPS protects communication between a browser and the server it connects to using TLS. It limits interception and modification of data in transit. This is useful for public pages as well as forms and signed-in areas.
A valid certificate lets the browser check the server's identity for the requested name. It does not guarantee that the website's content is trustworthy, that its application has no vulnerabilities or that data stored on the server is encrypted.
Check the certificate and renewal process
- Covered names: check every address used, including variants with and without www and any required subdomains.
- Validity: the certificate must be valid, trusted by the intended browsers and served with the required intermediate chain.
- Renewal: confirm the method, responsible person and handling of failures. Configured automation must still be able to complete domain validation.
If available in your cPanel interface, SSL/TLS Status shows certificate status. After DNS changes, a site move or a proxy change, have issuance and renewal requirements checked again.
Move the application to HTTPS
- Keep a recoverable backup of files, the database and configuration before changing addresses or redirects.
- Test the HTTPS address before forcing HTTP traffic to redirect.
- Configure application addresses and redirection using the tools appropriate to the service. If a CDN or proxy is involved, also check its connection to the origin server to avoid loops or an unencrypted connection.
- Correct mixed content: an HTTPS page can still request images, scripts or other resources over HTTP. Check their availability over HTTPS and update the references in the application.
- Test important pages, forms, sign-in and integrations, then check errors reported by the browser.
Free or commercial certificate?
A trusted free certificate, such as those issued by Let's Encrypt, can establish HTTPS. A paid certificate is not required solely to encrypt traffic. The choice depends on covered names, automation, organizational-validation requirements and support needs. Have the options appropriate to your service confirmed.
Keep supported TLS settings and do not ask visitors to bypass a certificate warning. To plan the change, use your Nuagerie Client Area and identify the domains and any intermediary services involved.
