Websites
HTTPS certificates
How your free certificate is issued and renewed, and what the HTTPS statuses mean.
Learning path · step 9 of 20
On this page
Every website on FiniteHost gets free HTTPS. There is nothing to buy, upload or renew: certificates are issued and renewed automatically. This guide explains how that works, so you know what to expect and what to check if it takes longer.
Before you start#
- Add the website in the panel.
- Connect your domain: the A record for the bare domain and the CNAME for
wwwmust be set at your registrar.
How the certificate is issued#
Your site has two names, and each gets its own certificate:
| Name | Served by | Certificate from | When it is tried |
|---|---|---|---|
acme.in | your FiniteHost web server | Let's Encrypt | checked about every 30 seconds; issued as soon as DNS points here |
www.acme.in | the Bunny CDN | Bunny (free, automatic) | once an hour until the www CNAME points at your CDN host |
For the bare domain, the server checks regularly whether acme.in resolves to its own IP address. As soon as it does, it asks Let's Encrypt for a certificate and proves it controls the domain over plain HTTP (port 80). This is why HTTPS usually starts a few minutes after your DNS records point here.
If a request to Let's Encrypt fails (for example because an old record still sends some visitors elsewhere), the server waits and tries again: first after 15 minutes, then 30, then 60, doubling each time up to a maximum of 6 hours between tries.
The www name is handled by the CDN. The CDN requests its own certificate for www.acme.in once your CNAME points at the site's CDN host. FiniteHost asks for it once an hour until it succeeds.
Read the status in the panel#
- Open SSL / HTTPS. In the left menu, choose SSL / HTTPS. The top of the page says how many of your websites are on HTTPS.
- Check each domain. The HTTPS column shows one of three states.
- Fix DNS if needed. For a site that is not on HTTPS yet, press Check DNS to see its records.
| Status | Meaning |
|---|---|
| HTTPS on | A certificate exists. It renews automatically. |
| Waiting for DNS | The site is set up, but the domain does not point to the server yet, or the certificate has not been issued yet. |
| After setup | The site is still being set up. Wait a minute. |
After HTTPS is on#
- Visits to
http://acme.inare redirected tohttps://acme.inautomatically. - Your site sends a security header (HSTS) telling browsers to use HTTPS for this domain for one year.
- Certificates are renewed automatically well before they expire. You never need to do anything.
If HTTPS does not start#
- An old AAAA (IPv6) record for the domain points somewhere else. Delete it at your registrar.
- An old A record is still present next to the new one. Keep only the FiniteHost IP address.
- Cloudflare's proxy (orange cloud) is on. Switch both records to DNS only.
- Your files block
/.well-known/: the folder/.well-known/acme-challenge/is served by FiniteHost itself, so your own files cannot block it. You do not need to create it. - It is only
wwwthat fails: check that thewwwrecord is a CNAME to the CDN host shown in the panel, not an A record. It can take up to an hour after the CNAME is visible.
For a full checklist, see HTTPS not issued.
What's next#
- Check DNS with simple commands
Was this helpful?
Still stuck?
Email support@finitehost.com with your subscription ID (it starts with t, shown on the panel's Dashboard) and what you tried. A person replies, usually within one business day.
Last updated 27 October 2026. Found something wrong? Tell support@finitehost.com.