# Re connecting player to new CMS

**URL:** https://community.xibo.org.uk/t/re-connecting-player-to-new-cms/14534
**Category:** Get Help
**Created:** [May 29, 2018, 11:14am UTC](https://community.xibo.org.uk/t/re-connecting-player-to-new-cms/14534 "2018-05-29T11:14:12Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Peter](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/peter/32/8154_2.png) [@Peter](https://community.xibo.org.uk/u/Peter)
#### Post date: [May 29, 2018, 1:27pm UTC](https://community.xibo.org.uk/t/re-connecting-player-to-new-cms/14534/2 "2018-05-29T13:27:55Z")

</div>

I assume you’re trying to connect the player with https url?

Can you reach the CMS address in the web browser on the PC with Xibo player?

It might also depend on what kind of SSL certificate you have, for example for the TSL 1.2 there are some registry changes required [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?source_topic_id=7051)

I’d also like to know if it is self-signed certificate or "trusted’/‘proper’ certificate, if it is the latter are the intermediate certificates installed correctly as well?

If there are cert chain problems then the following should help you identify (and fix) the issue  
Test your server here [https://www.ssllabs.com/ssltest/analyze.html](https://www.ssllabs.com/ssltest/analyze.html)

That should tell you where the issue is, if it’s issue with certificate chain, you can test it here [https://whatsmychaincert.com/](https://whatsmychaincert.com/)

---

_[View the full topic](https://community.xibo.org.uk/t/re-connecting-player-to-new-cms/14534)._