Caddy – The HTTP/2 Web Server with Automatic HTTPS

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by manigandham on Wednesday April 25, 2018 @06:15AM (#16920134)

What do you mean by locally? If you want HTTPS automatically then the site must be publically available so that LetsEncrypt can verify the domain and grant the certificate. If that's not possible then you'll have to use the DNS challenge and setup a provider plugin.

It doesn't matter where the backend points and you can use it to serve a docker container if you want, but that's different from the the host/frontend address you use.

[ Parent | on HN ]

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by onion2k on Wednesday April 25, 2018 @06:33AM (#16920227)

Locally in the sense of a local development server. The issue is that there wouldn't be a real DNS record pointing at the machine (well, unless you added one to point at your external IP address, but that's a pain for teams). I guess if Let's Encrypt needs to verify the domain it won't be possible...

[ Parent | on HN ]

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by captncraig on Wednesday April 25, 2018 @08:15AM (#16920785)

Let's encrypt can issue certs without needing a public route to your machine if you use the dns challenge. Here's what I do:

1. Add a public A record (or host file) local.mydomain.tld to 127.0.0.1.

2. Host my dns with cloudflare (other providers have plugins too), and install the caddy plugin to do the dns challenge for certs.

3. Caddy can then get certs for local.mydomain.tld and serve them locally.

[ Parent | on HN ]

Re:Caddy – The HTTP/2 Web Server with Automatic HTTPS by manigandham on Wednesday April 25, 2018 @06:48AM (#16920306)

Then you need to acquire the certificate yourself. Or just use a self-signed certificate since it's your own machine....

[ Parent | on HN ]