### Author:  [@goetzc](https://community.xibo.org.uk/u/goetzc)
#### Post date: [August 27, 2019, 10:14pm UTC](https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047/1 "2019-08-27T22:14:06Z")
Hi!
I’m experiencing this issue, where the Xibo player for Windows can’t connect to a host using HTTPS and SNI (it’s a multi-application server). The Android player connects successfully.
Reaching and using the CMS works from Windows. The error the player shows is:
> “The underlying connection was closed: An unexpected error occurred on a send.”
with no more information.
The server is hosted on AWS using an AWS-issued HTTPS certificate. After creating a new server —using Terraform, then provisioning with Ansible, so it’s the same configuration on both servers— and moving the CMS to this new, single application machine, the player connects without any issue. In both cases there is an LB which contains the AWS ACM certificate for HTTPS termination, a quite common setup.
So Android player connects, Windows does not connect to the multi-host server.
Server details:
NGINX
Xibo CMS: 2.0.5
Player details:
Windows 10
xibo-client-v2-R200-win32-x86.msi
GitHub issue:
>
>
> Hey there. CMS version 2.0.4 is installed using Docker and works correctly with …HTTPS on a multi-host server.
>
> Android player can connect to it, but the Windows player (xibo-client-v2-R200-win32-x86.msi) fails with the following error:
> \`“The underlying connection was closed: An unexpected error occurred on a send.” \`
>
> !\[image\](https://user-images.githubusercontent.com/2220440/62094292-35b2b280-b242-11e9-8794-c4419c6d7713.png)
>
> with no more information. After moving the CMS to a single application server, the player connects without issue.
>
> \
---
### Author:  [@alex](https://community.xibo.org.uk/u/alex)
#### Post date: [August 28, 2019, 7:13am UTC](https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047/2 "2019-08-28T07:13:41Z")
Thanks for your post
The Windows Player definitely connects to an SNI-enabled host, so that isn’t the issue.
I think it’s far more likely to be AWS denying TLS 1.0 connections. Windows by default doesn’t offer TLS 1.2 even though it’s quite capable of doing it.
Try enabling that, and I think you’ll find that will solve it:
> [@Enable TLS 1.2 / Strong Crypto in Windows .net Player](https://community.xibo.org.uk/t/enable-tls-1-2-strong-crypto-in-windows-net-player/7091):
>
> By default, the Windows .net Player uses the standard crypto libraries provided by the Microsoft .net Framework. If you need to use a CMS that provides only TLS 1.2 connections, then you will need to ensure you set the following registry settings: 32 bit machines Key: HKLM\SOFTWARE\Microsoft\.NetFramework\v4.0.30319\SchUseStrongCrypto Type: DWORD Value: 1 64 bit machines Key: HKLM\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319\SchUseStrongCrypto Type: DWORD Value: 1 Original post th…
---
### Author:  [@goetzc](https://community.xibo.org.uk/u/goetzc)
#### Post date: [August 28, 2019, 9:57pm UTC](https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047/3 "2019-08-28T21:57:56Z")
Thank you. TLS 1.0 is no longer recommended to use. I think compatibility with the latest TLS version requires an up to date .NET framework.
It looks like .NET 4.6+ supports TLS 1.2 by default. On .NET 4.5 you can set it on the `SecurityProtocol`:
```
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls;
```
For older versions of .NET there are some options:
> **[TLS 1.2 and .NET Support: How to Avoid Connection Errors - Perficient Blogs](https://blogs.perficient.com/2016/04/28/tsl-1-2-and-net-support/)**
>
> Can't upgrade your application to latest .NET framework and still want to use TLS 1.2? Solutions exist, but they vary depending on the framework version.
---
### Author:  [@alex](https://community.xibo.org.uk/u/alex)
#### Post date: [August 29, 2019, 2:26pm UTC](https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047/4 "2019-08-29T14:26:42Z")
All you need to do to enable TLS 1.2 connections is apply the registry key I linked in my original reply.
---
### Author:  [@system](https://community.xibo.org.uk/u/system)
#### Post date: [March 4, 2020, 5:14pm UTC](https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047/5 "2020-03-04T17:14:37Z")