# Https without SNI

**URL:** <https://community.letsencrypt.org/t/https-without-sni/35529>\
**Category:** Feature Requests\
**Created:** [June 5, 2017, 9:56am UTC](https://community.letsencrypt.org/t/https-without-sni/35529 "2017-06-05T09:56:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex-r](https://avatars.discourse-cdn.com/v4/letter/a/f4b2a3/32.png) [@Alex-r](https://community.letsencrypt.org/u/Alex-r)\
**Post date:** [June 5, 2017, 9:56am UTC](https://community.letsencrypt.org/t/https-without-sni/35529/1 "2017-06-05T09:56:48Z")

</div>

Hello.  
I need to ssl worked without SNI mode. You can make ssl worked without SNI? If you can, then please do. the website [https://belnos.ru](https://belnos.ru)  
Thank you!

---

<div class="post-metadata">

**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\
**Post date:** [June 5, 2017, 10:02am UTC](https://community.letsencrypt.org/t/https-without-sni/35529/2 "2017-06-05T10:02:23Z")

</div>

SNI has nothing to do with the Certificate Authority or the certificate they issue; it’s all a matter of your web server and its configuration. This question has nothing at all to do with Let’s Encrypt.

---

<div class="post-metadata">

**Author:** ![ahaw021](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ahaw021/32/14882_2.png) [@ahaw021](https://community.letsencrypt.org/u/ahaw021)\
**Post date:** [June 5, 2017, 12:48pm UTC](https://community.letsencrypt.org/t/https-without-sni/35529/3 "2017-06-05T12:48:20Z")

</div>

hi @Alex-r

I do not understand - your webserver supports SNI

Also if you are talking about the TLS-SNI validation method. The SNI component is mandated by the standard.

[https://tools.ietf.org/html/draft-ietf-acme-acme-01#section-7.3](https://tools.ietf.org/html/draft-ietf-acme-acme-01#section-7.3)

Andrei

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [June 5, 2017, 1:01pm UTC](https://community.letsencrypt.org/t/https-without-sni/35529/4 "2017-06-05T13:01:53Z")

</div>

> [@ahaw021](#):
>
> I do not understand - your webserver supports SNI

Perhaps some clients don't. 😉

For SSL to work without SNI, you would have to have multiple IP addresses to server multiple certificates. If you just have a single certificate for just one site, there shouldn't be any configuration needed at all. If you do have multiple IP addresses, just make sure every `<VirtualHost>` directive is using a different IP address. Also, the corresponding hostname for that `<VirtualHost>` should point to that IP address, but that's obvious, I hope.

If you don't have multiple IP addresses and you DO need multiple certificates to work without SNI: that isn't possible.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 6, 2017, 5:11am UTC](https://community.letsencrypt.org/t/https-without-sni/35529/5 "2017-06-06T05:11:21Z")

</div>

Can you show the conf file?  
Maybe we could better understand your situation and your goal.

---

<div class="post-metadata">

**Author:** ![tdelmas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tdelmas/32/1866_2.png) [@tdelmas](https://community.letsencrypt.org/u/tdelmas)\
**Post date:** [June 6, 2017, 8:45am UTC](https://community.letsencrypt.org/t/https-without-sni/35529/6 "2017-06-06T08:45:37Z")

</div>

To ensure your server works with clients without SNI support, the default domain of your server must answer a certificate that cover all domains managed by that server.

Let’s Encrypt allows you to create certificates that contains up to 100 domains (but no wildcard).

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 6, 2017, 9:41am UTC](https://community.letsencrypt.org/t/https-without-sni/35529/7 "2017-06-06T09:41:37Z")

</div>

SNI is required on “shared” servers.  
If you don’t own the entire IP, then the server must use SNI to direct individual requests to their proper website.  
[https://site.one](https://site.one) = IP1  
[https://site.two](https://site.two) = same IP1  
[https://site.three](https://site.three) = same IP1 again  
[https://site.four](https://site.four) = and same IP1 again

So, you basically want [https://IP1](https://IP1) and [https://your.site](https://your.site) to show your site?  
If so, talk to whomever controls the IP - who has root access? who can make changes to the web server conf file?  
Only a server admin can make such a change.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [July 6, 2017, 9:41am UTC](https://community.letsencrypt.org/t/https-without-sni/35529/8 "2017-07-06T09:41:54Z")

</div>

Closed on July 6, 2017, 9:41am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
