# Android Chrome SSL issues

**URL:** <https://meta.discourse.org/t/android-chrome-ssl-issues/18248>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [July 29, 2014, 11:36pm UTC](https://meta.discourse.org/t/android-chrome-ssl-issues/18248 "2014-07-29T23:36:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChrisGammell](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisgammell/32/114659_2.png) [@ChrisGammell](https://meta.discourse.org/u/ChrisGammell)\
**Post date:** [July 29, 2014, 11:36pm UTC](https://meta.discourse.org/t/android-chrome-ssl-issues/18248/1 "2014-07-29T23:36:38Z")

</div>

Have been troubleshooting for a few hours now, thought I’d use the meta site as well.

I have a domain SSL cert from Namecheap (Comodo). I appended the intermediate certs to the main cert and am now using that as the listed ssl.crt in use by nginx. However each android device I have refuses to accept that the SSL is valid.

Any thoughts or other experience with this?

---

<div class="post-metadata">

**Author:** ![elberet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elberet/32/122404_2.png) [@elberet](https://meta.discourse.org/u/elberet)\
**Post date:** [July 29, 2014, 11:53pm UTC](https://meta.discourse.org/t/android-chrome-ssl-issues/18248/2 "2014-07-29T23:53:37Z")

</div>

If there are several intermediary CA certificates, make sure to append them in the correct order, from most specific (i.e. your own certificate) to least specific (i.e. the top-most intermediary CA certificate).

For instance, if the certificate chain is:

- Root CA
- Non-EV intermediary CA
- Reseller’s sub-CA
- Reseller’s low-trust intermediary CA
- Your certificate

then the CA bundle file must contain these certificates excluding the root CA’s certificate in **reverse** order, starting with yours, then the reseller’s intermediary, reseller’s sub-ca, and so on.