# Installing a self-signed SSL certificate

> Generate and install a self-signed SSL certificate for testing or internal sites, and why browsers will warn about it.

Source: https://helpcenter.ruachost.com/ssl-security/ssl-certificates/installing-a-self-signed-ssl-certificate/

A **self‑signed SSL certificate** is an SSL certificate you generate yourself rather than purchasing from a Certificate Authority (CA). While it provides encryption, browsers will not automatically trust it, and visitors may see warnings. Self‑signed certificates are best used for **testing, staging, or internal projects**.

## Why Use a Self‑Signed SSL?

- Encrypts traffic between server and client.
- Useful for development or internal environments.
- No cost compared to CA‑issued certificates.

⚠️ Not recommended for production websites, as browsers will display “Not Secure” warnings.

## Steps to Install a Self‑Signed SSL Certificate

### 1. Generate the Certificate

1. **Log in to WHM.**
2. In the search box, type **SSL**.
3. Click **Generate an SSL Certificate and Signing Request**.
4. Fill in the required details:

   - Domain name
   - Company name and location
   - Email address
5. Select **Self‑Signed** instead of submitting to a CA.
6. WHM will generate:

   - ### Private Key
   - ### Certificate Signing Request (CSR)
   - ### Self‑Signed Certificate

### 2. Install the Certificate

1. In WHM, search for **Install an SSL Certificate on a Domain**.
2. Enter the domain name.
3. Paste the **Certificate**, **Private Key**, and (optional) **CA Bundle**.
4. Click **Install**.  The certificate is now active for that domain.

### 3. Verify Installation

- Visit your site using `https://`.
- You’ll see a browser warning (since the certificate is self‑signed).
- Confirm that the connection is encrypted despite the warning.

> **Note:**
- Self‑signed certificates are not trusted by browsers or visitors.
- For public websites, always use a CA‑issued SSL certificate.
- Self‑signed SSLs are ideal for testing environments or internal tools.

##