I've never had a single problem with hosting multiple https domains using Nginx and Let's Encrypt. This article is somewhat baffling, considering his example of clients that need this is "mobile browsers" but I've used iOS and Android and it works just fine.
Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
11–20 of 76 posts
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#12I use SNI for my Apache Lets Encrypt script. This allows one IP (my home IP) to host many sites easily and monitors changes to sites-enabled to trigger creation of new SAN certificates based on contents of ServerName and ServerAlias. The script also will regenerate certs for sites-enabled every 30 days. See: https://github.com/tzakrajs/cloud-fortress-lets-encrypt
Included is daemontools run script, the script runs in a loop but should it die, you want it to restart. I added supervise command to my /etc/rc.local to make this run when the web server comes up.
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#13I use SNI for my Apache Lets Encrypt script. This allows one IP (my home IP) to host many sites easily and monitors changes to sites-enabled to trigger creation of new SAN certificates based on contents of ServerName and ServerAlias. The script also will regenerate certs for sites-enabled every 30 days. See: https://github.com/tzakrajs/cloud-fortress-lets-encrypt
[deleted]
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#14This article advocates for IP Per Domain over SNI. It's 2017, please use SNI. There's not enough IPv4 addresses in the world. Every single major browser supports it, and has supported it for some time: http://caniuse.com/#search=sni
There's enough IPv6
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#15This article advocates for IP Per Domain over SNI. It's 2017, please use SNI. There's not enough IPv4 addresses in the world. Every single major browser supports it, and has supported it for some time: http://caniuse.com/#search=sni
That is if you don't care about supporting windows xp users, I certainly don't.
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#16Earlier quoted context omitted.
(author here) I would have loved to have SNI work. I wrote this article in response to having profound struggles making it work. My iPhone 7's Safari was routinely failing to connect to sites other browsers claimed were fine, when relying on SNI. The day i swapped over to IP-based connections, the problem resolved itself immediately. If there is something i am missing i would love to know what it is.
It must have been something else. Even Safari on iOS has supported SNI since iOS 4.0 (2010).
The only thing I've had SNI fail under (so far) had been Netscape Navigator 3.0 and at that point, does it really matter?
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#17This article advocates for IP Per Domain over SNI. It's 2017, please use SNI. There's not enough IPv4 addresses in the world. Every single major browser supports it, and has supported it for some time: http://caniuse.com/#search=sni
(author here) I would have loved to have SNI work. I wrote this article in response to having profound struggles making it work. My iPhone 7's Safari was routinely failing to connect to sites other browsers claimed were fine, when relying on SNI. The day i swapped over to IP-based connections, the problem resolved itself immediately. If there is something i am missing i would love to know what it is.
Can you get to https://sni.velox.ch/ from your phone? What are the first few lines?
In particular, I'm curious if this is a misconfiguration on the server end, or a misconfiguration on the client end. Certain VPNs or malware can break SNI.
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#18Ugh. Let's Encrypt will issue you a single certificate for multiple domains on the same server. It's easy to set up, too.
It's not just for multiple subdomains like sub1.example.com and sub2.exmaple.com. You can have any unrelated domains you want on the cert.
You don't need multiple IPs and you don't even need SNI with its legacy client compatibility problems (now mostly well past). Just get a certificate that covers all the domains you use.
There's no reason at all to suffer with the setup and security and resource problems of SNI or multiple IPs outside extreme scenarios.
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#19Ugh. Let's Encrypt will issue you a single certificate for multiple domains on the same server. It's easy to set up, too. It's not just for multiple subdomains like sub1.example.com and sub2.exmaple.com. You can have any unrelated domains you want on the cert. You don't need multiple IPs and you don't even need SNI with its legacy client compatibility problems (now mostly well past). Just get a certificate that cover…
I was about to comment pretty much all of these points. As soon as I read about multiple IP's I wondered what was going on.
I'm starting my own tech blog for similar articles, maybe I'll do a simpler example for my first post.
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#20I've never had a single problem with hosting multiple https domains using Nginx and Let's Encrypt. This article is somewhat baffling, considering his example of clients that need this is "mobile browsers" but I've used iOS and Android and it works just fine.
Me neither. I guess Cloudflare (to name but one service reliant on SNI) hasn't either...
This article is a bit of an unusual response to a problem of a device not working. When a device of mine doesn't work but others do I put it down to there being a problem with my device, not a widely used technology (like SNI).
It's an interesting article to read though.