Recent searches

in

Add an auto-generated SSL Certificate

Last modified: November 12th, 2026

On this page

Permissions required

Members of the Owners, Developers, and Partner Default Permission Groups, or Custom Permission Groups with the base-domain:settings:details:write permission, can change the HTTPS settings of a Subdomain.

Managing your SSL Certificate on CloudCannon requires you to host your Site through CloudCannon. If an external service hosts your Site, please review its documentation on SSL Certificates.

By default, CloudCannon issues an SSL Certificate for each Subdomain you host on CloudCannon, and renews it automatically, so your Site keeps a valid certificate. On CloudCannon Hosting and Cloudflare Proxy, Cloudflare issues the certificate that visitors see. CloudCannon also issues a certificate for its origin servers, which visitors see on Single Origin, and on your Base Domain on CloudCannon Hosting when your domain uses external DNS.

The certificate belongs to the Subdomain, so it covers every Site on that Subdomain. The HTTPS section of the Subdomain page shows whether HTTPS is on, what CloudCannon is waiting for, and what to do if something needs your attention. You can also redirect visitors who open the HTTP address of your website to the HTTPS address.

Before we begin, this article assumes you have added a Custom Domain to your Site, or added a subdomain to your Custom Domain.

To use an auto-generated SSL Certificate on a Subdomain:

  1. Log in to CloudCannon.
  2. Select the Organization your Custom Domain is connected to.
  3. Click the Custom Domains link in the App Sidebar. CloudCannon will open the Domains Browser.
  4. Click the Card for the domain to which you want to add a certificate. CloudCannon will open the Summary tab of the Domain page.
  5. Click the Subdomains tab. CloudCannon will open the list of Subdomains.
  6. Click the Card for the Subdomain to which you want to add the certificate. CloudCannon will open the page for that Subdomain.
  7. Click the Configure HTTPS button in the HTTPS section. CloudCannon will open the HTTPS for [Subdomain] modal.
  8. Select the Let CloudCannon issue and renew it option under SSL certificate.
  9. (Optional.) Check the Redirect http:// visitors to https:// checkbox under HTTP.
  10. Click the Save HTTPS button.

CloudCannon will request an SSL Certificate for the Subdomain once its DNS points at CloudCannon. Once the certificate is issued, the HTTPS section shows HTTPS is on and the date by which CloudCannon renews it.

A screenshot of the HTTPS for blog.example.com modal shows the Let CloudCannon issue and renew it option selected and labeled Recommended, the Use an SSL certificate you upload option, the Redirect http:// visitors to https:// checkbox under HTTP, the Minimum TLS version dropdown set to TLS 1.2, and the Save HTTPS button.
The HTTPS modal

New Subdomains use an auto-generated certificate by default, so you only need these steps to switch back from an uploaded certificate, or to change the HTTP redirect. You can also open the HTTPS section from the Custom Domain page under Site Settings. For the Minimum TLS version dropdown in the same modal, please read our documentation on increasing the minimum TLS version for your domains.

When you switch a Subdomain from an uploaded certificate to Let CloudCannon issue and renew it, CloudCannon requests its own certificate straight away. On Single Origin, visitors keep seeing the uploaded certificate until CloudCannon's certificate is issued, unless the uploaded certificate has already expired. If an uploaded certificate expires while a Subdomain still uses it, CloudCannon switches that Subdomain to Let CloudCannon issue and renew it within the hour. For more information on uploaded certificates, please read our documentation on adding a Custom SSL Certificate.

What the HTTPS section shows#

The HTTPS section of the Subdomain page explains the status of the certificate:

  • Waiting for DNS — The Subdomain's DNS record doesn't point at CloudCannon yet. HTTPS turns on by itself once it does, so there is nothing to do here. On Cloudflare Proxy, the section shows Waiting for your proxied record instead.
  • Waiting for nameservers — Your domain uses CloudCannon DNS, and its nameservers don't point at CloudCannon DNS yet. HTTPS turns on by itself once they do, so there is nothing to do here.
  • Turning HTTPS on — The Subdomain points at CloudCannon, and CloudCannon is requesting the certificate. This usually takes a few minutes.
  • HTTPS is on — The certificate is active. The section shows the date by which CloudCannon renews it, and whether visitors who open the http:// address land on https://.

Until HTTPS is on, visitors who open the https:// address see a security warning in their browser. If you are moving a live website to CloudCannon, you can issue the SSL Certificate with TXT validation before you switch DNS, so your visitors never see that warning.

If a certificate fails to issue or renew, the HTTPS section says why, and what to do next. For more information, please read our documentation on resolving SSL Certificate errors.

