# Android doesn't trust the certificate

**URL:** <https://community.letsencrypt.org/t/android-doesnt-trust-the-certificate/16498>\
**Category:** Uncategorized\
**Created:** [June 2, 2016, 11:09am UTC](https://community.letsencrypt.org/t/android-doesnt-trust-the-certificate/16498 "2016-06-02T11:09:34Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [June 2, 2016, 10:49pm UTC](https://community.letsencrypt.org/t/android-doesnt-trust-the-certificate/16498/9 "2016-06-02T22:49:16Z")

</div>

@csbubbles, this is the most common post-issuance problem (dozens of other people have had the same trouble), so I wonder where we could best explain this to people.

If (in Certbot) you’re using Apache and you use the Apache installer, it automatically sets the correct chain file. If you used `certonly`, the “Congratulations!” message should have pointed you to `fullchain.pem` instead of `cert.pem`. So, I’m wondering where users are getting the idea of just using `cert.pem` without `chain.pem`. Is it just the filename? Is there some of our documentation that refers to the cert without also mentioning the chain? Is there a clear place where our messages could be improved?

---

_[View the full topic](https://community.letsencrypt.org/t/android-doesnt-trust-the-certificate/16498)._