Android SSL Support
- Xibo for Android
- Install a White Label or a different Player version on DSDevices
- CEC Screen Power on/off with DSDevices
- Hardware Recommendations
- Philips Signage SoC Monitors
- 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
- 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
Android SSL Support
Xibo for Android is capable of communicating to an SSL enabled CMS, the only step required in most cases is to change the CMS URL in the Player settings to be prefixed with
https:// instead of
We recommend all Displays use SSL and our Cloud CMS instances come with SSL enabled as standard.
In some cases the certificate authority will not be listed as a trusted authority by the Android device and in these cases it will be necessary to install the SSL certificate manually. There are some instructions for how to do this on the Google Support Pages. This will certainly be the case for self-signed certificates.
SSL certificates have to be correct and have to be supported by Android. Common sources of problems are:
- Incorrect date/time on the Player
- Incorrectly configured certificate
The most common error is:
"SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure"
All certificates should be regularly validated with SSL Labs (or similar) to ensure they are secure and compatible. During a support case related to a SSL error we may ask for a SSL Labs report to help diagnose the problem.