Repository navigation
TLS SNI broken with nginx on 2017Q4 #95
Description
Activity
This was on a SmartOS [email protected] image.
nginx 1.13.3 on SmartOS [email protected] seems to work ok.
Brian, works for me with 1.13.7 on a base-lts-17.4.0 VM. Can you share your config bits?
Actually, looking at my config again I did have an error on the
server_namethat was the problem. Fixing that did resolve it, so this isn't an issue after all.Same for me. In the template I was basing my configs off of there was a semi-colon missing from the index statement just before the
server_name...I'm increasingly catching my brain seeing punctuation that isn't really there.
- added a commit that references this issue
on Aug 6, 2018 - added a commit that references this issue
on Oct 20, 2019 - added a commit that references this issue
on Nov 6, 2019 - added a commit that references this issue
on Dec 19, 2019 109 remaining items
- added 10 commits that reference this issue
on May 14, 2026 - added a commit that references this issue
on May 22, 2026 - added a commit that references this issue
on May 31, 2026 - added 2 commits that reference this issue
on Jul 26, 2026
Metadata
Metadata
Assignees
Labels
No labels
This affects both nginx 1.12.2 and 1.13.7. This does not affect Apache.
When visiting a server properly configured with SNI, only one server stanza is used. The certificate and content served for all SSL sites are from the first SSL enabled host.