Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
1–10 of 76 posts
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#2This 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
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#3The only clients I've had trouble with SNI is Amazon and Apple's Java clients, as well as python2. It's unfortunately still not possible to host a podcast feed with an SNI HTTPS URL in iTunes, nor can you use SNI for Alexa skills. Otherwise, I've been happily using SNI for years now.
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#4Can I apply this on Heroku hosted app?
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#5This 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.
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#6This article has an incorrect premise. The author should learn about SNI: https://en.wikipedia.org/wiki/Server_Name_Indication
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#7Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#8This 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.
You might be able to get useful debugging information with tcpdump or wireshark because SNI itself is sent in the clear (prior to the TLS cryptographic key exchange). You could see if the server is doing something different from other servers, or the browser is doing something different from other browsers.
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#9I 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
Re: Hosting Multiple HTTPS Domains from the Same Server with Let's Encrypt and Nginx
#10This 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.
It must have been something else. Even Safari on iOS has supported SNI since iOS 4.0 (2010).