TurtleGuard

Docs / Getting started

Certificates

HTTPS for the site is issued and renewed on its own, on every node at once.

2 minute readUpdated 2026-11-07

The HTTPS certificate is issued automatically once the domain is connected. Nothing to do on your side: we issue it with Let's Encrypt, deploy it to every node and renew it ahead of time.

How the certificate is issued

ConnectionHow ownership is checkedWildcard *.example.com
NSWith a DNS record in our zone, on our ownYes, if there is a proxied * record
CNAME or AOver HTTP: Let's Encrypt opens a service link on our nodeNo, only the listed names
  • Issuing starts once DNS is verified. New subdomains and proxied records are added to the certificate on their own.
  • With CNAME or A, names that do not point at us yet are skipped. We check them again every 15 minutes and add them once the record is switched.
  • Keys are ECDSA P-256: faster than RSA and supported by every modern browser.

Your own certificate

Uploading your own certificate is not available yet: every site gets a Let's Encrypt certificate.

Renewal

The certificate is renewed 30 days before it expires. If fewer than 14 days are left, the panel shows “expiring soon” — renewal is failing and DNS is worth checking.

If issuing failed

The error text is in the panel: domain → Settings → Connection. We retry on our own: first after 5 minutes, then less and less often, at most once a day. Common causes:

  • DNS is not pointed at us yet or has not updated at the provider.
  • The domain has a CAA record that does not allow Let's Encrypt.
  • The server or another proxy intercepts /.well-known/acme-challenge/ requests.

Once the cause is fixed, press Reissue — the certificate is ready in about a minute. Reissue works up to 5 times an hour.

Encryption for visitors

Settings in the panel: domain → Settings → Encryption.

  • HTTPS only — on by default. HTTP requests are redirected to HTTPS with a 301 once the site has a certificate.
  • HSTS — the browser remembers for a year, including subdomains, that the site opens over HTTPS only. Turn it on when you are sure every subdomain works over HTTPS.
  • Minimum TLS version — 1.2 (default) or 1.3. With 1.3 old clients cannot connect.
  • Visitors always get HTTP/2 when the browser supports it. HTTP/3 is not supported yet.

Encryption to your server

How the node connects to your server is set separately: domain → Protection → Encryption to the origin.

ModeHow the node reaches the server
AutoDefault. Port 443 — HTTPS, port 80 — HTTP, other ports are detected
FlexibleHTTP only. For a server without a certificate
FullHTTPS without checking the server certificate. A self-signed one works
StrictHTTPS with certificate and name checks. The safest; the server needs a valid certificate

The HTTP/2 switch in Settings → Speed turns on HTTP/2 between the node and your server. Turn it on only if the server supports HTTP/2 over HTTPS.