• Posts
  • RSS
  • ◂◂RSS
  • Contact

  • HTTPS Support

    April 13th, 2016
    https, tech  [html]
    This site is now available over HTTPS, with certificates from Let's Encrypt: https://www.jefftk.com.

    The certificates only last for three months, and I don't have automated renewal set up, so the https site might go down briefly every so often for the cert being out-of-date if I forget to renew. Once I sort this out I can redirect the http site to https, but I'm wary of doing it before then.

    The letsencrypt-auto command I'm using is:

    letsencrypt/letsencrypt-auto certonly        \
      --webroot                                  \
      -w /var/www/    -d www.jefftk.com          \
                      -d jefftk.com              \
      -w /var/www-fr/ -d www.freeraisins.com     \
                      -d freeraisins.com         \
      -w /var/www-lw/ -d www.lilywise.com        \
                      -d lilywise.com            \
      -w /var/www-tc/ -d www.trycontra.com       \
                      -d trycontra.com           \
      -w /var/www-aw/ -d www.annakaufmanwise.com \
                      -d annakaufmanwise.com     \
      --email jeff.t.kaufman@gmail.com           \
      --agree-tos
    

    This puts files on each of my domains under /.well-known/acme-challenge/, and tells the CA server about them. The CA server can verify that the files are actually reachable, through both the www and bare hostnames, and issue the certificate. I'm having it issue one SAN certificate for all of the sites, which makes certificate managemant simpler.

    Reading the docs now, it sounds like after running that command once it's sufficient to use letsencrypt-auto renew. It remembers the configuration, used to get the certs, and asks for new ones they're close to expiring. I've put letsencrypt-auto renew && service nginx restart in root's crontab, but I'm not confident yet that it will work.

    When I first set this up I had some mixed content issues and problems with links taking you to the http version of the site. Over the years various scripts had ended up generating absolute urls instead of relative ones [1] so I needed to through and remove all text references to http://www.jefftk.com.

    At this point I'm pretty happy, except for the renewal story.

    Update 2016-08-09: converted rss feed to give https links, as a first step in ramping up to full https.


    [1] This site started out under /~cbr/ on sccs, which would sometimes redirect people to /users/08/cbr/ depending on current configuration, which meant I couldn't use site-relative urls. I haven't been on sccs for years, but things stick around.

    Comment via: google plus, facebook

    Recent posts on blogs I like:

    Who Should Bear the Risk in Infrastructure Projects?

    The answer to the question is the public sector, always. It’s okay to have private-sector involvement in construction, but the risk must be borne by the public sector, or else the private sector will just want more money to compensate for the extra risk. …

    via Pedestrian Observations November 30, 2020

    Fireside Friday, November 27, 2020

    Hey folks! Fireside this week. A bit of a change-up in terms of the coming attractions. I had planned to start “Textiles, How Did They Make It?” next, but I want to do a bit more reading on some of the initial stages of textile production (that is, the pr…

    via A Collection of Unmitigated Pedantry November 27, 2020

    Thoughts you mightn't have thunk about remote meetings

    Welcome to this week's edition of "building a startup in 2020," in which all your meetings are suddenly remote, and you probably weren't prepared for it. I know I wasn't. We started a "fully remote" company back in 2019, but …

    via apenwarr November 23, 2020

    more     (via openring)


  • Posts
  • RSS
  • ◂◂RSS
  • Contact