Stream: boston

Topic: HTTPS everywhere, even Phil's site

Dan (Aug 13 2025 at 16:47):

@Philip Durbin In case you don't want to switch to Caddy for SSL, apparently nginx is making it easier: https://news.ycombinator.com/item?id=44889941

Dan (Aug 13 2025 at 17:11):

But man, Caddy still has it beat so badly.

From the nginx blog post:

acme_issuer letsencrypt {
    uri         https://acme-v02.api.letsencrypt.org/directory;
    # contact   admin@example.test;
    state_path  /var/cache/nginx/acme-letsencrypt;
    accept_terms_of_service;
}

server {
    # listener on port 80 is required to process ACME HTTP-01 challenges
    listen 80;
    location / {
        #Serve a basic 404 response while listening for challenges
        return 404;
    }
}

    acme_certificate letsencrypt;

Here's what I have for Caddy:

   tls <my email address>

For each domain.

Dan (Aug 13 2025 at 17:14):

And afaik it's optional

Dan (Aug 13 2025 at 17:15):

I'm sure there's a good reason for all that Ngnix does but I'm not the target audience for any of it.

Notification Bot (Aug 14 2025 at 01:17):

4 messages were moved here from #boston > Personal Websites by Philip Durbin.

Philip Durbin (Aug 14 2025 at 01:18):

Yeah, I should definitely set up HTTPS some day.

Last updated: Nov 11 2025 at 06:28 UTC