# Will I be able to manually get a certificate?

**URL:** https://community.letsencrypt.org/t/will-i-be-able-to-manually-get-a-certificate/172
**Category:** Issuance Tech
**Created:** [August 14, 2015, 10:37am UTC](https://community.letsencrypt.org/t/will-i-be-able-to-manually-get-a-certificate/172 "2015-08-14T10:37:22Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![darkstrym](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@darkstrym](https://community.letsencrypt.org/u/darkstrym)
#### Post date: [August 14, 2015, 10:37am UTC](https://community.letsencrypt.org/t/will-i-be-able-to-manually-get-a-certificate/172/1 "2015-08-14T10:37:22Z")

</div>

I keep seeing about how the script will automatically create the certificate. Will I be able to also do this manually?

---

<div class="post-metadata">

### Author: ![ac000](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ac000/32/71_2.png) [@ac000](https://community.letsencrypt.org/u/ac000)
#### Post date: [August 14, 2015, 10:43am UTC](https://community.letsencrypt.org/t/will-i-be-able-to-manually-get-a-certificate/172/2 "2015-08-14T10:43:42Z")

</div>

The closest I’ve seen to this is (from [https://letsencrypt.org/howitworks/](https://letsencrypt.org/howitworks/))

Without Automatic Web Server Configuration  
$ letsencrypt -d [example.com](http://example.com) auth

---

<div class="post-metadata">

### Author: ![jcjones](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jcjones/32/78_2.png) [@jcjones](https://community.letsencrypt.org/u/jcjones)
#### Post date: [August 14, 2015, 3:28pm UTC](https://community.letsencrypt.org/t/will-i-be-able-to-manually-get-a-certificate/172/3 "2015-08-14T15:28:29Z")

</div>

The official client has a “manual” mode, and other clients can, of course, implement different manual modes that may prove more suitable for your use case.

For example, [Boulder has a (not secret) Node.JS ACME client inside its repo](https://github.com/letsencrypt/boulder/tree/master/test/js) that is just about as manual as using `curl`. It’s certainly not intended as a user friendly product, but we use it for integration testing, so it works.
