A TLS certificate turns http into https and shows the padlock in the browser. The certificate has to sit on whatever answers HTTPS for your site, and on Gewape Cloud that is your server.
Where the certificate goes
Load balancers on Gewape Cloud pass encrypted traffic straight through without decrypting it, so they do not use certificates. Install the certificate on each server that answers HTTPS:
- One server: the quickest way is the free certificate that renews itself. See Turn on HTTPS (free certificate).
- Several servers behind a load balancer: install the certificate on every target server. See Create a load balancer.
Keep a copy in the console
TLS/SSL Certificates keeps a certificate and its private key encrypted in the console, so your team has one safe place to find them. It does not install the certificate anywhere.
- In the console menu open TLS/SSL Certificates and click Create Certificate.
- Choose the type:
- Server (cert + key): a certificate for your website or service.
- Client CA (cert only): the certificate authority you use to check your clients' certificates.
- Fill in:
- Name: for example
www-cert. - Certificate (PEM): paste the certificate, followed by its intermediate (chain) certificates. It starts with
-----BEGIN CERTIFICATE-----. - Private key (PEM): for a server certificate, paste the matching private key. It starts with
-----BEGIN PRIVATE KEY-----. - Domain(s) (optional): the names it covers, for example
example.com, www.example.com.
- Name: for example
- Click Import certificate.
Renewals
A certificate you bought expires on a fixed date. Replace it on every server before then, or visitors see security warnings. The free certificate renews itself.