Skip to main content
The Wizard is the front door of the SSL/TLS Certificates tool. The flow was rebuilt by cPanel: pick the domains you want on the certificate, the Wizard validates each one via an HTTP challenge, then you pick the product (Let’s Encrypt, on Noxity hosting) and the cert is issued. Open it from cPanel home → Security → SSL/TLS Certificates → Wizard (default tab).
SSL/TLS Wizard with the domain checklist and Continue button

Wizard tab with the domain list and Continue button at the bottom

​
What the Wizard does

In one flow:
  1. You tick the domains you want on the certificate.
  2. cPanel validates each one via HTTP-based Domain Control Validation (the file-on-server test that confirms the A record points at this account).
  3. Domains that pass show a green Validated via HTTP-based Domain Control Validation badge. Domains that fail show a reason.
  4. You click Continue with the validated domains, pick the product (Let’s Encrypt), and submit.
  5. cPanel installs the issued cert on every selected domain automatically.
You don’t need to handle CSRs, key pairs, or Apache config. The Wizard is the easy path.

​
Issue a Let’s Encrypt certificate

1

Tick the domains

Each domain on your account appears in the list, plus its www, mail, webmail, cpanel, cpcalendars, cpcontacts, webdisk, and autodiscover subdomains. Tick every variant you want covered. For a typical site, that’s the bare domain and www.Wildcards (*.yourdomain.com) appear in the list too. Wildcards on Let’s Encrypt require DNS-based validation, which Noxity AutoSSL handles automatically when the domain is on our DNS.
2

Wait for validation

cPanel runs the HTTP challenge in the background. Each domain that passes shows the green Validated via HTTP-based Domain Control Validation pill.
Validated via HTTP-based Domain Control Validation badge
Domains that fail show a reason: DNS not pointing here, the validation file couldn’t be served, or a redirect interferes. Fix the underlying issue (usually DNS) and re-run.
3

Click Continue

The bottom of the page shows a summary count of selected domains and a Continue button. Click it.
4

Pick Let's Encrypt as the product

A product picker opens. On Noxity hosting, you’ll see Let’s Encrypt Certificate as the only option (basic, free certs). Click Let’s Encrypt Certificate.
Let's Encrypt Certificate product card
5

Resolve any final issues

The last screen surfaces any remaining problems with the request (a domain you ticked that since lost validation, a rate-limit warning from Let’s Encrypt, etc.). Address them and submit.
6

Done

cPanel issues the cert, installs it on every domain in the request, and the green padlock in the Status tab flips on.

​
What “validated via HTTP” actually checks

cPanel writes a small file at http://yourdomain.com/.well-known/acme-challenge/<token>. The Let’s Encrypt server fetches that URL. If the file is served (status 200, correct contents) the domain is validated. What can break this:
  • The domain’s A record doesn’t point at your Noxity server. AutoSSL can’t validate a domain that resolves elsewhere.
  • A redirect rule rewrites /.well-known/acme-challenge/... (some .htaccess HTTPS-force rules do this). Bypass /.well-known/ in the rule.
  • A WordPress plugin is intercepting the path. Disable the plugin during issuance.
  • Cloudflare proxy is on with Always Use HTTPS plus an SSL mode that rejects the challenge. Pause Cloudflare proxy on the domain or use the Cloudflare-mode AutoSSL.

​
When to use the Wizard vs other tabs

  • Wizard for free Let’s Encrypt certs on domains hosted with us. The default and the easy path.
  • Requests if you bought a paid cert (DigiCert, Sectigo, GoDaddy) and need to generate a CSR to send to the CA.
  • Certificates to upload the issued paid cert once you receive it.
  • Installation to deploy an uploaded cert onto a domain.

​
Common issues

The domain’s A record points somewhere other than your Noxity server (often Cloudflare, sometimes a previous host). Either point DNS here, or use a CNAME-based validation (open a ticket).
A previous cert with the same domains is locked by another part of the system. Open a ticket; we can clear the lock.
Let’s Encrypt rate-limits issuance to 50 certs per registered domain per week, and 5 duplicate certs per week. If you’ve been re-issuing in a loop, wait an hour and try again. For repeated production issues, open a ticket.
The bare domain has a different A record (or no A record at all). DNS first, validation second.

​
Need a hand?

Open a ticket

Best for anything that needs an account check or a config change on our end.

Live chat

Faster for quick questions during business hours.