Sample Nodejs app which uses letsencrypt-express for HTTPS

index.js

'use strict';

var lex = require('letsencrypt-express').create({
  // NOTE, server should be set to 'staging' while testing
  server: 'https://acme-v01.api.letsencrypt.org/directory'
, challenges: { 'tls-sni-01': require('le-challenge-sni').create({ webrootPath: '/tmp/acme-challenges' }) }
, challengeType: 'tls-sni-01'
, store: require('le-store-certbot').create({ webrootPath: '/tmp/acme-challenges' })
, approveDomains: approveDomains
});

function approveDomains(opts, certs, cb) {
  if (certs) {
    opts.domains = certs.altnames;
  }
  else {
    opts.domains = [domain];
    opts.email = email;
    opts.agreeTos = true;
  }

  cb(null, { options: opts, certs: certs });
}

var app = require('express')();
app.use('/', function (req, res) {
  res.end('Hello, World!');
});

require('https').createServer(lex.httpsOptions, lex.middleware(app)).listen(443, function () {
  console.log("Listening for ACME tls-sni-01 challenges and serve app on", this.address());
});

Edited code to include ' lex.middleware(app)'. At first i thought it was working without this, but alas, i was wrong

Hmm. It should indeed work without the middleware. It should also not require webrootPath anywhere but letsencrypt-express may be trying to instantiate things you shouldn't need that require that. At the end of the day, if it's working for you, that's great, but you may find you can use letsencrypt directly, i.e. cut out letsencrypt-express, without making the code much longer. If you don't want to, I might have a go modifying letsencrypt-express to make an https-only version some time soon too. But if you come up with something, I may not need to. :-)