letsencrypt has been renamed to greenlock
janwo opened this issue · 8 comments
When I install the module, I get the following warning: �letsencrypt@1.5.1: letsencrypt has been renamed to greenlock. Please find it at npm greenlock
Any plans to update this?
The API has completely changed and would likely require a rewrite of this module to integrate. I will dig a bit deeper when I get some time.
@janwo I have updated auto-sni to use 'greenlock-express'. There were some features removed (disabling forcessl, custom redirect https status code and self signed certs on failure) but the api is more/less the same (except for restify users.)
This module is now an extremely thin wrapper and is only 51 loc. Please try updating and let me know how this goes!
@DylanPiercey I tried it out now, but now it does not work on my hapi environment anymore. Any ideas?
[le/lib/middleware.js] created middleware
Handling ACME challenges and redirecting to https on plain port 80
Handling ACME challenges and serving https 443
And thats it...
@janwo can you post your setup code?
import {Server} from 'hapi';
// Initialize Hapi server.
let server = new Server({
connections: {
router: {
isCaseSensitive: true,
stripTrailingSlash: true
}
}
});
// Load SSL key and certificate.
let autoSni = AutoSNI({
email: Config.backend.mails.admin,
agreeTos: true,
debug: Config.debug,
domains: [
Config.backend.domain
],
ports: {
http: Config.backend.ports.http,
https: Config.backend.ports.https
}
});
// Create server connection.
server.connection({
listener: autoSni,
tls: true,
autoListen: false
});
I removed forceSSL
and the redirectCode
in order to stay compatible to your update.
And you are running this on a server that is being accessed by Config.backend.domain
?
Oh, I think I solved the error. I used the https
prefix within the config. I try that out now. Sorry for wasting your time 🙄
No problem happy to help.