If a Subdomain on CloudCannon Hosting or Cloudflare Proxy doesn't point at CloudCannon within seven days of being set up, Cloudflare gives up on it, and CloudCannon sets the Subdomain up again. The HTTPS section says when CloudCannon set the Subdomain up again.

A screenshot of the HTTPS section for careers.example.com shows Waiting for DNS, a note that HTTPS turns on by itself once careers.example.com points at CloudCannon, and the Switch to TXT validation button.
The HTTPS section while waiting for DNS

How CloudCannon validates your certificate#

Before a certificate authority issues a certificate, it checks that you control the Subdomain, so that nobody else can get a certificate for your domain. How CloudCannon validates a certificate depends on the Subdomain's hosting, and on whether it is your Base Domain:

  • CloudCannon Hosting or Cloudflare Proxy — Cloudflare validates the certificate over HTTP once the Subdomain's DNS points at CloudCannon. CloudCannon answers the check itself, so you don't need to add any records.
  • Single Origin — CloudCannon validates the certificate itself once the Subdomain's DNS points at the CloudCannon origin. You don't need to add any records.
  • Your Base Domain — Your Base Domain (e.g., example.com) also gets a wildcard SSL Certificate, whatever its hosting. Cloudflare only validates wildcard SSL Certificates with TXT records.

The wildcard SSL Certificate covers subdomains you haven't set up yet (e.g., *.example.com), so visitors to them reach your Fallback Redirect over HTTPS. On CloudCannon DNS, CloudCannon adds its TXT records for you once your nameservers point at CloudCannon DNS. If the wildcard SSL Certificate needs renewing before then, CloudCannon emails the TXT records, and a CNAME record you can add instead, to everyone who can edit the settings of your Base Domain. Add them at your current DNS Provider. The DNS tab doesn't list them. For more information, please read the section on the email CloudCannon sends when the wildcard SSL Certificate needs renewing. On external DNS, visitors only reach those subdomains if you also add a wildcard DNS record (e.g., *.example.com) at your DNS Provider, which the DNS tab lists under Wildcard record (optional). You add the wildcard SSL Certificate's TXT records at your DNS Provider before each renewal, unless you add a CNAME record once that lets Cloudflare renew the certificate on its own. On CloudCannon Hosting with external DNS, visitors to your Base Domain itself reach CloudCannon's origin servers, which use their own certificate, validated over HTTP, so these records only affect the subdomains you haven't set up. For more information, please read the section on renewing the wildcard SSL Certificate on external DNS.

When your domain uses external DNS and your Base Domain is on CloudCannon Hosting, the HTTPS section of the Subdomain page for your Base Domain has an Other subdomains block, which shows the state of the wildcard SSL Certificate. The wildcard SSL Certificate is optional: your Base Domain and the Subdomains you have set up have their own certificates. Its records are on the DNS tab of the Domain page, rather than in the block. The block shows one of these states:

  • Setting up — CloudCannon is requesting the first wildcard SSL Certificate. Until it is issued, the DNS tab lists the TXT records it needs under Wildcard certificate records (optional), followed by the CNAME record that lets Cloudflare renew the certificate on its own.
  • HTTPS on — The wildcard SSL Certificate is active. The block shows when it renews. Until CloudCannon finds the CNAME record that lets Cloudflare renew the certificate on its own, each renewal needs two TXT records, and the block has a Make it renew by itself with a CNAME record link to the DNS tab, where you can add that record instead. Once CloudCannon finds it, the block shows that the certificate renews by itself. For more information, please read the section on letting Cloudflare renew the wildcard SSL Certificate on its own.
  • Action needed before [Date] — A renewal needs new TXT records at your DNS Provider. The block has a View the wildcard certificate records link to the records on the DNS tab. For more information, please read the section on renewing the wildcard SSL Certificate on external DNS.
  • No HTTPS — The wildcard SSL Certificate was not renewed in time, so visitors to a subdomain you haven't set up see a security warning.
A screenshot of the HTTPS section for example.com on external DNS shows HTTPS is on with the next renewal date, and the Other subdomains block with HTTPS on, explaining that visitors to a subdomain that isn't set up reach the fallback over HTTPS and that the certificate needs two TXT records before each renewal, with a link to make it renew by itself with a CNAME record.
The HTTPS section for a Base Domain on external DNS

Issue the SSL Certificate with TXT validation#

When a Subdomain is already live somewhere else, moving its DNS record to CloudCannon before CloudCannon has its certificate leaves a short gap where visitors see a security warning. For a Subdomain on CloudCannon Hosting or Cloudflare Proxy, other than your Base Domain, on a domain that uses external DNS, you can validate the certificate with TXT records at your current DNS Provider instead. CloudCannon issues the certificate while your DNS still points at the old host, so the move causes less downtime.

To open the page for a Subdomain, click the Card for the Subdomain on the Subdomains tab of the Domain page.

