# New Name, New Home, le.sh is renamed to acme.sh

**URL:** https://community.letsencrypt.org/t/new-name-new-home-le-sh-is-renamed-to-acme-sh/14290
**Category:** Uncategorized
**Created:** [April 14, 2016, 3:53pm UTC](https://community.letsencrypt.org/t/new-name-new-home-le-sh-is-renamed-to-acme-sh/14290 "2016-04-14T15:53:37Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![stevenpslade](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenpslade/32/7810_2.png) [@stevenpslade](https://community.letsencrypt.org/u/stevenpslade)
#### Post date: [June 21, 2016, 6:29pm UTC](https://community.letsencrypt.org/t/new-name-new-home-le-sh-is-renamed-to-acme-sh/14290/6 "2016-06-21T18:29:56Z")

</div>

Hi @Neilpang, thanks so much for [acme.sh](http://acme.sh).

I have used it to just issue a cert (nginx).

Everything is working great on desktop and iOS, however, Android Chrome cert is untrusted. The solution as per this topic ([On Android 6.0.1 the Certificate is untrusted](https://community.letsencrypt.org/t/on-android-6-0-1-the-certificate-is-untrusted/7815)) is to also serve the `fullchain.pem` in nginx conf.

I am wondering how to get the `fullchain.pem` using [acme.sh](http://acme.sh)? It seems to have only generated the `.csr` and `.key` files.

---

_[View the full topic](https://community.letsencrypt.org/t/new-name-new-home-le-sh-is-renamed-to-acme-sh/14290)._