• Posts
  • RSS
  • ◂◂RSS
  • Contact

  • Moving to HTTPS

    October 5th, 2017
    https, tech  [html]
    About a year and a half ago I added HTTPS support to my sites but kept them running on HTTP for the time being. Chrome plans to eventually mark all HTTP pages as "Not secure", however, and HTTP is in fact not secure, so today I decided to switch over to HTTPS as the default.

    Since Ubuntu 16 LTS ships with a very old version of the Let's Encrypt client I followed their instructions to move to a recent version. Then I put the following in my root crontab:

    28 11 * * * certbot renew --quiet --post-hook "service nginx restart"
    

    This runs the command daily at 11:28, which is a time I chose randomly. Random is good here: it keeps the load on the Let's Encrypt servers more consistent.

    This tells the client to renew whatever cert I currently have, which I had originally generated with:

    sudo letsencrypt 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
       -w /var/www-oc/ -d www.olivercumming.com
                       -d     olivercumming.com
       -w /var/www-bd/ -d www.bidadance.org
                       -d     bidadance.org
       -w /var/www-rs/ -d www.regularlyscheduled.com
                       -d     regularlyscheduled.com
       --email jeff.t.kaufman@gmail.com
       --agree-tos
    

    To switch over to HTTPS I've put:

    server {
      listen 80 default_server;
      server_name redirect_to_https;
      return 301 https://$host$request_uri;
    }
    

    in my nginx config and removed all my listen 80 directives.

    Since I'm still not 100% confident in my HTTPS setup I've put listen 8080 directives for each of my sites, so that it's possible to visit www.jefftk.com:8080 etc over HTTP.

    Comment via: google plus, facebook

    Recent posts on blogs I like:

    Collections: The Queen’s Latin or Who Were the Romans? Part IV: The Color of Purple

    This is the fourth part (I, II, III) of our series asking the question “Who were the Romans?” and contrasting the answer we get from the historical evidence with the pop-cultural image of the Romans as a culturally and ethnically homogeneous society typic…

    via A Collection of Unmitigated Pedantry July 23, 2021

    The Leakage Problem

    I’ve spent more than ten years talking about the cost of construction of physical infrastructure, starting with subways and then branching on to other things, most. And yet there’s a problem of comparable size when discussing infrastructure waste, which, …

    via Pedestrian Observations July 23, 2021

    Songs about terrible relationships

    [Spoilers for several old musicals.] TV Tropes lists dozens of examples of the “I want” song (where the hero of a musical sings about their dream of escaping their small surroundings). After watching a bunch of musicals on maternity leave, I’m wondering h…

    via The whole sky July 17, 2021

    more     (via openring)


  • Posts
  • RSS
  • ◂◂RSS
  • Contact