Each TXT record shows a Copy icon next to its Name and Value, which copies it.

To issue the SSL Certificate with TXT validation, on the page for the Subdomain:

  1. Click the Switch to TXT validation button in the HTTPS section. CloudCannon will show the Issuing the SSL Certificate with TXT validation notice and the two TXT records to add.
  2. Add each record at your current DNS Provider, using the Name, Type, and Value shown.
  3. Wait until both records show Found.

CloudCannon will turn HTTPS on once Cloudflare finds both records, and you can then move the Subdomain's DNS record to CloudCannon with less downtime. The first record confirms that you own the Subdomain (its name starts with _cf-custom-hostname⁠), and the second issues the certificate (its name starts with _acme-challenge⁠). You can remove both records once HTTPS is on.

If Cloudflare is still preparing the records, the section shows Preparing records... until they are ready. CloudCannon checks for them at least once a day, and again each time you open the Subdomain page, at most once an hour.

Your current DNS Provider is the service whose nameservers your domain uses, which is often your domain registrar. The DNS tab of the Domain page lists the nameservers CloudCannon found. Some DNS Providers add your domain to the name of a record for you. If yours does, enter only the part of the name before your domain (e.g., _acme-challenge.careers for _acme-challenge.careers.example.com⁠).

You can still move DNS before the records are found. HTTPS catches up after a short gap. To go back to HTTP validation, click the Switch to HTTP validation button below the records. If CloudCannon doesn't find the records within two weeks, it goes back to HTTP validation by itself.

A screenshot of the HTTPS section for careers.example.com shows the Issuing the SSL Certificate with TXT validation notice, a table with the two TXT Records to add at the current DNS Provider, each marked Not found yet, a note that CloudCannon checks daily and when you open the page, and the Switch to HTTP validation button.
The HTTPS section with TXT records to add

Issue the certificate before you switch a proxied record

On Cloudflare Proxy, your own Cloudflare account proxies the Subdomain (a record whose proxy status is Proxied), so Cloudflare confirms that you own the Subdomain from your proxied record itself, and only the certificate needs a TXT record.

To issue the certificate before you switch a proxied record, on the page for the Subdomain:

  1. Click the Switch to TXT validation button in the HTTPS section. CloudCannon will show the TXT record to add.
  2. Add the TXT record CloudCannon shows to the DNS records of your domain in your Cloudflare account.

CloudCannon will issue the certificate before your proxied record changes, so HTTPS is on as soon as you switch. For more information, please read our documentation on configuring Cloudflare Proxy.

A screenshot of the Subdomain page for app.example.com on Cloudflare Proxy shows the HTTPS section with Waiting for your proxied record, and the Issuing the SSL Certificate with TXT validation block with the TXT Record to add in your Cloudflare zone and a Not found yet status.
The HTTPS section for a Subdomain on Cloudflare Proxy

Move a subdomain from another platform that uses Cloudflare

Some website platforms (e.g., Webflow) also serve your domain through Cloudflare. If the subdomain is still set up on that platform when you point your DNS at CloudCannon, Cloudflare can keep sending its visitors to the old platform, or show them an error page from Cloudflare, until CloudCannon's certificate for the Subdomain is active.

These instructions are for a Subdomain on CloudCannon Hosting whose domain uses external DNS. Before you begin, add the Subdomain on CloudCannon using the exact name visitors use (e.g., www.example.com), and leave its DNS pointing at the old platform for now.

To move a subdomain from another platform that uses Cloudflare, on the page for the Subdomain:

  1. Click the Switch to TXT validation button in the HTTPS section. CloudCannon will show the two TXT records to add.
  2. Add both records at your current DNS Provider, including the record that confirms you own the Subdomain.
  3. Wait until the HTTPS section shows HTTPS is on.
  4. Change the DNS record for the Subdomain at your DNS Provider to the record listed first in the Record column of the DNS section.

CloudCannon will serve the Subdomain once your DNS change spreads, with no certificate warning. You can then remove the subdomain from the old platform, and remove the TXT records.

Add each subdomain that visitors use as its own Subdomain on CloudCannon, even if it only redirects. Cloudflare prefers the old platform's setup for an exact subdomain over the wildcard SSL Certificate that covers subdomains you haven't set up on CloudCannon. The Switch to TXT validation button isn't available for your Base Domain. For more information, please read Cloudflare's documentation on migrating a hostname from another provider.

Renew the wildcard SSL Certificate on external DNS#

If your domain uses external DNS, each renewal of the wildcard SSL Certificate for your Base Domain needs new TXT records at your DNS Provider, unless you let Cloudflare renew it on its own.

