Do not fear all is not lost. As we know an SSL is a certificate issued by a trusted authority (Comodo, GeoTrust etc.). These trusted authority are authorised to include their root certificates into most web browsers which is used to link the domain's certificate with the hosting server's certificate and finally with the CA's root certificate. This verification hierarchy is called Chain Root linking. This happens behind the scenes and users go about their business none the wiser. Back to why an SSL may work / display correctly on a desktop environment and appear as untrusted on most mobile browsers. This is the result of the device's browser not including the CA's root certificate and therefore the verification chain link fails and indicates an untrusted connection. The Chain Link needs to be created manually by removing the SSL in its entirity from the server and re-installing it while including the CA Bundle which is supplied with the main certificate from the CA. A few of the authorities (Entrust and Comodo) have tools and instructional guides on creating the Chain Link (https://support.comodo.com/index.php?/Default/Knowledgebase/Article/View/637/37/certificate-installation-apache--mod_ssl
). Once the chain has been installed, you can test the links on http://www.sslchecker.com
- my preference. If you have installed the chain correctly, all mobile devices will now trust the connection.
Hopefully I have shed some light on your concerns and put your mind at ease :)