Try your current server with tens of thousands of sites and certificates, then try them with Caddy – you'll see what we mean. Caddy 2 is designed to be highly flexible when needed, but also highly focused on its core competency. The ideal way to do this is DNS validation (which will require building Caddy with the Cloudflare module, and configuration with your Cloudflare API keys).
Caddy has the most robust TLS stack on the market. We should probably make it longer.As far as I know, the only supported browsers on Windows are those which use the system trust store.And is this necessary if I access my local server using its public DNS ?If I manage to configure Caddy to get a certificate from Let’s Encrypt, I assume Firefox will trust it out of the box ?Yeah, because Let’s Encrypt is a publicly-trusted CA.This topic was automatically closed 30 days after the last reply. Caddy is the only first web server that can acquire and renew SSL/TLS certificates automatically using Let’s Encrypt. When accessing localhost through a web browser, I get the following error in the console:I’ve tried untrusting / re-trusting the certificate.When accessing localhost through a web browser, I get the following error in the console:This is fine, it just means there’s no OCSP server URL in the certificate, which is expected because Caddy itself issued this certificate and there’s no real utility for revocation checking in that case.Thanks. 1. If the CA sees the expected resource, a certificate is issued.This challenge requires port 443 to be externally accessible. Caddy 2 can and will renew certificates behind Cloudflare’s CDN. All rights reserved. Caddy 2 is a highly extensible, self-hosted platform on which you can build, configure, and deploy long-running services ("apps").. Caddy ships with apps for an HTTPS server (static files, reverse proxing, load balancing, etc. And you seem to be telling me there’s nothing I can do about that (using Caddy’s toolset) until the certs expire?To be unambiguous, there’s no flag or config you can use to tell Caddy to renew certificates on disk that are currently valid. Read on, since there's some things you should know when upgrading! When trying to renew the ssl cert, I received the following message: 2020/07/08 07:38:22 [INFO] [milanolarry.tk] acme: Obtaining bundled SAN certificate 2020/07/08 07:38:23 [INFO] [milanolarry.… Caddy was the first server to fully automate public certificate management—so we've been doing this longer than anyone.
Caddy 2 is capable of renewing certificates … © 2015-2020 Light Code Labs. Caddy 2 is a highly extensible, self-hosted platform on which you can build, configure, and deploy long-running services ("apps").. Caddy ships with apps for an HTTPS server (static files, reverse proxing, load balancing, etc. I moved a working Caddy server behind CloudFlare’s CDN. I don’t have a good explanation for the NXDOMAIN issue either, but it worked fine only a minute or two later.Once you’ve worked out the kinks in your last two domains on the staging server, run Caddy manually again against the production endpoint to generate the live certificates you need.Oh… ha.
"Rewrite hacks" are no longer necessary in v2, because the Caddyfile now lets you That sounds like a bit more than a transient Cloudflare API issue; that’s LetsEncrypt telling you a DNS lookup totally failed on their end.Except everything worked fine on the second manual run. At time of writing (December 2018), Let's Encrypt only issues wildcard certificates with the DNS challenge.
1.
We've solved some hard problems together—usually during nights and weekends—and in days of isolation during this pandemic, no less. For example, To get a wildcard from Let's Encrypt, you simply need to enable the You won't have to know or do anything else about it. Might have merit as a feature request.That’s what it’s there for; it’s identical to the production endpoint, with the exception of issuing untrusted certificates, for test purposes.Once you’ve worked out the kinks in your last two domains on the staging server, run Caddy manually again against the production endpoint to generate the live certificates you need.Caddy won’t ever bring your sites down (even if the certificates start failing to renew).Caddy will never take your sites offline if it’s already serving them.