Skip to main content

Fewer false warnings for Cloudflare-proxied domains

A single failed HTTPS check through Cloudflare no longer flags your domain or emails your team. Easel warns after two failed checks in a row.

Author
Sean WhitemanFounder, Easel.sh
Published
Product
Domains

Easel regularly checks that HTTPS requests to a domain proxied through Cloudflare reach your project. Until now, one failed check marked the domain Check DNS and emailed the workspace’s owners and admins, even when the failure was a brief blip that the next check cleared.

A single failed check is now ignored. The warning and the email come only after two failed checks in a row, and a successful check resets the count. Domains that point at Easel without a proxy already worked this way.

Project Domains section with www.acme.com, Production, Through Cloudflare, marked Check DNS. Its message says www.acme.com is proxied by Cloudflare, but HTTPS requests through it don't reach Easel (HTTP 525: SSL Handshake Failed), and to set SSL/TLS to Full (strict) and make sure no rule blocks or redirects /.well-known/easel-tls-check.

Check DNS shows only after two failed checks in a row, and says what to change in Cloudflare

A warning on a live domain never removes it from your project. See Cloudflare.

All updates

Start deploying

Free to start. Import a repository and get a production URL in a few minutes.