Issue with TLS-SNI-01 and Shared Hosting Infrastructure

Re:Issue with TLS-SNI-01 and Shared Hosting Infrastructure by mh-cx on Wednesday January 10, 2018 @08:03AM (#16114607)

Does this basically say, that letsencrypt will no longer work in a virtual hosting setup?

What about existing certs? Can they at least be renewed when they expire?

[ Parent | on HN ]

Re:Issue with TLS-SNI-01 and Shared Hosting Infrastructure by luto on Wednesday January 10, 2018 @08:21AM (#16114696)

Let's Encrypt works just fine in a virtual hosting setup using the http-01 or dns-01 challenges. In fact, all (shared/virtual hosting) users in my company automatically get certificates this way.

[ Parent | on HN ]

Re:Issue with TLS-SNI-01 and Shared Hosting Infrastructure by v4tab on Wednesday January 10, 2018 @10:09AM (#16115395)

Is there a way to tell whether I am using http-01, dns-01 or TLS-SNI-01? I'm using the letsencrypt nginx module.

[ Parent | on HN ]

Re:Issue with TLS-SNI-01 and Shared Hosting Infrastructure by discreditable on Wednesday January 10, 2018 @10:31AM (#16115606)

Seems to use tls-sni-01. This is my guess by looking at the certbot-nginx source directory: https://github.com/certbot/certbot/tree/b1826d657ffc7c278041...

[ Parent | on HN ]

Re:Issue with TLS-SNI-01 and Shared Hosting Infrastructure by mnordhoff on Wednesday January 10, 2018 @01:16PM (#16117366)

That's correct.

Certbot can use different plugins for validating the name and for installing the certificate.

You can configure HTTP-01 to work and use "certbot -a webroot -i nginx -w /path/to/whatever -d example.com -d www.example.com".

https://community.letsencrypt.org/t/solution-client-with-the...

[ Parent | on HN ]