Resolve Hostname/Service SSL Issues on CWP

If Let's Encrypt hasn't generated a certificate for your hostname in CWP, potential hostname SSL issues may arise from an incorrect or unconfigured hostname setting.

To resolve these issues, ensure that your server's hostname is accurately defined in CWP settings and that DNS records are correctly configured to point to the server's IP address.

In cases where Let's Encrypt hasn't issued a certificate, the absence of SSL for your hostname might affect services like email and secure connections. Therefore, verifying the hostname configuration and correcting any discrepancies is crucial to enable Let's Encrypt to issue a certificate, ensuring secure communications across your server.

Here, we cover the process of resolving hostname and/or service SSL certificate issues using Let's Encrypt AutoSSL, assuming it is already enabled in the Control Web Panel (CWP) admin panel.

Rerun AutoSSL

IMPORTANT: This solution will require root access. If this needs to be obtained, follow the guide on requesting root access.

1. Log into CWP Admin
2. Navigate to Server Settings
   
    
3. Click on Change Hostname
   
    
4. Ensure that the server's hostname is resolving to the server's IP address
   TIP: You should see SUCCESS in a green box.
   
5. Ensure that the correct hostname is reflected in the New Hostname field
   
6. Click on Change Hostname
   NOTE: This step will force-run Let's Encrypt AutoSSL for all CWP service SSLs, not just the default hostname.