TLS should be enabled only after DNS for the hostname resolves to your Chapter22 web account. Let’s Encrypt via AutoSSL / cPanel “SSL/TLS Status” is the usual path.
Prerequisites
- Domain pointed to Chapter22.
- Apex and
wwwresolve to the correct IP from a public resolver. - Ability to serve HTTP on port 80 for HTTP-01 validation (default on shared web hosting).
Issue the certificate
- Log in to the client area and open cPanel (or the SSL tool linked on the service).
- Open SSL/TLS Status or AutoSSL.
- Select the domains/subdomains to include → Run AutoSSL / Issue.
- Wait for success, then visit
https://yourdomain.com.
Force HTTPS
In cPanel Force HTTPS Redirect, or add a canonical redirect in .htaccess only if you maintain custom rules carefully. Avoid redirect loops with existing force-SSL plugins.
Common failures
| Error pattern | Fix |
|---|---|
| DNS not pointing here | Correct A/NS; wait for TTL |
| CAA record blocks LE | Allow letsencrypt.org in CAA |
| Only www issued | Include apex on the cert |
| Mixed content | Update absolute http:// asset URLs |
Renewal
AutoSSL renews automatically on Chapter22 web hosting when DNS remains correct. After domain moves, re-run AutoSSL once.
Related guides
- How to Point Your Domain to Chapter22 Hosting
- How to Migrate Your Website to Chapter22 Hosting
- Web Hosting plans
Frequently Asked Questions
Certificate issuance failed with a connection error.
DNS probably does not point here yet, or port 80 is blocked. Verify the A record, then retry HTTP-01.
WWW works but the apex domain shows not secure.
Issue or include both yourdomain.com and www.yourdomain.com on the certificate, and redirect consistently.
Need help?
If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.
Build the server. Grow the community. Start your next chapter.