Display won’t connect a CMS secured with a self-signed certificate
- Xibo for Android
- DSDevices DSCS9X/95 Set-up Guide
- Install a White Label or a different Player version on DSDevices
- CEC Screen Power on/off with DSDevices
- Hardware Recommendations
- Philips Signage SoC Monitors
- Sony Bravia SoC
- Hisense Commercial Displays SoC
- Managing Storage on the Android Device
- Player Settings
- Players without an Internet Connection
- Remote Administration with SS Helper
- Restart Rooted Device with a Shell Command
- Running Xibo for Android
- Resolving Common Issues
- Error shown when I try to licence my Player?
- Player not updating from the CMS?
- I can see my Licence entry but the Player appears unlicensed?
- Error message - Player is missing dependencies
- My scheduled Layouts are not working?
- Layout won't play? Splash screen plays?
- Watchdog error message
- Troubleshooting for Administrators
- Audit Trail
- Log Information
- Player Logs
- Getting the Player Status
- Request Player Status via CMS - Logged in Players only
- Request Player Status directly from a Device
- Can I use the Xibo name / logo?
- Can I run a Xibo Player on Raspberry Pi?
- How can I increase the upload file size limit?
- How do Players communicate with the CMS?
- How many displays can Xibo support?
- How do I reset the Xibo_admin account password?
- Power On/Off for Players
- Testing with Xibo
- Why do I need a Default Layout?
- Xibo for Android FAQ's
- Autoplaying Embedded Youtube Videos
- Closing to Home screen
- Displaying Images
- Embedded TV
- External SD card not listed when running Banana-Pi
- Helper Command to change Time zone
- HTML5 Video
- Memory Notifications
- Menu not accessible
- SSL Support
- Using Portrait Displays
- Video wont play properly
On this page
Display won’t connect a CMS secured with a self-signed certificate
If you have an on-premise CMS that uses a self-signed SSL certificate, you may see that your connection is being rejected. This is because the webOS Display will not accept self-signed certificates.
To resolve this you will need to import the public portion of the self-signed certificate in use by your CMS into the screen so that the certificate becomes trusted.
C and D series models only support importing self-signed certificates to be trusted. Later models (for example E series) support the import of a root CA certificate into the Trust Store which means you can use certificates signed by a central CA for your organisation.
To import your certificate you need to have it in X.509 (PEM) format, and you’ll need a USB stick to load it on to.
On your USB stick, create a folder and a subfolder named LG_MONITOR/CERTIFICATE and put the CRT file into that subfolder to ensure that the webOS can “see” it. Connect the USB stick to your webOS device.
From the TV menu, go to SI Server Settings, then Self-Signed Certificates, and you should be able to select your certificate to import from the USB stick.
If at all possible, use publicly recognised SSL certificate authorities which webOS already trusts to sign your certificates, as it removes the need to configure any trust on the TV.