When Cloudflare starts a renewal, the DNS tab of the Domain page lists the two TXT records under Wildcard certificate records, and the Other subdomains block in the HTTPS section of the Subdomain page for your Base Domain shows Action needed before [Date] with a link to them. CloudCannon also emails the records to everyone who can edit the settings of your Base Domain (the base-domain:settings:details:write permission).

Each record shows a Copy icon next to its name and value. If your DNS Provider adds your domain to record names for you, enter only the part of the name before your domain.

To renew the wildcard SSL Certificate:

  1. Log in to CloudCannon.
  2. Select the Organization your Custom Domain is connected to.
  3. Click the Custom Domains link in the App Sidebar. CloudCannon will open the Domains Browser.
  4. Click the Card for your domain. CloudCannon will open the Summary tab of the Domain page.
  5. Click the DNS tab. CloudCannon will open the DNS tab of the Domain page.
  6. Add the two TXT records listed under Wildcard certificate records at your DNS Provider.
  7. Click the I've updated it button for each record you added.

CloudCannon will check for the records every hour, and show Configured next to each record it finds. Once Cloudflare finds both records, it renews the certificate.

If the records are not in place the day before the certificate expires, Cloudflare does not renew the wildcard SSL Certificate. Your Base Domain and the Subdomains you have set up keep their own certificates, but visitors to a subdomain you haven't set up see a security warning, and the Other subdomains block shows No HTTPS. To give those visitors HTTPS again, add each subdomain they use as its own Subdomain, as a Redirect Subdomain if it should send them elsewhere, or contact our support team. Include your Base Domain, the subdomains your visitors use, and the expiry date shown in the Other subdomains block.

A screenshot of the HTTPS section for example.com shows the Other subdomains block with Action needed before a date and a link to the wildcard certificate records on the DNS tab.
The HTTPS section while the wildcard SSL Certificate renews

Action required: [Base Domain]'s wildcard SSL Certificate needs renewing

CloudCannon sends this email to everyone who can edit the settings of your Base Domain (the base-domain:settings:details:write permission) when a renewal of the wildcard SSL Certificate needs TXT records. The email lists the TXT records to add and the date to add them by, offers the CNAME record that lets Cloudflare renew the certificate on its own, and has an Open the Subdomain page for [Base Domain] button. If the email arrives more than 10 days before the certificate expires, and the records are still missing six days before it expires, CloudCannon sends a second email with the subject Action required: [Base Domain]'s wildcard SSL Certificate needs renewing (second warning).

A screenshot of the wildcard renewal email shows the headline example.com's wildcard SSL Certificate needs renewing, the date to add the TXT Records by, the two TXT Records to add, the CNAME Record under Want to skip this next time?, and the Open the Subdomain page for example.com button.
The wildcard renewal email

Let Cloudflare renew the wildcard SSL Certificate on its own

Instead of adding new TXT records at each renewal, you can add one CNAME record that lets Cloudflare validate each renewal itself. Its name is _acme-challenge.[Base Domain], and it points at an address on dcv.cloudflare.com that is specific to your domain. You can add it at any time, not only during a renewal. Until CloudCannon finds the record, it shows the record to add in these places:

  • The DNS tab of the Domain page, under Automatic renewal record (optional). The Other subdomains block in the HTTPS section of the Subdomain page for your Base Domain links to it.
  • The renewal email.

A name can't have a CNAME record and TXT records at the same time, so remove the TXT records before you add the CNAME record.

To let Cloudflare renew the wildcard SSL Certificate on its own:

  1. Remove the TXT records for _acme-challenge.[Base Domain] at your DNS Provider.
  2. Add the CNAME record CloudCannon shows at your DNS Provider, using the Name, Type, and Value shown.

Once CloudCannon finds the CNAME record, it will show that the certificate renews by itself in the Other subdomains block and on the DNS tab, and stop emailing you about renewals.

A screenshot of the HTTPS section for example.com shows HTTPS is on, and the Other subdomains block with HTTPS on, explaining that the certificate renews by itself through the CNAME record you added and showing the next renewal date.
The HTTPS section once Cloudflare renews the wildcard SSL Certificate on its own

Redirect HTTP to HTTPS#

Once HTTPS is on, visitors can open your Site at the more secure HTTPS address. When you check the Redirect http:// visitors to https:// checkbox in the HTTPS for [Subdomain] modal, CloudCannon redirects anyone who opens the HTTP address on the Subdomain, for every Site on it. The HTTPS section says whether visitors who open http:// land on https:// or stay on HTTP. For more information on HTTPS, please read our documentation on what an SSL Certificate is.

For a Redirect Subdomain, the checkbox is turned off: anyone who opens its http:// address goes straight to the redirect target, over HTTPS when the target has an SSL Certificate. For more information on redirects, please read our documentation on configuring HTTP redirects.

Related Resources

Open in a new tab